WIP limit calculator
Average WIP equals throughput times average cycle time (Little's law). Enter how many items your team finishes per week and how long an item takes, and the calculator returns a WIP limit for your board.
Everything runs in your browser. Your text and files stay on your device and are never uploaded.
Work it out from your own history
Fill in the two numbers above and the third appears here.
How to use it
- Choose what you want to find: the WIP limit, cycle time or throughput.
- Enter your throughput, the items finished per day or week, and your average cycle time in working days or weeks.
- Or open the history box and paste the cycle time of each finished item and your weekly counts, then use the averages.
- Add a buffer percentage if you want headroom above the exact number, and your team size to see items per person.
- Set the limit on your board's columns, run two or three weeks, then recalculate with the new data.
What Little's law says about WIP
For any stable flow, average work in progress equals average throughput times average cycle time. If your team finishes 7 items a week and an item takes 5 working days, 7 items per 5 days is 1.4 a day, and 1.4 times 5 is 7 items in progress. That number is a starting WIP limit: more than that and items wait in queues, fewer and people sit idle.
The law also works in reverse. Hold throughput steady and every extra item in progress adds waiting time to all of them, so a lower limit is the cheapest way to shorten cycle time. Lower the limit a little, watch two or three weeks of data, and repeat.
| Throughput | Avg cycle time | WIP by Little's law |
|---|---|---|
| 5 per week | 5 days | 5 |
| 10 per week | 4 days | 8 |
| 10 per week | 10 days | 20 |
| 3 per week | 10 days | 6 |
Questions
What is Little's law?
In a stable process, the average number of items in progress equals the average arrival rate times the average time an item spends in the system. For a team this means WIP = throughput x cycle time, which is why shortening the queue shortens the wait.
How do I calculate a WIP limit for a Kanban board?
Take your average weekly throughput, convert it to items per working day, and multiply by your average cycle time in working days. Round up, then try that number across your in-progress columns and adjust after a few weeks of data.
Should I use average or 85th percentile cycle time?
Use the average for the WIP number, since Little's law is about averages. Use the 85th percentile when you promise a delivery date, because it tells you how long 85 out of 100 items take.
What is a good WIP limit per person?
Many teams start at one to two items per person and tune from there. If your calculated limit is far above that, items are probably waiting between steps, and a lower limit will show where.
Why does the calculator say to add a buffer?
Work arrives and finishes unevenly, so a limit equal to the exact average blocks people often. A buffer of 10 to 25 percent leaves room for that variation while still keeping the queue short.