VeloWiseengineering delivery intelligence

Sprint Commitment vs Completion: What the Numbers Really Tell You

Comparing what a team committed to with what it completed is one of the most useful planning signals a leader has — if you read the trend rather than the latest sprint.

Part of Engineering Delivery Intelligence: better planning and fewer surprises

For: Engineering managers, directors and Scrum MastersUpdated

This guide answers

  • Is the team completing less, or committing more?
  • What does a widening gap mean?
  • How much should the next sprint commit to?

Four sprints, one pattern

Sprints 20–23 · committed vs completedExample delivery data

Committed Completed

  • Sprint 2060 → 56gap 4
  • Sprint 2165 → 57gap 8
  • Sprint 2272 → 58gap 14
  • Sprint 2378 → 59gap 19

Completed work stayed between 56 and 59 issues per sprint.

Commitment rose 30% in four sprints. Completed work barely moved.

Look at the two series separately. Completed work is almost flat: 56, 57, 58, 59. That is this team’s demonstrated throughput — what it reliably delivers in a sprint. Commitment, meanwhile, climbed from 60 to 78. The gap grew from 4 to 19 issues.

A report that shows only the completion rate would say the team got worse: 93%, 88%, 81%, 76%. The team did not get worse. It delivered slightly more each sprint. The plan drifted away from what the team can do.

Why the completion rate can mislead

Sprints 20–23 · the same data, two headlinesExample delivery data

Completion rate

93% → 76%

  • Reads as declining performance
  • Invites “why is the team slowing down?”
  • Encourages committing to less — or padding estimates

Commitment vs throughput

Committed ↑ · Completed →

  • Throughput steady at 56–59
  • Commitment up from 60 to 78
  • Invites “why are we planning above what we deliver?”

A falling completion rate with flat throughput is a planning problem, not a performance problem.

The completion rate divides two numbers that move for different reasons. Throughput depends on the team, its flow and its interruptions. Commitment depends on planning pressure: roadmap deadlines, optimism, carried-over work that was never re-estimated. Put them in one ratio and you cannot tell which moved.

What usually drives commitment upward

  • Carried-over work added on top of a full plan. The previous sprint’s unfinished issues re-enter, and new work is planned as if they were not there. The sprint carryover guide shows how to see this.
  • Deadline pressure. A date is fixed, so each sprint absorbs a larger share of the remaining work.
  • Planning from estimates instead of history. Story-point capacity looks bigger than what the team has ever delivered.
  • Scope added and never removed. The backlog for the sprint grows; nothing is traded out. See how scope change affects outcomes.
What the next sprint can holdExample delivery data
Next sprint demand24 carried in44 new
Typically completed57 (median, last 6 sprints)

68 issues of demand against 57 typically completed: about 11 more than the team has recently delivered — before any interrupts.

Plan the next sprint from demonstrated throughput, after carried-over work and the usual interrupts — not from the size of the backlog.

Using the numbers to plan the next sprint

Planning the next sprint · from history to a commitmentExample delivery data
  1. 56–59Demonstrated throughputlast four sprints
  2. −11Carried inunfinished from the last sprint
  3. −8Usual mid-sprint additionstypical growth to leave room for
  4. ≈ 38New work to commitplus the carried-in issues

Start from what the team has delivered, then subtract what is already spoken for.

A realistic commitment starts from the throughput range, subtracts work that is already in flight, and leaves room for the scope growth the team usually sees. The result is often smaller than the roadmap wants. That gap is exactly the information leadership needs before the sprint starts — not after it ends.

The difference between “we’ll commit to 78” and “we can complete about 58; the roadmap needs 78; here are the 20 issues that will slip unless we change something” is the difference between a surprise and a decision.

Presenting the gap to leadership

Leaders do not need the chart every sprint; they need the conclusion and the decision. A useful format:

Example · Planning note for leadership

Over the last four sprints we have completed 56–59 issues per sprint, while commitments rose from 60 to 78.

This sprint we are committing to about 49 issues: 11 carried over from last sprint and 38 new. The roadmap items that do not fit are listed below, so we can decide now what moves.

This keeps the discussion on trade-offs rather than effort, and it sets an expectation leadership can plan around. It also gives the sprint progress update a baseline to report against mid-sprint.

See this in VeloWise: Capacity and commitment

Historical throughput ranges, carried-in work and typical scope growth, with a simulator to test a proposed commitment before the sprint starts.

Open Capacity and commitmentHow capacity and commitment works

Works with the sample project or your own data. VeloWise currently imports delivery data from delivery data exports.

Go deeper

Frequently asked questions

What is a good commitment-to-completion ratio?
Consistency matters more than a number. A team that completes 85–95% of a realistic commitment sprint after sprint is more predictable than one that swings between 60% and 100%.
Should we measure commitment in story points or issues?
Either, as long as you are consistent and compare the team to its own history. Issue counts are simpler to explain and harder to inflate; points help when issue sizes vary widely.
Does a widening gap mean the team is underperforming?
Not if completed work is stable. A widening gap with flat throughput usually means the plan is growing faster than the team’s capacity. Check commitment and throughput separately.

All engineering delivery guides