Standard : Throughput Rate (Items Completed per Sprint or Week)

Description

Throughput Rate measures the number of work items completed within a specific time window, typically per sprint or week. It gives teams a clear picture of how much work is flowing through the system and being delivered.

This is a foundational flow metric used to understand team capacity, forecast future delivery, and evaluate changes in productivity. It is particularly powerful when combined with other metrics like cycle time and WIP.

How to Use

What to Measure

  • Count the number of completed work items within each fixed time period (e.g. weekly or per sprint).
  • Include only items that meet the “Definition of Done” and are in a fully completed state.
  • Optionally break down throughput by item type (e.g. story, bug, spike).

Formula

Throughput Rate = Number of Completed Items / Time Period

You can track:

  • Weekly throughput (for continuous delivery teams)
  • Sprint throughput (for scrum teams)
  • Rolling average throughput over multiple sprints or weeks

Instrumentation Tips

  • Use delivery tools (e.g. Jira, Azure DevOps) to filter completed items by date range.
  • Maintain consistency in work item size or use complementary metrics like cycle time to normalise throughput trends.
  • Visualise throughput using bar charts or time series plots.

Benchmarks

Benchmarks are specific to each team and depend on:

  • Item size and granularity
  • Team size and maturity
  • Degree of flow interruption (e.g. context switching, blockers)

Instead of comparing across teams, monitor:

  • Your team’s trend over time
  • Stability of throughput per period
  • Deviation during holidays, incidents or staffing changes

Why It Matters

  • Measures delivery capacity
    Helps teams understand how much value they can deliver over time.

  • Supports forecasting
    Provides input for Monte Carlo simulations and empirical planning techniques.

  • Highlights changes in flow
    Drops in throughput may signal bottlenecks, excessive WIP or unplanned work.

  • Builds team awareness and focus
    Encourages completion over starting new tasks and can drive continuous improvement.

Best Practices

  • Track throughput consistently over multiple sprints or weeks.
  • Pair throughput with cycle time to assess flow health.
  • Normalise for work item size if items vary significantly (or aim for similarly sized work).
  • Review spikes and dips to understand underlying causes (e.g. priority shifts, system health).

Common Pitfalls

  • Over-relying on throughput as a productivity proxy without context.
  • Comparing throughput across teams without accounting for different work types or team size.
  • Using story points instead of item count, which introduces estimation bias.
  • Failing to pair throughput with WIP and cycle time, leading to incomplete flow insights.

Signals of Success

  • Stable throughput trends over time, even during varied work.
  • Higher throughput without quality or cycle time degradation.
  • Increased predictability and accuracy in forecasting using historical throughput data.
  • Throughput used in planning conversations rather than velocity or gut feel.
  • [[Cycle Time per Work Item Type]]
  • [[Throughput Rate (Items Completed per Sprint or Week)]]
  • [[Work Item Age]]
  • [[WIP per Team or Stream]]

Aligned Industry Research

  • ActionableAgile (Daniel Vacanti)
    Recommends throughput as one of the core flow metrics for healthy systems.

  • Kanban Method (David J. Anderson)
    Promotes monitoring throughput alongside WIP and cycle time to improve system performance.

  • Accelerate (Forsgren et al.)
    Uses delivery throughput and lead time to benchmark software delivery performance across teams.