Leanban is a team-level framework that makes higher level Lean-Agile tenets actionable on a day-by-day basis. It guides processs refinements using the most valuable lessons from Lean, Scrum, eXtreme Programming (XP), and Kanban. It requires a focus on business value, an organizational view, and a deep appreciation of empowered teams.
- based on Lean-Thinking
- a set of starting practices from Scrum, Kanban, and XP
- a way of migrating to different practices when appropriate
- a set of organizational commitments called Guardrails that keep everyone on track
The Agile world is partially based on Lean-Thinking. Both Scrum and Kanban have implemented many of Lean’s principles with set practices – often with great success. Including more of a Lean perspective and incorporating other practices can lead to even more success. A Scrum or Kanban team can readily jump to Leanban, but that is not necessary. Scrum and Kanban teams can learn from each other and incorporate practices from each that work for them. The key is to investigate what works and why and then do that, and understanding Leanban can help.
Leanban is the next step in the evolution of Agile in that it provides guidance to help Agile teams use Lean principles to select and use practices that best fit their situation and to change those practices when beneficial. It provides a consistent approach for delivering business value quickly and sustainably across the organization.
For more information, see Leanban in Depth.
To see how Leanban can help your Scrum team see Improve Scrum with Leanban.
To see how Leanban can help your Kanban team see Improve Kanban with Leanban.
Resources in this topic
Alternatives to Scrum of Scrums (Article)
Business Value, the Forgotten Goal (Blog Entry)
Carry-Over Work (Article)
Contrasting the Daily Scrum with Kanban's Daily Stand-up (Article)
Cross-Functional Teams: Improving Communication Between People who Work Together (Article)
Daily Stand-Ups (Article)
Designing the Kanban Board (Article)
Dynamic Feature Teams: When Static Won't Work (Article)
Further Information on Leanban (Article)
Going Beyond Scrum, Part 1 (Blog Entry)
Going Beyond Scrum, Part 2 (Blog Entry)
Improve Scrum with Leanban (Article)
Iteration 0 - Conduct (Article)
Iteration 0 - Facilitate (Article)
Iteration Planning Meeting - Facilitate (Article)
Iteration Retrospective - Facilitate (Article)
Lean-Agile Team Checklists (Article)
Leanban in Depth (Article)
Meetings for Lean-Agile (Article)
Overview of Standard Work (Article)
Product Demonstration and Review - Facilitate (Article)
Product Demonstration and Review - Plan (Article)
Product Planning and Review - Conduct (Article)
Resistance is Not to Change (Article)
Scrum as Example (Article)
Scrum of Scrums (Article)
Scrum/APM Case Studies (Article)
Types of Tests for Code (Article)
Value Stream Mapping (Article)
What Framework / Method / Approach Are We Using? (Article)
What Roles Are Missing? Which Roles Need To Be Redefined? (Article)
What Should Team Process(es) Be: Scrum, Kanban, Leanban? (Article)
Writing Explicit Policies (Article)
Writing Tasks (Article)