Kanban
A visual workflow management method using boards and WIP limits.
Detailed Explanation
Kanban is an agile framework for managing work by visualizing tasks on a board, limiting work in progress (WIP), and optimizing flow. Originally from Toyota's manufacturing system, it has been adapted for knowledge work, software development, and project management.
A Kanban board typically has columns representing workflow stages (e.g., To Do, In Progress, Review, Done). WIP limits restrict how many items can be in each column simultaneously, preventing overload and encouraging the team to finish work before starting new items.
Unlike Scrum, Kanban does not prescribe timeboxed iterations, roles, or ceremonies. It is a continuous flow system that is particularly effective for teams handling a mix of project work and operational tasks, support teams, or teams transitioning to agile gradually.
Key Points
- Visualizes work on a board with columns for workflow stages
- WIP limits prevent overload and improve flow
- Continuous flow — no prescribed timeboxes or sprints
- Originated from Toyota's lean manufacturing system
- Fewer prescribed roles and ceremonies than Scrum
- Best for teams with mixed project and operational work
Practical Example
A DevOps team uses a Kanban board with columns: Backlog, Ready, Development (WIP: 3), Code Review (WIP: 2), Testing (WIP: 2), Done. When Development hits its WIP limit of 3, no new work can start until something moves to Code Review. This forces the team to collaborate on finishing in-progress items rather than starting more work.
Tips for Learning and Applying
Start with your current process and visualize it — Kanban does not require a big-bang transformation
Set WIP limits and enforce them — they are the heart of Kanban's effectiveness
Measure lead time and cycle time to identify bottlenecks
Use cumulative flow diagrams to visualize flow health over time
Related Terms
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.