How Process Variation is Calculated

How Process Variation is Calculated

Overview

Process Variation is our user-friendly name for Coefficient of Variation (CV), a statistical measure of how consistent your team's delivery process is over multiple sprints (or weeks). By analyzing the relative variability of your core flow metrics (Cycle Time, Work in Progress, Throughput), this single metric helps you understand overall process predictability at a glance.

Calculating Process Variation

Step 1: Individual Metric Coefficient of Variation (CV) calculation

For each core flow metric:

  • Cycle Time - How long work items take to complete

  • Work in Progress (WIP) - Number of items being worked on

  • Throughput - Number of items completed per sprint

We calculate the Coefficient of Variation over multiple sprints (or weeks) - typically last six weeks:
CV = Standard Deviation / Mean

Step 2: Weighted Aggregation

With CV calculated for each core metric, the Process Variation combines these individual CVs using the following weights:

Metric

Weight

Rationale

Metric

Weight

Rationale

Cycle Time

40%

Primary driver of delivery predictability directly impacts "when will this be done?”

Work in Progress (WIP)

35%

Leading indicator that controls variation
in other metrics (Little's Law)

Throughput

25%

Important for capacity planning, mathematically connected to WIP and cycle time

Formula for Process Variation:

Process Variation = (Cycle Time CV × 0.40) + (WIP CV × 0.35) + (Throughput CV × 0.25)

Step 3: Predictability Classification

The resulting Process Variation value indicates your process predictability. We use thresholds adapted from statistical forecasting practices:

  • Highly Predictable (< 0.3): Sharp distribution with very consistent delivery process - reliable
    forecasting possible

  • Moderately Predictable (0.3-0.5): Clear trend with some variation - forecasting still viable
    with expected variability

  • Low Predictability (0.5-0.7): More flat distribution with significant variation - forecasting
    becomes difficult

  • Unpredictable (> 0.7): Nearly flat distribution - traditional forecasting methods unreliable

Understanding Coefficient of Variation (CV) Thresholds

These threshold values are adapted from supply chain demand forecasting practices and applied to software development contexts:

  • CV < 0.3: Data points cluster around the mean, creating highly predictable delivery
    patterns that enable reliable sprint planning and forecasting

  • CV 0.3-0.5: Moderate spread in delivery times - teams can still plan effectively but should
    monitor and address sources of variation

  • CV 0.5-0.7: Significant spread indicates process instability - focus on stabilizing core
    metrics before making firm commitments

  • CV > 0.7: Wide, flat distribution makes traditional forecasting methods unreliable - prioritize
    process stabilization over forecasting

Context-Dependent Thresholds

Important Note: These threshold values (0.3, 0.5, and 0.7) are derived from statistical supply chain and demand forecasting literature, not software development research. They should be regarded as starting points to be adjusted based on your organization and team's specific context.

While Coefficient of Variation analysis is increasingly used to assess forecastability in software flow metrics, these specific thresholds require calibration to your team's context rather than being treated as software industry standards.

Calibrating Thresholds for Your Context

Start with the default supply chain-derived thresholds as your baseline, then refine them based on:

  • Your business's tolerance for delivery uncertainty - How much variation can your stakeholders
    actually handle?

  • The consequences of missed delivery predictions - What actually happens when you're off by a
    week? A month?

  • Your team's actual forecasting accuracy over time - Are you consistently hitting your targets
    with current variation?

The goal is achieving the level of process predictability that meets your business needs - no
more, no less. Organizations should balance the costs of increasing predictability against the
benefits it provides in their specific context."

 

 

Further Reading