Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 41 ยท Agile and Scrum

Kanban and Flow Metrics

Learn Kanban for project management: boards, WIP limits, pull systems, cycle time, throughput, Little's Law and how Kanban combines with Scrum, with Python.

Kanban (Japanese for "visual signal") began in Toyota's factories as a card system that told a workstation when to make more parts. Applied to knowledge work, it is a method for managing flow: you make all work visible, limit how much is in progress, and measure how long items take to get through. Unlike Scrum, Kanban has no sprints, no required roles and no fixed events. You start from your current process and improve it gradually.

The Kanban board

A board has columns for the stages of your workflow, and a card for each work item. A typical software board: Backlog, Ready, In Progress, Review, Testing, Done. A swimlane is a horizontal row for a class of work (for instance expedite, features, bugs).

flowchart LR
  B["Backlog"] --> R["Ready"]
  R --> I["In Progress<br/>WIP limit 3"]
  I --> V["Review<br/>WIP limit 2"]
  V --> D["Done"]

Work is pulled from left to right only when the next column has room.

Core practices

Six Kanban practices

Visualize Show every item and its stage.
Limit WIP Cap work in progress per column.
Manage flow Watch where work waits.
Explicit policies Write down what "done" means.

Also: feedback loops and improve collaboratively.

1 / 2

The central idea is a pull system. You do not push new work into a busy stage; you pull a new item only when you have capacity. A WIP limit is a hard cap on items in a column. When the column is full, you must help finish something, not start something. Typical rule of thumb: limit about equal to the number of people or a bit lower.

Metrics that matter

  • Lead time: from the request being made until it is delivered (the customer's view).
  • Cycle time: from when work starts until it is done (the team's view).
  • Throughput: items finished per unit of time (for example, per week).
  • WIP: items currently in progress.
  • Work item age: how long an unfinished item has been in progress.

These are related by Little's Law, a result from queueing theory that holds for any stable system:

TEXT
average cycle time = average WIP / average throughput

If your team has 12 items in progress and finishes 4 per week, the average cycle time is 3 weeks. To halve the cycle time you can either double throughput (hard) or halve WIP (easy: just stop starting).

Python Little's Law in numbers

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Computing flow metrics from data

Here is a small dataset of finished items with start and finish days. From it we get cycle times, percentiles and throughput, the inputs for forecasting.

Python Cycle time and throughput from completed items

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The percentile-based statement is called a service level expectation: "85 percent of items are done within 7 days". It is much more useful for customers than the average, because averages hide the long tail.

Forecasting with throughput

Kanban teams forecast without estimating each item: sample from historical throughput. If you finished 3, 5, 4, 2, 6 and 4 items in the last six weeks and have 30 items left, simulate how many weeks it takes.

Python When will 30 items be done?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Spotting a bottleneck

A bottleneck is the stage where work queues up. On the board it appears as a column that is always full while columns after it are empty. The fix is not to speed up other stages (that only increases the pile), but to:

  1. Make the best use of the constrained stage (no idle time, no low-value work).
  2. Subordinate other stages to it (do not feed it more than it can handle).
  3. Add capacity to it (cross-train people, automate).

Kanban versus Scrum

Aspect Scrum Kanban
Cadence Fixed sprints Continuous flow
Roles PO, Scrum Master, Developers None prescribed
Commitment Sprint Goal WIP limit
Change in mid-cycle Protected Allowed when capacity opens
Key metric Velocity Cycle time, throughput
Best for Product development in iterations Support, operations, mixed or unpredictable work

Many teams use both. Scrumban keeps sprints for planning but adds a board with WIP limits and flow metrics. Kanban also fits non-software teams: marketing, HR onboarding, and the personal to-do list.

Starting Kanban

  1. Draw the current workflow as columns, with what you actually do, not an ideal process.
  2. Put every item on the board.
  3. Set initial WIP limits and adjust them every few weeks.
  4. Review flow metrics at a regular cadence and run a short improvement discussion.
  5. Write policies: what must be true to move a card.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A team has an average WIP of 15 items and a throughput of 5 items per week. What is the average cycle time by Little's Law?

    Cycle time = WIP / throughput = 15 / 5 = 3 weeks.
  2. 2. What is the purpose of a WIP limit?

    WIP limits force finishing before starting, which shortens cycle time and reveals constraints.
  3. 3. Lead time differs from cycle time because it:

    Lead time covers the customer's whole wait, including time in the backlog.
  4. 4. Which statement is a good service level expectation?

    A percentile with a time frame is a clear, measurable promise that reflects variation.

Summary

  • Kanban visualizes work, limits WIP and manages flow with a pull system.
  • Key metrics: lead time, cycle time, throughput, WIP and item age.
  • Little's Law links them: cycle time equals WIP divided by throughput.
  • Forecast with historical throughput and express commitments as percentile service levels.
  • Scrum and Kanban combine well; choose by the nature of the work.

Next: Choosing a Methodology