Scrum is a great adapting tool. But does it adapt fast enough?
We discover we are running late and here we dealt with the problem by descoping. But did we act too late? And what caused it? Let’s plot our feature development phases on a timeline:
Obviously testing is a bottleneck. Maybe we lack test resources, or automation. But this is what causes our burndown to flatten and a buildup of unfinished work. Unfortunately for us, it remains hidden.
Now let’s see how a Kanban board could give this situation away. We make phases horizontal slices (and projects team is working on vertical lanes).
Can you spot the problem?
Yes. The queues gives away the bottleneck.
Queues are excellent problem indicators. The beauty with Kanban is that problems can be seen at an early stage and by the glance of an eye. So it helps visualize problems early and for everyone – including the occational manager. 🙂