Evolution of Kanban Board – Part 2
We have now added Ready queues prior to each state.
Corey Ladas writes
The irregularity of requirements and the creative, knowledge intensive nature of a design activity like software development rules out clocked workflow synchronisation. Risk and uncertainty are built into the nature of development work. Novelty is what gives software its value, so we can only get so far in reducing this kind of variation before you have to mitigate and adapt to it.
We use small inventory buffers between value adding processes in order to absorb variation in the duration of each activity across work items. We allocate tokens to those buffers just like anywhere else and those count towards out total allocation.
Therefore our board now has the following states:
- Ready for Analysis
- In Analysis
- Ready for Acceptance Criteria
- In Acceptance Criteria
- Ready for Development
- In Development
- Ready for QA
- In QA
- Ready for Live
- Released
