Layering the Kanban Method with Scrum

Definition

Layering is the practice of deliberately weaving the Kanban Method's principles and practices into a Scrum foundation without replacing or dismantling Scrum itself. The Kanban Method contributes four principles (start with what you do now, respect current roles and responsibilities, pursue incremental evolutionary change, encourage leadership at all levels) and six practices (visualize, limit WIP, manage flow, make policies explicit, develop feedback mechanisms, improve collaboratively through experiments). Scrumban takes the position that these are wholly consistent with how Scrum was designed to operate—Scrum emphasizes local decision-making and empowers practitioners to choose how to achieve its outcomes using whatever models and tools make sense in their context.

In the Book

Reddy uses the Mammoth Bank and Objective Solutions case studies to illustrate contrasting implementations of this layering. Both organizations added kanban visualization and flow management to their Scrum contexts. Mammoth Bank, whose teams were less mature in Scrum execution, continued time-boxed iterations and used the Kanban Method's transparency to improve ceremony effectiveness and shared understanding. Objective Solutions, with mature teams experienced in Extreme Programming, used kanban's continuous-flow capability to eliminate sprint starvation—a business problem, not a team maturity issue. The book emphasizes that the Kanban Method's mechanisms for explicit policies, visualization, and feedback loops directly address weaknesses in Scrum's ceremonial structure without requiring teams to abandon ceremonies entirely.

The book notes that the Kanban Method itself had not fully matured when Ladas first coined Scrumban in 2008; today's layering is far more sophisticated, enabled by the Kanban Method's later crystallization into four clear principles and six practices.

Why It Matters

This concept unlocks the capability to improve Scrum implementations that are struggling not because of Scrum's design but because the context into which it was transplanted makes that design ineffective. Scrumban doesn't position Kanban as a replacement but as a complement that brings psychological safety, service orientation, and flow visibility—dimensions Scrum is largely silent about by design. Layering also allows an organization to preserve Scrum's benefits (team cohesion through sprints, ceremonies for coordination) while gaining Kanban's benefits (predictability, demand-capacity visibility, evolutionary change). Most crucially, this approach scales: you can layer kanban capabilities across multiple teams using the same principles without requiring a wholesale organizational restructure.