Skip to content
All apps

WIP Limit and Lead Time

About this app

A Kanban board with analysis, development and testing, day by day: cards with number and start day move across the board, people (1/3/1) work on the oldest cards, and a queue forms in front of the testing bottleneck. The WIP limit (none down to 2) is a pull rule with a gauge, next to a cumulative flow diagram with measuring lines. Without a limit throughput 0.5 and a lead time of 26 days; with limit 5 still 0.5, but 10 days. Little's Law, plus a switch to let developers help with testing.

Start less, finish sooner

In Kanban a WIP limit (work in progress) caps the number of started but unfinished tasks. New work is only pulled when something is done. Little’s Law describes the relationship: lead time = work in progress ÷ throughput. A system’s throughput is set by its bottleneck. Starting more than the bottleneck can handle does not raise throughput; it only increases work in progress and therefore lead time. A limit that is too small, on the other hand, lets the bottleneck run idle.

What the app shows

A Kanban board with analysis, development and testing runs day by day. Analysis has one person and takes one day per card, development three people with three days, testing one person with two days. Testing manages 0.5 cards per day and is the bottleneck. Cards carry a number and start day, and figures stand at their next card. The WIP limit can be set from “none” down to 2. A cumulative flow diagram shows work in progress as vertical and lead time as horizontal distance. Without a limit lead time is 26 days; with limit 5 it is 10 days at the same throughput.

Try it yourself

Play the run without a limit and watch cards pile up in front of testing. Then set limit 5 and compare the numbers. Lower the limit to 2: testing runs idle and throughput drops. The switch “developers help with testing” lets idle developers test at half speed; it only works with a limit, because without one developers are never idle. A table lists all settings side by side.

Frequently asked questions

What is a WIP limit?
A WIP limit caps how many tasks may be in progress at the same time. Only when a task is finished may a new one start. This prevents queues, shortens lead times and makes bottlenecks visible.
What does Little’s Law say?
Little’s Law relates three quantities of a stable system: lead time = work in progress ÷ throughput. At equal throughput, less work in progress therefore means shorter lead time. It holds for systems in equilibrium where work in progress does not keep growing.
Why does more parallel work not increase throughput?
Throughput is limited by the slowest step, the bottleneck. Extra started tasks just wait in front of it. They lengthen lead time without getting more done.
What can I adjust in the app?
The WIP limit from “none” down to 2 and whether developers help with testing. Staffing and processing times are fixed. The run advances day by day or automatically, and a numbers panel shows throughput, lead time and work in progress.

Subject: Software engineering

More from Software engineering

A VisuApp by heyprof: interactive, free in your browser, no sign-up. What is a VisuApp? · All apps