In 30 seconds
- No sprints: work flows continuously through visible stages.
- Work-in-progress limits stop the team taking on too much at once.
- You start with your current process and improve it gradually.
The core practices
- Visualize the work on a Kanban board, one card per item.
- Limit work in progress so items finish before new ones start.
- Manage flow: watch where work piles up and fix the bottleneck.
- Make policies explicit, such as what "done" means for each column.
- Improve collaboratively using data, in small steps.
Where it came from
Kanban (Japanese for "signboard") began in Toyota's production system as cards that signalled when to make more parts. David J. Anderson adapted the idea to software and knowledge work in the mid-2000s.
How you know it's working
Kanban teams track flow metrics rather than velocity: lead time (request to delivery), throughput (items finished per week) and how much work is in progress. Shorter, more predictable lead times are the goal.
When to choose Kanban
Kanban fits work that arrives unpredictably: support, operations, maintenance, or teams that find fixed sprints artificial. It also suits teams that can't change roles or ceremonies yet, because it starts from the current process. Compare it on Scrum vs Kanban.
Myth vs reality
FAQ
Does Kanban have roles?
No mandatory ones. Teams often keep existing roles and add a service owner later.
What is a good WIP limit?
Start near the number of people in the column, then lower it until flow improves.
Can Scrum teams use a Kanban board?
Yes, and many do. Using the board doesn't make them a Kanban team without WIP limits.