techwiki
LinkedIn·Wednesday, 26 August 2026·2h ago

The approach of analyzing your data using the Cycle Time Breakdown is extremely powerful if you maintain a Kanban pull system. Kanban pull…

Nave
1,197 followers
The approach of analyzing your data using the Cycle Time Breakdown is extremely powerful if you maintain a Kanban pull system. Kanban pull systems enable teams to assess how much time the workflow sits in each queue state. In the example here, we have a process with the following steps – Development, Code Review, Testing, Deployment and Done, and the queue states Code review (Done) and Testing (Done). On the Cycle Time Breakdown, it is clearly visible that 20% of the workflow is spent in the Code Review (Done) step. As this is a queue state, it means that the work is not able to move to Testing, it is just sitting and waiting in the queue due to a bottleneck in the Testing state. An obvious solution may be to hire more testing specialists. We could assume that adding more testing capacity would remove the bottleneck. This approach is also known as “elevating the constraint”. However, it costs both time and money. So, rather than jumping immediately to elevation, it might be better to use the resources you already have and relieve the people responsible for that step from activities that could be handled by someone else or completely nixed. Explore the Cycle Time Breakdown Chart by Nave → https://getnave.co/3SOEDmk #NavigateYourFlow #Kanban #Agile #ContinuousImprovement
View on LinkedIn

Cross-referenced

Related on the wire