AI Leader · Solution Architect · TPM

Skip to main content

Plan · Delivery

Sprint Capacity & Delivery Confidence Calculator

Turn capacity, focus factor, and interrupt load into a confidence band for the sprint.

Honest delivery confidence from hours, meetings, and interrupts — not story-point theater.

How it works

  1. Enter team size, sprint length, hours/day, meeting load, focus factor, and interrupt load.
  2. Add committed points and historical velocity — capacity vs commitment and confidence update live.
  3. Use the cut-line suggestion in planning; unlock Print / Save as PDF with a work email when ready.
Sprint inputs

Honest inputs beat optimistic calendars. Defaults are a starting point.

How the model works

  1. Gross hours = team size × sprint days × hours/day.
  2. After meetings = gross × (1 − meeting %).
  3. After interrupts = after meetings × (1 − interrupt %).
  4. Available capacity = after interrupts × focus factor.
  5. Commitment load compares committed points to historical velocity and maps load onto capacity (points-per-hour implied by velocity ÷ typical capacity).
  6. Confidence: High when commitment ≤ ~90% of velocity and capacity is comfortable; Medium when tight; Low when overcommitted — suggest a cut-line.

All math runs in your browser. Prefer cutting scope early over heroic overtime.

Unlock printable capacity summary

Work email unlocks Print / Save as PDF. Same subscribe flow as the newsletter.

FAQ

How is available capacity calculated?

Gross hours = team size × sprint days × hours/day. Then subtract meeting load and interrupt load, and apply focus factor. Result is available capacity hours for committed work.

What is focus factor?

Focus factor is the share of remaining time that is truly deep work (typically 0.6–0.85). Lower focus means less delivery capacity even if calendars look open.

How is delivery confidence decided?

We compare committed points to historical velocity and to capacity vs commitment %. High ≈ comfortably under capacity and near velocity; Medium ≈ tight; Low ≈ overcommitted — cut scope.

What is the cut-line suggestion?

When commitment exceeds a safe band of historical velocity (or capacity is thin), the calculator suggests how many points to cut so the sprint lands in a Medium/High confidence band.

Should I use points or hours?

Capacity is hour-based; commitment uses your team’s story points and velocity. Keep both honest — padding points while ignoring interrupts creates false confidence.

Are results a guarantee of delivery?

No. This is directional planning. Dependencies, production incidents, and scope creep still move outcomes. Use it for sprint planning honesty, not as a performance scorecard.