• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : WIP is limited to optimise flow and focus

Purpose and Strategic Importance

Limiting Work in Progress (WIP) is essential for maintaining flow, reducing context switching, and ensuring high-quality delivery. This standard ensures that teams focus on completing work before starting new items, creating predictable throughput and improving delivery cadence.

It supports the policies “Make Work Visible and Limit WIP” and “Embrace Iteration over Perfection” by encouraging flow-based thinking and disciplined prioritisation. Excessive WIP creates hidden queues, stalls feedback, and leads to burnout and delivery delays.

Strategic Impact

  • Reduces delivery lead times and increases predictability
  • Enhances team focus and quality by minimising context switching
  • Supports faster feedback cycles and value realisation
  • Makes delivery bottlenecks visible for improvement
  • Reinforces sustainable flow and planning discipline

Risks of Not Having This Standard

  • Teams become overburdened and delivery slows down
  • Quality drops due to multitasking and incomplete work
  • Feedback is delayed, reducing learning opportunities
  • Priorities are unclear, leading to inefficient effort allocation
  • Bottlenecks are hidden, preventing flow optimisation

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Work is started without regard to capacity or completion.
- Multitasking is seen as a sign of productivity.
Process & Governance - No defined limits or work-in-progress policies.
Technology & Tools - Work management tools do not visualise or constrain WIP.
Measurement & Metrics - WIP levels are unknown or unmanaged.

Level 2 – Managed

Category Description
People & Culture - Teams begin to recognise the negative impact of too much WIP.
- Some effort to finish work before starting new items.
Process & Governance - Basic WIP limits introduced for selected stages.
Technology & Tools - Simple visual tools (e.g. boards with WIP indicators) are used.
Measurement & Metrics - Informal tracking of items in progress per person or stage.

Level 3 – Defined

Category Description
People & Culture - Teams commit to respecting WIP limits and swarming to finish work.
Process & Governance - WIP limits applied across full delivery workflow.
- Teams inspect WIP levels in retrospectives and planning.
Technology & Tools - Tools enforce or flag WIP breaches.
Measurement & Metrics - WIP per team, per stage; adherence to WIP limits.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Teams use WIP trends to improve forecasting and capacity planning.
- WIP is actively balanced across teams to maintain flow.
Process & Governance - WIP metrics drive improvement experiments and planning conversations.
Technology & Tools - Analytics dashboards show WIP trends, breach frequencies, and bottlenecks.
Measurement & Metrics - Average vs maximum WIP; WIP breach counts; lead time correlation with WIP.

Level 5 – Optimising

Category Description
People & Culture - WIP discipline is deeply embedded in team behaviour.
- Continuous flow improvement is part of team DNA.
Process & Governance - WIP management is integrated into cross-team coordination and scaling.
- WIP limits are dynamically adjusted based on real-time flow data.
Technology & Tools - Predictive tools suggest optimal WIP levels to maintain delivery efficiency.
Measurement & Metrics - Flow efficiency; time to complete WIP items; WIP limit change effectiveness.

Key Measures

  • Number of WIP items per person, team, and stage
  • Frequency of WIP limit breaches
  • Correlation between WIP level and lead time
  • % of work completed within defined WIP limits
  • Flow efficiency score (active work time vs total elapsed time)
Associated Policies
Associated Practices
  • Minimising Work in Progress (WIP)

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering