Process

Process workflows and artifacts internalized and used throughout my career

2004 RUP

2006 Agile Manifesto (signed)

  • 2006 Signed the Manifesto for Agile Software Development
    • Signatures Received: 30 Jul to 12 Aug 2006

      Victor Kane: (AWebFactory) Building software must be built around real human needs, and neither the product nor the process shoved down people's throats. The need for software and the need to produce that software must be framed in a process (the process mirrored in the product - Hudson), is optimized by open, flowing structures reflecting those very real needs and their most excellent solutions. Obstacles imposed by greed and the need to defend privilege must be removed. Working people who produce and use software must together manage that process themselves, worldwide.

2007 Iconix

2009 Leveraging Drupal

2011 Project Flow & Tracker

2013 Lean/UX

2014 DrupalPicchu Drupal Lean Process and Code as Single Source of Truth

2015 DrupalCon Latin America 2015

2021 Headless WordPress Project and its process

2022 Atomic Design Systems, Code as single source of truth with figma and framer

  • Brad Frost's Blog Post on Atomic Design
  • 2022 Interest in figma and design systems (framer motion + next via ES module links (import atomic, molecular links)): the idea is to make everything "code as single source of truth" and have designers work in code (as Jason was suggesting with: drawing -> html (UI library like bootstrap))
  • Let's galvanize
    • the process workflow
    • the artifacts
  • Main focus is the avoidance of team member silos and the road to interdisciplinary development with code as a single source of truth (as in design systems with Figma + UI Components)

Conclusion

  • Final list of process workflow, artifact and tools scenarios:
    • Agile
    • Lean/UX
    • Design Systems
    • DevOps and CI/CD
  • [unfinished, to be completed and continued]