# Work in Progress

Work in progress is the number of work items that have crossed the workflow's start point but have not yet crossed its finished point.

- Type: metric
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/work-in-progress/>)

## What it means

Work in progress, or WIP, is the count of items currently between a workflow's defined start and finish points. It includes items being actively worked, waiting, blocked, reviewed, or otherwise unfinished inside that boundary. A WIP limit or control expresses how many items may occupy a workflow or state at once.

## Why it matters

Excess WIP spreads attention, increases queues and aging, hides blocked work, and delays feedback. Explicit control encourages people to finish before starting more and makes capacity constraints visible. The goal is not universally minimal WIP, but a sustainable level that supports flow, quality, responsiveness, and necessary collaboration.

## When to use it

Track WIP whenever work moves through a multi-step system and demand can exceed completion capacity. Apply controls where queues form or where scarce review, design, testing, or approval capacity is repeatedly overloaded. Include explicit exception policies for urgent work rather than silently bypassing the control.

## How it works

1. Define start, finish, intermediate states, and which item types belong to the workflow.
2. Count every unfinished item within the boundary, including blocked and waiting work.
3. Set an initial system or state-level control based on current capacity and observed flow.
4. When the control is reached, collaborate to finish, unblock, or swarm before selecting another item.
5. Review WIP, aging, throughput, and cycle time together and adjust policies through experiments.

## A practical example

A product team has eight changes in development and nine awaiting code review. It sets a review-state limit of five and agrees that developers will review or pair when the limit is reached. The visible constraint changes daily choices: fewer changes are started, review queues shrink, and older items receive attention earlier.

## Where it breaks

A number alone does not create flow; teams need authority and skills to resolve constraints. Limits set too low can starve specialists or prevent sensible parallel discovery, while loose limits change nothing. Hidden work, oversized items, and exceptions undermine the signal. WIP control also cannot repair chronically insufficient capacity by itself.

## Common mistakes

- Excluding blocked or waiting items from WIP even though they remain unfinished inside the boundary.
- Treating a limit as a target to fill rather than a maximum that triggers different behavior.
- Raising the limit whenever it becomes uncomfortable instead of investigating the underlying queue.

## Sources

1. [The Kanban Guide \(May 2025\)](<https://kanbanguides.org/the-kanban-guide/>) — Kanban Guides · Official guide
2. [Best Practices for Agile Project Management](<https://learn.microsoft.com/en-us/azure/devops/boards/best-practices-agile-project-management?view=azure-devops>) — Microsoft Learn · Technical guidance

## Related topics

- [Cycle Time](<https://wiki.soroush.uk/topic/cycle-time/>)
- [Throughput](<https://wiki.soroush.uk/topic/throughput/>)
- [Cumulative Flow Diagram](<https://wiki.soroush.uk/topic/cumulative-flow-diagram/>)
