Skip to content
Omnikalc

How does work in progress affect delivery time?

Enter the items in progress, the throughput and a target cycle time: get the average cycle time and the WIP limit needed to reach the target.

Updated on
Your inputs

Value out of range

Value out of range

Value out of range

Results

Average cycle time (weeks)

3.00

The cycle time is above the target: reduce the work in progress
Average cycle time (days, 5 working days a week)
15.0
WIP limit for the target cycle time
16.0
Items to remove from WIP to reach the target
8.0

Why does work take so long when everyone is busy? Little’s law gives a simple link between three numbers: the work in progress, the throughput and the cycle time. When a team starts more than it finishes, items wait, and the average time grows. This calculator gives the cycle time from the WIP and throughput, and the WIP limit needed to reach a target.

How the calculation works

  • Cycle time = work in progress ÷ throughput
  • WIP limit = throughput × target cycle time
  • Items to remove = current WIP − WIP limit

Example

A team has 24 items in progress and finishes 8 per week. The average cycle time is 3 weeks, or 15 working days. To get the average to 2 weeks, the WIP limit is 16, which means 8 items must be finished or removed before new ones start.

Why it matters

Little’s law underlies kanban and lean practice. It explains why limiting work in progress shortens delivery without asking anyone to work faster, and it holds for support queues, factory floors, hospital wards and server requests. It is also a quick consistency check: if reported figures for the three quantities do not fit, one of them is wrong.

Good to know

The law relates averages in a stable system. If the team’s throughput changes sharply, or the backlog grows rapidly, the equation holds only over long periods. Average cycle time hides spread: some items take far longer than average, and percentiles are better to promise delivery dates. Keep the units consistent: if throughput is per week, the cycle time comes out in weeks. The law says nothing about the order in which items are handled, so it should be combined with good prioritization, and it does not tell you how to raise the throughput itself; reducing WIP mainly removes waiting. This tool is for education.

The queue wait time calculator estimates waiting at a service desk, the sprint velocity calculator forecasts how long a backlog takes, and the team capacity calculator estimates what a sprint can hold.

Frequently asked questions

What is Little's law?

A result from queueing theory: the average number of items in a system equals the average arrival rate multiplied by the average time an item spends in it. In symbols, L = λ × W.

How does it apply to a team?

The items in progress (WIP) equal the throughput multiplied by the cycle time. If a team finishes 8 items a week and has 24 in progress, an item takes 3 weeks on average to get through.

Does reducing WIP really cut the cycle time?

Yes, if throughput stays the same. Cutting the number of items in progress shortens the time each item waits, which is the basis of kanban limits. Throughput often improves too, because there is less switching between tasks.

What assumptions does it make?

That the system is stable over the period: the average arrival rate equals the average departure rate, and the work in progress is not growing or shrinking. It holds for any distribution of times, which is why it is so widely applicable.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.