Kanban

Kanban is a visual project management method that originated in the manufacturing industry and is now widely used in software development, service delivery, and business operations. It emphasizes visualizing work, limiting work in progress (WIP), and optimizing the flow of tasks through a process.

Kanban is one of the most popular Agile project management frameworks and is often compared with Scrum. Unlike Scrum, Kanban does not prescribe fixed-length iterations (sprints) but enables continuous delivery of value.

Origins

Kanban originated at Toyota in the 1940s as part of the Toyota Production System (TPS), pioneered by Taiichi Ohno.

In Japanese, kanban (看板) means "visual card" or "signboard."
The system was initially designed to improve manufacturing efficiency and eliminate waste through a just-in-time production approach.
The method was later adapted for knowledge work and software development in the 2000s, notably by David J. Anderson.

Core Principles

Kanban is guided by four foundational principles:

Start with what you do now – no need to overhaul processes immediately.
Agree to pursue incremental, evolutionary change.
Respect current roles, responsibilities, and processes.
Encourage leadership at all levels (from team members to executives).

Key Practices

Kanban is operationalized through six core practices:

Visualize the Workflow

Work items are represented on a Kanban board (physical or digital).
Columns represent process stages (e.g., To Do, In Progress, Done).
Improves transparency and shared understanding.

Limit Work in Progress (WIP)

Each workflow stage has a maximum number of tasks allowed at once.
Prevents overload, ensures focus, and improves flow efficiency.

Manage Flow

Focus on how work items move through the system.
Use metrics such as cycle time and lead time to measure performance.
Identify bottlenecks and optimize throughput.

Make Policies Explicit

Define clear rules for moving work between stages.
Policies may include Definition of Done (DoD), prioritization rules, or quality criteria.

Implement Feedback Loops

Regular meetings (daily stand-ups, service delivery reviews, risk reviews).
Feedback ensures continuous improvement and adaptability.

Improve Collaboratively, Evolve Experimentally

Teams continuously reflect and implement small, data-driven changes.
Empirical approach inspired by scientific experimentation.

Kanban Board

The Kanban board is the central tool in Kanban practice.

Consists of columns representing process stages.
Cards represent individual tasks or work items.
WIP limits are applied per column.

A typical software development Kanban board includes:

Backlog
To Do
In Progress
Review / Testing
Done

Metrics and Analytics

Kanban uses data to drive improvements:

Cycle Time – the time it takes for a task to move from start to finish.
Lead Time – the total time from when a request is made until it is delivered.
Cumulative Flow Diagram (CFD) – visualizes work distribution across stages over time.
Throughput – number of tasks completed in a given period.

Advantages

Continuous delivery without fixed iterations.
Increased flexibility compared to Scrum.
Improved visibility of workflow and bottlenecks.
Enhanced team focus due to WIP limits.
Data-driven insights for process optimization.
Can be applied at team, departmental, or enterprise scale.

Challenges

Lack of time-boxed iterations may reduce urgency.
Requires discipline in respecting WIP limits.
Risk of boards becoming cluttered or unmanaged.
Can be harder to predict delivery timelines compared to sprint-based approaches.
Misuse of Kanban as a "task list" without flow management reduces effectiveness.

Comparison with Scrum

Feature	Scrum	Kanban
Iterations	Fixed-length sprints (2–4 weeks)	Continuous flow, no fixed iterations
Roles	Defined (Product Owner, Scrum Master, Dev Team)	No specific roles required
Planning	Sprint Planning & Backlog	On-demand, continuous backlog refinement
WIP Control	Implicit via sprint capacity	Explicit WIP limits per workflow stage
Meetings	Sprint ceremonies (Planning, Review, Retrospective)	Flexible reviews, daily stand-ups optional
Delivery	At end of sprint	Continuous, as work is completed

Tools Supporting Kanban

Kanban boards can be managed physically with sticky notes or digitally with specialized software. Popular tools include:

Trello
Jira (Kanban boards)
Azure DevOps
ClickUp
Asana
Taiga

Applications Beyond Software Development

Kanban is widely applied in non-IT contexts:

Marketing – campaign management, creative workflows.
Human Resources – recruitment pipelines.
Manufacturing – lean production.
Healthcare – patient workflow optimization.
Education – curriculum and assignment tracking.

References

Anderson, D. J. (2010). Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press.
Ohno, T. (1988). Toyota Production System: Beyond Large-Scale Production. Productivity Press.
Kniberg, H. (2011). Kanban and Scrum: Making the Most of Both. C4Media.