Standard : Flow Stability (Variance in Cycle Time or Throughput)

Description

Flow Stability measures the consistency of a team’s delivery performance over time, based on the variance in either cycle time or throughput. It reflects how stable the delivery system is — enabling predictable outcomes, accurate forecasting, and sustainable delivery pace.

High variability means work is flowing unpredictably, which undermines trust in forecasts and increases the likelihood of delivery surprises. Low variability supports high confidence planning.

How to Use

What to Measure

  • Cycle Time Stability: Track the distribution (spread) of cycle times across work items over multiple sprints or weeks.
  • Throughput Stability: Track the number of items delivered per sprint or week and assess fluctuation over time.

Use statistical measures such as:

  • Standard deviation or coefficient of variation (CV)
  • Control chart bands to show flow predictability

Formula

  • Cycle Time CV = Standard Deviation / Mean Cycle Time
  • Throughput CV = Standard Deviation / Mean Throughput

A lower CV means higher flow stability.

Instrumentation Tips

  • Use delivery tracking tools to export cycle time and throughput history.
  • Visualise control charts to detect natural variation vs anomalies.
  • Group by work item type for more meaningful analysis.

Benchmarks

General guidance for Coefficient of Variation (CV):

CV Range Flow Stability Interpretation
< 0.3 Highly stable (excellent predictability)
0.3–0.5 Stable with minor variation
0.5–0.7 Moderate fluctuation, requires improvement
> 0.7 High volatility, system is not predictable

Use historical baselines to compare performance and improve consistency.

Why It Matters

  • Enables reliable forecasting
    Low variability supports accurate predictions with narrower confidence intervals.

  • Supports sustainable pace
    Smooth, repeatable delivery reduces pressure, stress and unplanned work.

  • Highlights delivery system health
    Volatility often indicates hidden bottlenecks, unbalanced WIP, or process weaknesses.

  • Builds trust
    Stakeholders prefer consistent delivery over erratic bursts of output.

Best Practices

  • Limit WIP and manage queues to reduce variability in work delivery.
  • Prioritise flow efficiency over individual task speed.
  • Track flow metrics regularly and inspect for outliers or regressions.
  • Use standard work definitions and stable item sizing to reduce variance.
  • Review changes in process, scope or team structure when variance increases.

Common Pitfalls

  • Focusing on average cycle time or throughput without considering spread.
  • Not segmenting flow data by work type, masking underlying variation.
  • Misinterpreting outliers as normal behaviour.
  • Using stability as an excuse to avoid necessary innovation or experimentation.

Signals of Success

  • Cycle time and throughput remain consistent over time.
  • Forecasting models based on historical data are accurate within a reasonable margin.
  • Delivery surprises decrease, and sprint outcomes become more reliable.
  • Flow stability improves after targeted process changes or interventions.
  • [[Cycle Time per Work Item Type]]
  • [[Throughput Rate]]
  • [[Forecast Accuracy]]
  • [[Sprint Volatility Index]]

Aligned Industry Research

  • ActionableAgile (Daniel Vacanti)
    Emphasises the importance of measuring and reducing flow variability to improve predictability.

  • Accelerate (Forsgren et al.)
    Recommends tracking delivery performance variability to support reliable delivery and adaptive planning.

  • Lean Software Development (Poppendieck & Poppendieck)
    Advocates for consistent, smooth flow as a foundation for lean and predictable delivery systems.