kanban in Dynamic Analysis
Problem to solve
Dynamic Analysis is now a rather small team and the existing per-milestone planning process isn't quite matching the cadence of the group.
Proposal
Conduct a 6 month experiment where the group switches to kanban rather than a scrum-based approach. This would allow for more granular prioritization as well as smooth out the planning process.
Implementation steps
-
Establish a single kanban board from which the team works. https://gitlab.com/groups/gitlab-org/-/boards/5719921?label_name[]=group%3A%3Adynamic%20analysis -
Determine average length of time issues spend in each identified workflow state. - Sisense dashboard with average time per workflow state: https://app.periscopedata.com/app/gitlab/792261/Product-Development-Flow-Analytics
-
Establish WIP limits per column. -
Document process in the handbook. -
Establish start milestone for this new process -- %16.2.
Proposed WIP limites
Workflow state | WIP limit | Notes |
---|---|---|
workflowplanning breakdown | 3x engineer | What to do if issue is too big? Initial thoughts are to 1) articulate a course, iterative implementation plan, 2) work with PM on priority order, 3) Promote initial issue to an epic, 4) create implementation issues out of the implementation plan, and 4) move first issue into planning breakdown. |
workflowrefinement | 1x engineer | |
workflowready for development | 2x engineer | Buffer queue |
workflowin dev | 2x engineer | Frequently need to update multiple projects while working on a single issue. |
workflowin review | 3x engineer | Need room for projects with longer review cycles. |
workflowverification | 1x engineer |
- Assumes WIP limits need to adjust depending upon the number of engineers working within the group.
Edited by Thomas Woodham