What Is Kanban? Origin, Principles, and Core Practices
Discover the origins of Kanban in manufacturing and how it evolved into a powerful agile methodology. Learn the four core principles and six practices.
Detailed Explanation
What Is Kanban?
Kanban (Japanese for "visual signal" or "card") is a workflow management method that originated in Toyota's manufacturing system in the late 1940s. Taiichi Ohno developed it as a scheduling system to improve production efficiency by limiting work in progress.
The Four Core Principles
- Start with what you do now -- Kanban does not prescribe a specific process. It overlays onto your existing workflow, making incremental improvements.
- Agree to pursue incremental change -- Rather than radical transformation, Kanban encourages small, continuous improvements.
- Respect current roles and responsibilities -- No new roles are required. Existing team structures remain intact.
- Encourage leadership at all levels -- Everyone from individual contributors to managers is empowered to suggest improvements.
The Six Core Practices
- Visualize the workflow -- Use a board with columns representing stages.
- Limit Work in Progress (WIP) -- Set maximum items per column to prevent overload.
- Manage flow -- Monitor how cards move through the system and remove blockers.
- Make policies explicit -- Define clear rules for when cards move between columns.
- Implement feedback loops -- Regular reviews and retrospectives.
- Improve collaboratively, evolve experimentally -- Use data to guide process changes.
From Manufacturing to Software
David J. Anderson adapted Kanban for knowledge work and software development in 2007. The transition was natural because software development, like manufacturing, benefits from limiting work in progress and visualizing flow.
Use Case
Use this guide as an introduction to Kanban for team members or stakeholders who are new to the methodology and want to understand its foundations.
Try It — Kanban Board
Related Topics
Basic Kanban Workflow: To Do, In Progress, Done
Fundamentals
Kanban vs Scrum: Key Differences and When to Use Each
Fundamentals
WIP Limits: How to Set and Enforce Work-in-Progress Limits
Best Practices
Kanban Metrics: Lead Time, Cycle Time, and Throughput
Best Practices
Kanban for Software Development Teams
Fundamentals