Scrumban simulation
Imagine this...
You’re part of a team that has been implementing a product backlog for a while. You have your priorities well under control and you are able to deliver value iteration after iteration, which helped you bring a first version of your product to the market and delight your customers.
But now that you also have a product to maintain, things are changing. Your iteration plans get cluttered with unplanned work. And what about events that impact you capacity or priorities?
If you want to learn how to deal with both planned and unplanned work in an iterative context, then you have come to the right place. Because the Scrumban simulation is made especially for you!
Why Scrumban?
Scrum works fine to have focus, a timebox in which you create value as agreed. But once you start getting bothered with operational work, your iteration forecast gets under pressure.
​
Kanban is ideal to create a constant flow of changes but to do Kanban properly, is really hard. It requires maturity and discipline. I've seen many teams struggle with a Scrum based approach, so they switched to Kanban instead. But what they really did, was just work visualization, not Kanban. Why? Because:
-
Their board was not based on their workflow
-
They didn't respect the pull principle of Kanban
-
They didn't limit their work in progress
-
There was no measurement of cycle time and lead time, metrics they can use to improve their flow
​
Scrumban on the other hand can be a step up towards Kanban. If your work is a mixture of create (plannable) and operational work, then the iteration candence gives you focus to work on this plannable work.