EBM Implementation Blueprint

The Innovation Rate Blueprint

Empirical Capacity Partitioning

Most teams plan their sprints around an average, and that average quietly fails them about half the time. The reason is simple: when you load a sprint to 100% of your average throughput, you've left no room for the work you didn't see coming. Real predictability starts when you stop planning against averages and start partitioning capacity using your own empirical data.

The Failure Of Averages in Agile Forecasting

Planning to your average throughput is a coin flip, and the math says so. If your commitment equals your historical average, you have a 50% probability of finishing it.

Deterministic Planning Error:When a sprint commitment equals average historical throughput, there is a 50% probability the work won't finish.

The missing variable is emergent work, which arrives in every system whether you've planned for it or not: production bugs, urgent maintenance, architectural spikes, shifting priorities. Commit your full capacity to planned features and that emergent work has nowhere to go. It piles up as work-in-progress, fragments focus through context switching, and surfaces as late-stage delays. The fix isn't better estimation, it's drawing an empirical boundary that protects innovative work before the sprint begins — through capacity partitioning and an empirical measure of your Ability to Innovate.

Predictable delivery requires Capacity Partitioning and Empirical A2I.

The Core Metric: Ability to Innovate

Scrum.org defines the Ability to Innovate (A2I) as a key value area: a measure of how much capacity an organization spends delivering new value rather than maintaining what already exists. You can track it without administrative overhead by sorting completed backlog items into two buckets, what we'll call the Item Mix.

1. Innovative Work

Items that expand user value, test new hypotheses, or ship strategic features.

Examples: User Stories, Experiments, Enhancements

2. Emergent Work

Unplanned items that absorb capacity without advancing the roadmap.

Examples: Hotfixes, Spikes, Interruptions

The Innovation Rate Formula

From those two buckets, the Innovation Rate tells you what share of a sprint's completed work actually delivered planned customer value.

{
  "metric": "Innovation Rate",
  "formula": "( Completed Stories / Total Completed Items ) * 100",
  "data_scope": "Past 7 to 10 consecutive sprints",
  "purpose": "Identify what percentage of sprint capacity actually yields new value."
}

The Sorting Method: Probabilistic Planning

Once you have a few sprints of Innovation Rates behind you, you can plan against real confidence intervals instead of a single average. The technique is deliberately simple: sort your historical rates from lowest to highest, and that ordering becomes a cumulative probability distribution you can plan against.

1

Step 1 — Collect and Sort Historical Rates

Start by gathering the Innovation Rates from your last 7 to 10 sprints, then arrange them in ascending order, lowest to highest. That sorted list is the foundation for everything that follows.

2

Step 2 — Select a Target Confidence Level

With your rates sorted, decide how much risk you're willing to carry. Rather than defaulting to the coin-flip average, map your commitment to a confidence range drawn from the sorted rates:

  • 90% Confidence (Safe) — for high-stakes commitments you can't afford to miss.
  • 85% Confidence (Recommended) — the standard professional benchmark.
  • 75% Confidence (Stretch) — for stable, low-interruption, high-trust environments.
  • 50% Confidence (Average) — the coin flip. Don't plan here.
3

Step 3 — Partition Sprint Capacity

Finally, turn that confidence rate into a plan. Multiply it by your planned sprint throughput to size the innovative work, then leave the remainder as **empirical slack** to absorb whatever emerges.

Interactive Sprint Calculator

See the Sorting Method in action. Adjust the completed items below to watch the live percentiles adapt and partition capacity dynamically.

Live Simulation

The 7-Sprint Empirical Sorting Widget

Adjust the completed items below and watch the Sorting Method re-order your rates in real time and project your exact Sprint Experiment Size.

Sprint (Completed Items)Innovation Rate
S19
Stories
12
Emergent
3
80.0%12 / 15 items
S20
Stories
15
Emergent
7
68.2%15 / 22 items
S21
Stories
10
Emergent
6
62.5%10 / 16 items
S22
Stories
13
Emergent
5
72.2%13 / 18 items
S23
Stories
8
Emergent
5
61.5%8 / 13 items
S24
Stories
9
Emergent
4
69.2%9 / 13 items
S25
Stories
9
Emergent
1
90.0%9 / 10 items

Sorted Probabilistic Innovation Rates

90% ConfidenceHighly Safe
61.5%
85% ConfidenceCommitment
Recommended Target
62.5%
75% ConfidenceModerate Stretch
62.5%
50% ConfidenceCoin Flip / Average
69.2%

Predictable Experiment Size Planner

Enter your overall planned Sprint Throughput (e.g. 12 items). The planner allocates capacity empirically using your 85% confidence rate.

Innovative Stories8Value & Experiments
Reserved Slack4Bugs & Interruptions

The Empirical Sprint Planning Playbook

Copy this Markdown template into team documentation to guide planning sessions:

empirical-sprint-planning.md
# Facilitation Guide: Empirical Capacity Partitioning

## Phase 1: Establish Throughput
- Check the historical sprint throughput of the past 7 to 10 sprints.
- Agree on the upcoming planned throughput.

## Phase 2: Select Innovation Rate Target
- Sort the historical Innovation Rates in ascending order.
- Select the 85% confidence rate.

## Phase 3: Capacity Partitioning
- Multiply the planned throughput by the 85% confidence rate to determine the innovative story count.
- Subtract the innovative story count from the planned throughput to determine the reserved slack.

## Phase 4: Sprint Backlog Commitment
- Pull the calculated number of innovative stories into the sprint backlog.
- Leave the remaining throughput slots empty to absorb emergent bugs, spikes, and support interruptions.

Three Strategies for Delivery Excellence

The partition only holds if you protect it. Three habits keep the Innovation Rate high:

1. Control WIP

High work-in-progress limits multiply context switching and breed late-stage bugs and rework. Tightening active WIP raises your predictable Innovation Rate.

2. Swarm on Interruptions

When emergent work hits, don't hand it to one person in isolation. Swarm on it collaboratively to clear the blocker fast, protect the sprint goal, and keep flow intact.

3. Plan for Slack

A sprint planned to 100% of theoretical capacity has no defense against disruption. Math-based slack is that defense.

Empirical Implementation Guidelines

It comes down to a repeatable rhythm. During planning, sort each completed sprint into innovative and emergent work, use the Sorting Method to set your commitment at 85% confidence, and let the data do what guesswork can't. Partitioning capacity this way builds a delivery system that sustains itself, and protecting the team's focus pays back as higher engagement, stronger collaboration, and more room to innovate.

Explore Professional Tools