02 / Production system
Optimize the work
as deliberately as the code
Statistical planning
Used Scrum with relative complexity and historical velocity so project management—not individual developers guessing hours—translated scope into dates.
Value / Time
Prioritized work by expected value relative to delivery cost, keeping technical and product decisions in the same conversation.
Continuous improvement
First learned Scrum in a mentor-guided Wargaming team with rotating responsibilities and retrospectives, then applied and adapted those principles as CTO.
At D.A.W.Studio I designed a Jira and Confluence workflow in which feature specification, implementation, QA acceptance, and lasting documentation were one evolving artifact. User Stories, Job Stories, and JTBD were combined with concrete requirements and testable game rules.
- Game Design described intended rules rather than only wishes.
- QA accepted the request from Game Design and the completed feature from development.
- Final acceptance updated the same page from “what to build” to “what was built,” including justified changes.
- Department backlogs were separated from tasks assigned to named people, exposing capacity and unallocated work.
- The workflow made Game Design, development, and QA mutually accountable instead of creating a one-way handoff chain.