Standard : Throughput

Description

Throughput is the number of work items completed within a defined period. It provides a quantitative measure of delivery pace and is one of the most critical indicators of system performance in Lean and Agile environments.

High and stable throughput reflects a well-functioning flow system. Variability or sudden drops in throughput can signal issues like overburden, unclear priorities, or systemic blockers.

How to Use

What to Measure

  • Count all completed work items in a given time window (e.g. weekly, bi-weekly).
  • Optionally segment by work type (feature, bug, enabler, tech debt).
  • Measure at team, programme, or portfolio levels.

Formula

Throughput = Number of Completed Work Items / Time Period

You can also track:

  • Throughput Trend: Rolling average or variation over time.
  • Work Type Mix: Ratio of features vs. bugs vs. enablers.
  • Throughput per Person: As a directional capacity signal (not a performance metric).

Instrumentation Tips

  • Use delivery board state transitions (e.g. “Done”) for counting.
  • Tag items clearly by work type for breakdown analysis.
  • Automate data capture with dashboards and visual trend lines.
  • Exclude trivial or automated items to maintain relevance.

Why It Matters

  • Measures pace of delivery: Helps understand what the team can achieve over time.
  • Informs forecasting: Enables better estimation and planning with historical data.
  • Supports flow improvements: Pairs with cycle time to reflect efficiency and predictability.
  • Surfaces imbalance: Uncovers whether too much reactive or technical work is being done.

Best Practices

  • Review throughput regularly in retrospectives and planning sessions.
  • Visualise rolling averages and trends to reduce overreaction to short-term dips.
  • Use throughput insights to adjust WIP limits, staffing, or scope.
  • Pair with cycle time and flow load for a holistic view of system flow.
  • Keep conversations focused on flow, not individual productivity.

Common Pitfalls

  • Using throughput as a performance KPI for individuals (leads to gaming and stress).
  • Failing to normalise for team size or sprint duration when comparing across teams.
  • Tracking only feature throughput and ignoring enablers or defects.
  • Ignoring variability and treating throughput as fixed capacity.

Signals of Success

  • Throughput trends are stable or improving with low variance.
  • Teams use throughput data to support flow-based forecasting.
  • Teams complete work across different types, maintaining healthy balance.
  • Predictable delivery increases stakeholder confidence.
  • [[Cycle Time]]
  • [[Work Item Age]]
  • [[Flow Load]]
  • [[Flow Efficiency]]
  • [[Delivery Predictability]]