What is Kanban?
Kanban is a workflow management method that visualizes work, limits work in progress (WIP), and optimizes flow.
Kanban is a workflow management method that visualizes work, limits work in progress (WIP), and optimizes flow. Originating from Toyota's manufacturing system, it was adapted for software development by David J. Anderson.
Kanban principles: visualize the workflow (board with columns), limit WIP (set maximum items per column), manage flow (optimize throughput), make policies explicit, and improve collaboratively.
Kanban vs. Scrum: Kanban is flow-based (continuous), Scrum is iteration-based (sprints). Kanban has no prescribed roles, Scrum has Scrum Master and Product Owner. Kanban limits WIP per column, Scrum limits work per sprint. Many teams use "Scrumban" — combining elements of both.
The key insight: limiting WIP reduces context-switching, which dramatically improves productivity. A developer working on 5 things completes all 5 slower than a developer working on 2 things sequentially.
Why It Matters
Kanban WIP limits are the most effective technique for reducing context-switching, which is the single biggest productivity killer in software development. Limiting WIP can improve throughput by 30-50%.
Frequently Asked Questions
What is Kanban?
A workflow method that visualizes work and limits work in progress. It optimizes flow by preventing context-switching and bottlenecks.
Should I use Kanban or Scrum?
Kanban for continuous flow work (support, operations). Scrum for project-based work with clear deliverables. Many teams use Scrumban — combining sprints with WIP limits.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →