Kanban
Agile method to visualize and control work on a board with columns (To Do, In Progress, Done) and WIP limits for continuous flow.
Kanban is simplicity in practice: a board, cards and clear rules. Originally developed by Toyota for production, Kanban is now one of the most popular agile methods in software. Unlike Scrum there are no fixed sprints – work flows continuously. Kanban fits teams with variable workload: support, maintenance, DevOps and continuous improvement.
What is Kanban?
Kanban (Japanese: visual signal) is an agile method that makes work visible on a board and controls flow with work-in-progress (WIP) limits. Principles: 1) Visualize the workflow (board with columns for each step), 2) Limit WIP (max tasks per column), 3) Manage flow (measure and improve lead/cycle time), 4) Make process rules explicit, 5) Use feedback loops, 6) Improve collaboratively (Kaizen). Kanban has no fixed roles, events or timeboxes – it adapts to existing process.
How does Kanban work?
A Kanban board has columns for each step: Backlog, To Do, In Progress, Review, Done. Each task is a card that moves left to right. WIP limits cap how many cards can be in a column (e.g. max 3 in In Progress). When a column is full, no new card enters until one leaves (pull). Blocked cards are marked and addressed. Metrics: Lead Time (created to done), Cycle Time (in active work), Throughput (completed per period).
Practical Examples
IT support: Tickets flow from Received → Analysis → In progress → Waiting for feedback → Resolved; WIP limit 3 avoids overload.
DevOps: Infrastructure tasks, deployments and incidents on one board, prioritized and processed in continuous flow.
Marketing: Content from Idea → Draft → Review → Design → Approval → Publish – visible to all stakeholders.
Software maintenance: Bugfixes, small features and tech debt prioritized and done continuously, without sprint overhead.
Typical Use Cases
Support and maintenance: Teams with variable, hard-to-plan workload
DevOps and operations: Continuous work without fixed planning cycles
Marketing and content: Creative work with varying lead times
Scrumban: Sprint planning with Kanban flow for day-to-day work
Personal task management: Visualize and limit your own WIP
Advantages and Disadvantages
Advantages
- Easy start: Kanban can be applied to the current process immediately
- Flexible: No fixed sprints or roles – adapts to the team
- Transparent: Everyone sees what’s in progress and where bottlenecks are
- WIP limits reduce multitasking and improve focus and quality
- Continuous improvement: Lead time and cycle time make progress measurable
Disadvantages
- No timeboxes: Without deadlines, work can drag
- Discipline: WIP limits must be respected or Kanban loses effect
- Less structure: No built-in events (e.g. review, retro) like in Scrum
- Prioritization: Without a product owner and sprint planning it can suffer
Frequently Asked Questions about Kanban
Kanban or Scrum?
How do I set the right WIP limit?
Which tool for Kanban?
Related Terms
Want to use Kanban in your project?
We are happy to advise you on Kanban and find the optimal solution for your requirements. Benefit from our experience across over 200 projects.