WIP limits and Little's law: ship faster by starting less
· 4 min read
Most teams that feel slow are not short of effort. They have too much work started. There is a formula for this, and it is one of the few in software delivery that reliably holds.
Little's law
Average cycle time = work in progress ÷ throughput.
- Work in progress (WIP): the number of items started but not finished.
- Throughput: the number of items finished per unit of time.
- Cycle time: how long an item takes from start to finish.
A team with 24 tickets in progress that finishes 6 a week has an average cycle time of four weeks. This is arithmetic, not a judgment on the team. And since throughput is hard to change quickly, the lever within reach is WIP.
A worked example
The same team limits WIP to 12. Throughput stays near 6 a week, because the same people are doing the same amount of work. Average cycle time falls to two weeks. Customers get each fix in half the time, with no additional effort from anyone.
It feels wrong, because starting work feels like progress. But an item that is started and waiting delivers nothing. Value arrives only when something finishes.
Why high WIP hurts beyond the formula
- Context switching: every extra item in flight costs attention.
- Late feedback: problems are found weeks after the work was done, when the context has gone.
- Hidden bottlenecks: when everyone is busy, nobody can see where work is actually stuck.
- Stale work: branches drift, requirements change, and rework grows.
Find the bottleneck
Look at where items pile up. If eleven tickets are waiting for review, review is the constraint, and writing more code only lengthens that queue. The fix is to make the constrained step the priority: review before starting something new. Once it clears, the bottleneck will move, and you repeat the exercise.
How to introduce WIP limits
- Count your current WIP and set the first limit slightly below it. Do not start with a dramatic cut.
- Set limits per stage — in progress, in review — rather than one number for the whole board.
- Agree the rule: when a column is full, help finish something before pulling new work.
- Lower the limit gradually, and watch cycle time rather than how busy people look.
Expect discomfort in the first weeks. Someone will have nothing to pull and will want to start a new ticket. The limit exists for that moment: the right move is to review, test or unblock something already in flight.
