Sprint Capacity Calculator
Estimate story-point capacity across planned sprints for sprint story points.
How to use Sprint Capacity Calculator
1. Enter Team Velocity, Number of Sprints in the labelled units. 2. Velocity is a non-negative assumption from the same team and point scale. Team availability and performance can change; this is a simple forecast. Story points are a team planning scale, not hours or individual productivity. These constant-velocity calculations are forecasts, not delivery promises or Scrum requirements. 3. Select Calculate or press Enter to see the result. 4. Select Select Copy result to copy the answer, or Reset to clear the form.
Why use this tool?
Use this tool to estimate story-point capacity across planned sprints for sprint story points. Use the same team, estimation scale and completion definition when choosing a recent velocity.
How the calculation works
Capacity = entered team velocity × whole number of sprints. Velocity is a non-negative assumption from the same team and point scale. Team availability and performance can change; this is a simple forecast. Story points are a team planning scale, not hours or individual productivity. These constant-velocity calculations are forecasts, not delivery promises or Scrum requirements. Numeric results use up to six decimals, with scientific notation for tiny nonzero values. Fractional averages and capacity are equivalents; allocate whole items and remainders separately when appropriate. Entered decimal arithmetic is applied before display rounding. Numeric inputs/results and durations in seconds are bounded by magnitude 9,007,199,254,740,991. Forecast context: https://scrumguides.org/scrum-guide.html
Example
Sprint Backlog example: An assumed 30 story points per sprint × 4 sprints = 120 story points.
Practical tip
Use the same team, estimation scale and completion definition when choosing a recent velocity.
Frequently asked questions
What does this sprint capacity calculator calculate?
Capacity = entered team velocity × whole number of sprints. Velocity is a non-negative assumption from the same team and point scale. Team availability and performance can change; this is a simple forecast. Story points are a team planning scale, not hours or individual productivity. These constant-velocity calculations are forecasts, not delivery promises or Scrum requirements.
Which assumptions matter for sprint story points?
Story points are a team planning scale, not hours or individual productivity. These constant-velocity calculations are forecasts, not delivery promises or Scrum requirements. Use the same team, estimation scale and completion definition when choosing a recent velocity.
How are units and rounding handled?
Numeric results use up to six decimals, with scientific notation for tiny nonzero values. Fractional averages and capacity are equivalents; allocate whole items and remainders separately when appropriate.