Discussion and Clarification of the Product Development Workflow
Purpose
Per our previous conversation, lets map out each stage of the product dev workflow and document the following:
- Who is responsible for working on the issue in the stage?
- What criteria enable the issue to move to the next stage of development?
- Who is responsible for moving the issue to the next stage?
- What is the WIP we would like to put in place for the stage?
Proposed Stages
| Stage | Responsible | Completion Criteria | Who Transitions Out | Proposed WIP Limit | Notes |
|---|---|---|---|---|---|
| workflowstart | PM | Item has enough information/data to begin Problem Validation | PM | - | |
| workflowproblem validation | PM | Item is validated and defined enough to propose a solution | PM | 4 | |
| workflowdesign | UX | Design work is complete enough for issue to be implemented | UX | 2 per Group | |
| workflowsolution validation | ENG | Proposed Solution is deemed viable by Engineering | EM | 2 per Group | |
| workflowplanning breakdown | ENG | Issue has backend and/or frontend labels and estimated weight attached | EM | 2 per Group | |
| workflowscheduling | ENG | Issue has a numerical milestone label | PM/EM | - | |
| workflowready for development | ENG | An engineer has started to work on the issue | Eng | - | |
| ~"workflow::In dev" | ENG | Initial engineering work is complete and review process has started | Eng | 1 per Dev | |
| ~"workflow::In review" | ENG | MR(s) are merged | Eng | 2 per Group | |
| workflowverification | ENG | Work is demonstrable on production | Eng | 2 per Group | Transitioning Out == closing issue |
| workflowblocked | PM/EM | Work is no longer blocked | EM | - | Will probably go away once blocking issues are completed. |