Work in progress (WIP) is the flow metric most directly under your team’s control, and it is often the single fastest lever for delivering faster. Also called flow load, it counts how many items you have started but not yet finished at any moment. This guide explains what WIP is, how Flow Metrics Charts for Jira Cloud measures it, why high WIP quietly destroys delivery speed, and how to use WIP limits and Little’s Law to fix it.
What is work in progress (flow load)?
Work in progress is the number of work items that are actively in flight — started but not yet done — at a given point in time. In flow-metrics terms it is called flow load, because it measures how much your delivery system is carrying. Unlike lead time or throughput, which look backward at completed work, WIP is a snapshot of the present: how much you are trying to do at once.
Why high WIP silently kills delivery speed
It is the most counter-intuitive truth in Lean delivery: starting more work makes everything slower. When a team starts more than it finishes, items pile up in queues, context-switching multiplies, and each item takes longer to reach done — even though the team is busier than ever. High WIP is the hidden cause behind ballooning lead time and stalled delivery, and it rarely shows up until you measure it.
Little’s Law: the math behind WIP
The relationship is captured by Little’s Law, one of the few genuinely reliable laws in software delivery:
Average lead time ≈ average work in progress ÷ average throughput.
A worked example makes it concrete. A team with 24 items in progress that completes 8 items per week has an average lead time of about three weeks (24 ÷ 8). Cut WIP to 16 items without adding a single person, and lead time drops to two weeks (16 ÷ 8). You delivered the same throughput, faster, simply by carrying less at once. This is why teams that “stop starting and start finishing” speed up without working harder or hiring.
How flow load is measured in Jira
Flow Metrics Charts counts the items currently in active statuses for your chosen data source. It is visualized with a cumulative flow diagram (CFD): the vertical band between “started” and “done” is your WIP, and a band that widens over time is a red flag that you are starting faster than you are finishing. A stable, parallel CFD means work arrives and departs at the same rate — a system in control.
How to read the WIP chart and CFD
- A widening band means WIP is growing — arrivals outpace departures, and lead time is about to climb.
- A flat or narrowing band means the team is finishing what it starts — the goal.
- Sudden vertical jumps often mark bulk starts (a whole sprint pulled in at once) that will stretch cycle time.
- Compare WIP to throughput. If WIP is many times your weekly throughput, most items are sitting idle rather than being worked.
How to set WIP limits that work
A WIP limit is a deliberate cap on how many items can be open in a stage at once; when the limit is hit, the rule is to finish something before starting anything new. Practical guidance:
- Start from today’s reality. Set the first limit near your current average WIP, then lower it gradually — a shock cap creates rebellion, not flow.
- Limit per column, not just overall, so bottlenecks (often code review or test) become visible.
- Make finishing the priority. When the limit blocks a new start, swarm the nearest-to-done item instead.
- Expect cycle time to fall. Studies of Kanban teams applying WIP limits report cycle-time reductions of roughly 20–30%.
How flow load connects to the other flow metrics
Flow load is the lever; the others are the result. Because of Little’s Law, reducing WIP shortens flow time at the same throughput, and steadier flow improves system stability and predictability. When delivery feels slow, reducing work in progress is almost always the first lever to pull.
Track work in progress in Jira
Flow Metrics Charts for Jira Cloud builds your cumulative flow diagram and WIP trend directly from Jira status history — no manual tagging or spreadsheets — on an interactive board and in dashboard gadgets, with Rovo AI flagging when your WIP band starts to widen. Start with the flow metrics for Jira overview, or read the canonical explainer, Flow Metrics Explained.
Frequently asked questions
What is work in progress (WIP)?
WIP is the number of items that have been started but not yet finished at a given moment. In flow metrics it is called flow load, and it is the amount of work your delivery system is carrying at once.
How does WIP affect cycle time?
They are linked by Little’s Law: average lead time is approximately WIP divided by throughput. Holding throughput constant, higher WIP means longer cycle and lead times, which is why WIP limits speed up delivery.
What is a good WIP limit?
There is no universal number. Start near your current average WIP, limit work per stage, and lower the cap gradually while watching cycle time fall. The right limit is the lowest one the team can sustain without starving.
What is a cumulative flow diagram?
A cumulative flow diagram (CFD) plots the count of items in each status over time. The band between started and done shows WIP; a widening band signals growing work in progress and rising lead time.
1 Comment
Leave your reply.