Tag Archives: Scrumban

Why Stretched Teams do “Scrumban”

15842087_sA few years ago Corey Ladas wrote an article about an Agile approach he called “Scrumban”. As the name suggests, this is a variant of Scrum with certain Lean-Kanban characteristics. What he proposed was a graduation of Scrum teams to leaner and more pull-based ways of working than Scrum itself allows.

Whereas Scrum will “batch” work up into Sprint Backlogs and potentially releasable increments, a leaner Scrumban approach will seek to minimize the batching of work as far as possible. Each work item will be processed in response to a clear signal for demand, and not because it has been planned into a Sprint backlog. In strictly Lean terms, holding on to such inventory is a form of waste.

What Corey proposed was the gradual facilitation of leaner practices in Scrum. He sought “…to incrementally enhance Scrum with more and more pull-like features until all that remains of the original process is vestigial scaffolding”. For example, he argued that “if your iteration backlog contains 20 work items, then that’s still about 19 more than it needs to be in a pull system”.

The result was an agile approach which makes a Leaner way of working an end in itself. Since then though, Scrum-Kanban hybrids have taken off in ways that were perhaps not entirely foreseeable at the time when Scrumban was floated.