Sprint Capacity Planner
Calculate realistic team capacity, account for availability and recurring commitments, allocate planned effort across work types and test whether the proposed sprint commitment fits before a capacity shock occurs.
Sprint capacity should reflect the team that will actually be available.
The planner starts with working days and member availability, subtracts known leave and recurring commitments, applies an explicit reserve, then compares net capacity with planned sprint work. It keeps capacity hours separate from story points and uses capacity as an input to team commitment—not as a utilization quota.
Sprint Capacity Planner — Step by Step
Eight locked stages move from sprint context through availability, recurring commitments, reserve, work-type demand, sprint commitment, a capacity shock and management review.
Available Effort, Work Mix and Sprint Commitment
Reveal the sprint context to begin.
See how gross team time becomes net delivery capacity.
Test a Sprint-load Scenario
Experiment Mode is isolated from the guided demonstration. Change team size, sprint length, support demand, reserve and planned work to see how capacity utilization responds.
Test sprint-capacity judgement.
Sprint-capacity planning cues
Gross Team Capacity
Sum of each member's available sprint time after known leave and allocation percentage.
Recurring Commitments
Subtract known Scrum-event time and recurring support or business-as-usual demand.
Reserve
Use an explicit, context-based allowance for normal unplanned work and delivery uncertainty.
Net Capacity
Gross capacity minus recurring commitments, support load and explicit reserve.
Capacity Utilization
Committed workload ÷ net capacity × 100. Higher is not automatically better.
Capacity ≠ Story Points
Do not use a universal point-to-hours conversion. Story points and capacity hours answer different planning questions.
Plan from real availability, subtract known commitments, retain transparent room for uncertainty and revisit scope when capacity or demand changes materially.