Kanban
A visual workflow management method that tracks work items on a board with columns representing stages of progress, with work flowing continuously.
Detailed Explanation
Kanban is a flow-based system where work items move through columns (To Do, In Progress, Review, Done) as they are completed. Unlike Scrum, Kanban has no fixed iterations—work flows continuously as capacity allows. The key principle is limiting work in progress (WIP) to prevent overload and improve flow.
Kanban boards visualize the entire workflow, making bottlenecks obvious. WIP limits ensure the team focuses on completing work before starting new items. Kanban is ideal for teams with continuous incoming work (support, operations, maintenance) rather than batch-based feature development.
Why It Matters
Kanban provides visibility into workflow, limits overload, and improves throughput. It is simpler to implement than Scrum and works well for many team types.
Real-World Example
A support team uses Kanban with WIP limits: 3 tickets in "In Progress" maximum. When a developer finishes a ticket, they pull the next one from the queue. This prevents multitasking and ensures tickets move through the system quickly.
When to Use
For teams with continuous incoming work (support, DevOps, maintenance), when you need visual workflow management, or when Scrum's ceremonies feel too heavy.
Advantages
- Visual workflow makes bottlenecks obvious
- WIP limits improve focus and throughput
- No sprint planning overhead
- Continuous delivery without batch constraints
- Simple to implement and understand
Disadvantages
- No fixed delivery cadence
- Harder to plan long-term without sprints
- Requires discipline to respect WIP limits
- Less structure than Scrum
- Can become "doing Agile" without Agile mindset
Frequently Asked Questions
What is the difference between Kanban and Scrum?
Scrum uses fixed sprints with planning. Kanban is continuous flow with WIP limits. Scrum is better for feature development; Kanban is better for operations and support. They can be combined.
What is WIP limit?
Work In Progress limit restricts how many items can be in a column at once. It prevents multitasking, surfaces bottlenecks, and improves throughput. Start with limits equal to team size and adjust.
How do I set up a Kanban board?
Create columns for your workflow stages (To Do, In Progress, Review, Done). Add cards for each work item. Set WIP limits. Move cards as work progresses. Use tools like Trello, Jira, or GitHub Projects.
Can I combine Scrum and Kanban?
Yes. "Scrumban" combines Scrum's ceremonies with Kanban's flow-based approach. Use sprints for planning but Kanban board for visualization and WIP limits. Many teams naturally evolve to this hybrid.
How do I handle urgent work in Kanban?
Create an "Expedite" or "Urgent" column with a WIP limit of 1. Only truly urgent items go there. This prevents everything from being labeled "urgent" while still allowing genuine emergencies.