Practice : Minimising Work in Progress (WIP)

Purpose and Strategic Importance

Minimising Work in Progress (WIP) is the disciplined practice of limiting the number of concurrent work items in play. It supports flow efficiency, improves delivery predictability, and reduces cognitive overload on teams.

By focusing on fewer items at a time, teams finish work faster, improve quality through deeper focus, and surface blockers more effectively. This is a cornerstone of Agile and Lean systems thinking—optimising throughput, not utilisation.

Description of the Practice

  • WIP limits are explicitly agreed and applied to workflow stages (e.g. "In Progress", "Code Review").
  • Teams monitor the number of active stories, tasks, or features at any point in time.
  • Excessive WIP triggers a team response—e.g. swarming, refocusing, or unblocking.
  • Reducing WIP improves flow predictability, increases throughput, and shortens lead time.

How to Practise It (Playbook)

1. Getting Started

  • Visualise all work on a physical or digital board (e.g. Kanban).
  • Identify bottlenecks and places where work regularly piles up.
  • Agree initial WIP limits for each column and monitor them daily.
  • Start by enforcing limits on the most overloaded stages of the process.

2. Scaling and Maturing

  • Use WIP data (e.g. time-in-column) to tune limits over time.
  • Pair WIP limits with pull policies and working agreements.
  • Measure impact on flow metrics such as cycle time and throughput.
  • Use retrospectives to discuss what happens when WIP is exceeded or ignored.

3. Team Behaviours to Encourage

  • Collaborate to finish work before starting new items.
  • Swarm on blocked or high-value items to complete them faster.
  • Reflect on WIP discipline as part of regular team health checks.
  • Prioritise flow and impact over busywork or multi-tasking.

4. Watch Out For…

  • WIP limits becoming symbolic and routinely ignored.
  • Teams resisting swarming due to unclear roles or ownership boundaries.
  • Stakeholders interpreting lower WIP as lower productivity.
  • Bottlenecks shifting to unmonitored queues (e.g. test, deploy).

5. Signals of Success

  • Lead times decrease and become more predictable.
  • Blockers are surfaced and resolved faster.
  • Teams report less context-switching and more focus.
  • Flow metrics are actively used to guide improvement.
  • Sustainable pace improves morale and delivery outcomes.