b2KIT

Capacity Planning Calculator

Calculate team capacity with sprint velocity, planned time off, and buffer allocation for accurate sprint/iteration planning.

Tested tool guide Tested browser tools Checked August 16, 2026

What Capacity Planning Calculator does and how it behaves

Sprint velocity alone can overstate what a team should plan when the next iteration includes vacations, holidays, training, or expected interruptions. This calculator combines a velocity baseline with planned time off and a reserved buffer to produce an adjusted sprint capacity. The result remains in the same work unit as the entered velocity. A common mistake is treating velocity as staff-hours: if velocity is measured in story points, the calculated capacity is also expressed in story points, not hours.

How the result is produced

1

Velocity baseline

Enter the sprint velocity that represents the team's completed work in its established unit, such as story points or another consistently tracked measure. This value provides the starting capacity for the iteration. A velocity drawn from several comparable sprints is generally more representative than a single unusually productive or disrupted sprint.

2

Availability adjustments

Planned time off reduces the availability represented by the velocity baseline, while buffer allocation reserves part of the remaining capacity for interruptions or unplanned work. The calculator reports the resulting amount available for planned sprint work. Keep time-off and buffer assumptions separate so that the same expected absence or interruption is not deducted twice.

Good uses

  • Set a planning target for a sprint that overlaps team vacations, company holidays, or scheduled training.
  • Compare alternative buffer allocations before deciding how much backlog work to bring into an iteration.
  • Adjust a team's historical velocity when the upcoming sprint has less working availability than its recent sprints.

Limits and checks

  • Velocity and adjusted capacity share a work unit. A result based on story-point velocity cannot be read as hours or person-days.
  • Planned time off and buffer allocation describe different reductions. Including the same disruption in both inputs understates usable capacity.
  • Historical velocity is evidence from earlier sprints, not a guarantee. Team changes, dependencies, and unusually complex work can make the next result differ.

Common questions

Should sprint velocity be entered as story points or hours?

Use the unit in which the team actually records completed sprint work, and interpret the output in that same unit. Story points are suitable when the velocity history is in story points; hours are suitable only when the baseline is genuinely tracked in hours. The calculator does not make story points and hours interchangeable.

Is the adjusted capacity a firm sprint commitment?

No. It is a planning figure based on the supplied velocity, time-off assumptions, and buffer. It cannot account for every dependency, production incident, estimation error, or change in team composition. Use it to size a plausible workload, then review the selected work against current risks and the team's judgment during sprint planning.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools