Sprint Velocity Calculator
Sprint velocity is the most important metric for release forecasting in agile development. By tracking how many story points your team completes in each sprint and calculating the average, you can predict how many more sprints are needed to finish the remaining backlog. This calculator accepts story points completed for up to 8 sprints, computes average velocity, identifies your minimum and maximum, and uses the average to forecast how many sprints you need to deliver a given backlog of story points. Velocity is a planning tool - it is a historical average, not a performance target or quota.
Velocity calculation formula
average_velocity = sum(SP per sprint) / number_of_sprints
sprints_needed = remaining_SP / average_velocity
conservative_sprints = remaining_SP / min_velocity
Velocity tracking guidelines
- Only count story points for stories that are fully completed and accepted by the Product Owner.
- Partially completed stories do not count toward velocity for the sprint.
- Track velocity separately for each team - do not aggregate across teams.
- Avoid using velocity as a performance metric or target - it will cause teams to inflate estimates.
- Investigate velocity outliers: a particularly high or low sprint usually has an identifiable cause that should be noted.
Frequently asked questions
What is sprint velocity?
Sprint velocity is the average number of story points (or work units) a team completes per sprint, measured over multiple sprints. It is used to forecast how many future sprints are needed to complete the remaining product backlog. Velocity is a team-level metric and not comparable between different teams.
How many sprints of data do I need to calculate velocity?
A minimum of 3 sprints is needed for a meaningful velocity estimate. After 5-8 sprints, the average stabilizes and provides reliable forecasts. New teams have high velocity variance in early sprints; use a conservative (lower) estimate for release planning until velocity stabilizes.
Should I use average velocity or the lowest recent velocity for planning?
For release date commitments (where missing the date has significant business consequences), use the lowest velocity from the past 3 sprints as your conservative estimate. For general roadmap planning, use the rolling average. Some teams use the 10th percentile of recent velocity for risk-adjusted planning.
Why does sprint velocity fluctuate?
Common causes include team size changes, holidays and leave, newly added team members ramping up, sprint scope changes, technical debt spikes, and estimation calibration changes. Track the reasons for velocity outliers and normalize them out before calculating your planning baseline.
How do I use velocity to forecast a release date?
Divide the total remaining story points in the backlog by your average velocity to get the number of sprints needed. Multiply by sprint length in weeks to get the number of weeks until completion. Add buffer for known risks. For example: 300 SP remaining / 40 SP velocity = 7.5 sprints * 2 weeks = 15 weeks.
Official sources
- PMI: PMBOK Guide - Project Management Body of Knowledge.
- IEEE: IEEE 12207 - Software Life Cycle Processes.
Reviewed by the CalculatorHub team, edited by James Graham, 14 June 2026. See our methodology.