Practice : WIP and Throughput Limits

Purpose and Strategic Importance

WIP and Throughput Limits help teams optimise delivery flow by reducing multitasking, context switching, and system overload. By intentionally limiting the amount of work in progress and monitoring throughput, teams improve focus, reduce delays, and deliver value more predictably.

Without WIP and throughput limits, teams risk overloading the system, creating hidden queues, and generating friction that slows delivery, increases errors, and undermines system stability.

Description of the Practice

  • Teams establish explicit limits on the amount of work in progress (WIP) at each stage of their delivery process.
  • Throughput, the rate at which work is completed, is monitored to ensure sustainable, predictable delivery.
  • WIP limits trigger team-level conversations about priorities, blockers, and flow bottlenecks.
  • Limits are adjusted over time based on team capacity, delivery patterns, and system health.

How to Practise It (Playbook)

1. Getting Started

  • Visualise the team's delivery process using a board or equivalent tool.
  • Identify stages of work where WIP limits will apply (e.g. development, testing, review).
  • Set initial limits based on team size and observed delivery patterns.
  • Monitor throughput and flow metrics to assess impact.

2. Scaling and Maturing

  • Use WIP limit breaches as a signal for improvement, not blame.
  • Continuously adjust limits based on capacity, system constraints, and delivery goals.
  • Track trends in throughput, cycle time, and flow efficiency over time.
  • Integrate WIP discussions into daily stand-ups, retrospectives, and planning.

3. Team Behaviours to Encourage

  • Focus on finishing work, not starting new tasks.
  • Raise blockers and bottlenecks proactively when limits are breached.
  • Treat WIP limits as a system constraint, not a personal performance metric.
  • Collaborate to optimise flow rather than maximise individual utilisation.

4. Watch Out For…

  • WIP limits that are unrealistic or ignored.
  • Limits used to blame individuals rather than improve the system.
  • Teams artificially limiting work without addressing underlying flow issues.
  • Lack of throughput monitoring to balance flow with delivery pace.

5. Signals of Success

  • Teams consistently respect WIP limits, using them to optimise delivery flow.
  • Throughput becomes more predictable and sustainable.
  • Bottlenecks and blockers are identified and resolved quickly.
  • Teams report improved focus, reduced context switching, and higher delivery confidence.