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. Your work is a mixture of create and operational work and the iteration candence gives you focus.