In 30 seconds
- WIP = items in progress at any moment.
- More WIP means longer lead times.
- Limit it to finish faster.
Why too much WIP hurts
- Longer lead times, via Little's Law
- Context switching between tasks
- Delayed feedback, so problems are found late
- Half-done work that delivers no value
Measuring it
Count items in all "in progress" states on the board each day. A cumulative flow diagram shows WIP over time as band thickness.
Reducing it
Set WIP limits, finish before starting, and swarm on stuck items. "Stop starting, start finishing" sums it up.
Myth vs reality
Myth · High WIP shows the team is busy and productive.
Reality · It usually means work is stuck.
Myth · Multitasking is efficient.
Reality · Switching costs eat time and focus.
Myth · WIP only matters in Kanban.
Reality · It slows any team, including Scrum teams.
FAQ
What's a healthy WIP level?
Often around one item per person or less.
Does WIP include waiting items?
Yes, anything started and not done.
How do we lower WIP without idle people?
Have them help finish existing work.