A pull-based work management method that visualises flow, limits work-in-progress, and improves the system through measured experiments. It is a method, not a framework — it overlays improvement discipline on the team's existing process.

How is Kanban different from Scrum?

Scrum prescribes sprints, roles, and ceremonies; Kanban prescribes none of those. Kanban focuses on flow metrics (lead time, throughput, WIP) and continuous delivery rather than time-boxed iterations.

What should the WIP limit be?

Tight enough to feel uncomfortable. A common starting point is one or two items per person in development columns. If the team is never blocked by limits, they are too generous and you are not gaining the benefit.

What is a cumulative flow diagram?

A stacked area chart showing the number of items in each workflow state over time. Widening bands signal bottlenecks; flat top lines signal delivery failures. It is the single most useful Kanban diagnostic.

How do you handle priorities in Kanban?

Classes of service: standard, expedite, fixed-date, intangible. Each class has explicit policies (e.g. expedite items bypass WIP limits but are capped). Priorities become rules, not opinions.

Does Kanban work for project teams?

Yes, especially for teams with unpredictable demand (support, ops, platform). For purely greenfield project work with fixed scope, Scrum or hybrid models often fit better — though Kanban-style WIP limits still help.

What is a replenishment meeting?

The Kanban equivalent of sprint planning: a cadenced session where the team pulls new items from the backlog into the committed queue. Usually weekly or bi-weekly, attended by the team and the service request manager.

How do I forecast in Kanban?

Use Monte Carlo simulation on historical throughput. Given the current backlog and observed throughput distribution, the simulation produces probabilistic delivery dates. It is more reliable than story-point velocity averages.

Which calculators on PMMilestone.org apply to Kanban?

For Kanban, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Kanban?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Kanban?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Kanban?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Kanban is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Kanban defined on PMMilestone Research & Insights?

A pull-based work management method that visualises flow on a board, limits work-in-progress, and improves delivery through measured experiments rather than fixed iterations. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Agile · Letter K

Kanban

A pull-based work management method that visualises flow on a board, limits work-in-progress, and improves delivery through measured experiments rather than fixed iterations.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-22

Definition

Kanban is a method for managing knowledge work that emphasises visualising the workflow, limiting work-in-progress (WIP), and managing flow through evolutionary improvement. Unlike Scrum, Kanban does not prescribe sprints, roles, or ceremonies. It overlays a measurement and improvement discipline on the team's existing process, then steers the system using feedback loops and flow metrics rather than calendar events.

History

Kanban's roots are in the Toyota Production System, where physical "kanban" cards signalled material replenishment between workstations from the 1950s onward. David J. Anderson adapted the method to software development at Microsoft and Corbis in 2005–2007, codifying it in his 2010 book Kanban: Successful Evolutionary Change for Your Technology Business. The Kanban Method has since become a standalone framework taught by the Kanban University and widely used in operations, IT support, and product engineering.

Six Practices

Visualise the work: a board with columns representing workflow states.
Limit WIP: explicit caps per column force completion before starting.
Manage flow: watch for bottlenecks; act on them.
Make policies explicit: rules for pull, blocked items, expedited work.
Implement feedback loops: daily stand-ups, replenishment, service-delivery reviews.
Improve collaboratively, evolve experimentally: small, measured changes.

Real-World IT / Agile Example

A managed-services operations team I worked with had no sprint cadence and 90+ open tickets at any time. We introduced a board with a WIP limit of 8 items in progress and a "ready for review" column capped at 3. Within six weeks, average lead time dropped from 11 days to 4.5 days, even though the team handled the same volume. Limiting WIP forced finishing; finishing freed the queue.

Real-World Construction Example

Lean construction borrows the same idea through visual planning walls and the Last Planner System. On a refurbishment programme, the planning wall showed activities pulled left-to-right across "constraint-free → committed → in progress → done" columns, with WIP limits per trade. The discipline cut Reasons for Incomplete Work (RNC) from 32% to 9% over two months.

Flow Metrics

Lead time: calendar time from request to delivery.
Cycle time: calendar time from start to delivery.
Throughput: items completed per period.
WIP: items in progress at a given moment.
Cumulative Flow Diagram (CFD): stacked area chart by column, exposes bottlenecks visually.

Project Controls Perspective

Kanban turns a controls dashboard into a service-delivery dashboard. Track lead-time distribution (percentiles, not averages — the 85th percentile is the honest commitment), throughput trend, and CFD width per column. A widening band in the "in progress" column is a bottleneck; a flat "done" line is a delivery failure.

Common Mistakes

Putting up a board with no WIP limits — the board becomes a parking lot.
Ignoring the queue policies; everyone pulls what they like.
Reporting averages instead of percentiles; lead-time commitments become fiction.
Mistaking Kanban for "Scrum without sprints" — the method has its own discipline.
No regular replenishment cadence; the backlog rots.
Skipping service-delivery reviews; improvements stop happening.

Expert Tips

Set WIP limits at "uncomfortable." If the team is never blocked, the limits are too generous.
Report the 85th percentile lead time. Averages hide tail risk.
Use classes of service. Standard, expedite, fixed-date, intangible — explicit prioritisation policy.
Run a service-delivery review monthly. Look at flow, not feature counts.
Limit columns, not just WIP. Boards with 12 columns hide flow; 4–6 is usually enough.

Key Takeaways

Kanban is a method, not a framework; it overlays improvement on existing process.
Visualise, limit WIP, manage flow — the three load-bearing practices.
Lead-time percentiles, not averages, drive credible commitments.
Bottlenecks live in the CFD's widening bands.
Construction's Last Planner System is the same idea in a different industry.

Related Concepts

Kanban interlocks with Agile, Backlog Refinement, Daily Stand-ups, Look-Ahead Schedules, and Burn-Down Charts. Resources at PMMilestone.org.

Frequently Asked Questions

What is Kanban?
A pull-based work management method that visualises flow, limits work-in-progress, and improves the system through measured experiments. It is a method, not a framework — it overlays improvement discipline on the team's existing process.
How is Kanban different from Scrum?
Scrum prescribes sprints, roles, and ceremonies; Kanban prescribes none of those. Kanban focuses on flow metrics (lead time, throughput, WIP) and continuous delivery rather than time-boxed iterations.
What should the WIP limit be?
Tight enough to feel uncomfortable. A common starting point is one or two items per person in development columns. If the team is never blocked by limits, they are too generous and you are not gaining the benefit.
What is a cumulative flow diagram?
A stacked area chart showing the number of items in each workflow state over time. Widening bands signal bottlenecks; flat top lines signal delivery failures. It is the single most useful Kanban diagnostic.
How do you handle priorities in Kanban?
Classes of service: standard, expedite, fixed-date, intangible. Each class has explicit policies (e.g. expedite items bypass WIP limits but are capped). Priorities become rules, not opinions.
Does Kanban work for project teams?
Yes, especially for teams with unpredictable demand (support, ops, platform). For purely greenfield project work with fixed scope, Scrum or hybrid models often fit better — though Kanban-style WIP limits still help.
What is a replenishment meeting?
The Kanban equivalent of sprint planning: a cadenced session where the team pulls new items from the backlog into the committed queue. Usually weekly or bi-weekly, attended by the team and the service request manager.
How do I forecast in Kanban?
Use Monte Carlo simulation on historical throughput. Given the current backlog and observed throughput distribution, the simulation produces probabilistic delivery dates. It is more reliable than story-point velocity averages.
Which calculators on PMMilestone.org apply to Kanban?
For Kanban, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Kanban?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Kanban?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Kanban?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Kanban is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Kanban defined on PMMilestone Research & Insights?
A pull-based work management method that visualises flow on a board, limits work-in-progress, and improves delivery through measured experiments rather than fixed iterations. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Kanban →