Calculators

Sprint Velocity Calculator

Estimate a team's average sprint velocity from completed work across multiple sprints. Enter the story points completed in each sprint to calculate the average points delivered per sprint. This planning measure assumes consistent estimation and sprint length.

Loading calculator...

What this Sprint Velocity Calculator does

The Sprint Velocity Calculator estimates a team's average completed work per sprint using three sprint totals. Its exact calculator description is: “Estimate a team's average sprint velocity from completed work across multiple sprints. Enter the story points completed in each sprint to calculate the average points delivered per sprint. This planning measure assumes consistent estimation and sprint length.” The inputs are Sprint 1 completed story points (points), Sprint 2 completed story points (points), and Sprint 3 completed story points (points). The formula is (sprint_one_points + sprint_two_points + sprint_three_points) / 3, and the result is Average Velocity (points per sprint).

In project planning, velocity is a summary of how much estimated work a team completed during a sprint. The result is expressed in points per sprint. It can help a team discuss capacity and make a rough forecast when the work, estimation approach, and sprint cadence are comparable. It does not measure individual productivity, the value of the work, or the quality of an outcome.

This version averages three sprint totals. It treats each sprint equally and uses only work counted as completed under the team's definition. That makes the calculation straightforward, while leaving the team responsible for deciding whether the three periods are representative enough to inform a planning conversation.

How to use the Sprint Velocity Calculator

Enter the completed story points for each of the three sprints. Use the team's recorded totals and the same completion rule for every sprint. If a sprint had no completed points, enter zero. The allowed range for each input is 0 to 200 points, in whole-point steps. The defaults are example values and can be replaced with the team's own data.

  • Choose three recent sprints with a comparable length and team composition.
  • Enter points for work completed by the sprint boundary according to the team's normal practice.
  • Review the result in points per sprint, then discuss whether unusual events affected the period.

For example, suppose a team completed 24 points in Sprint 1, 27 points in Sprint 2, and 25 points in Sprint 3. Add the totals to get 76 points, then divide by three sprints. The average is 25.33 points per sprint. The units follow the calculation because points are divided by sprints. A forecast based on this figure should be treated as a planning estimate rather than a commitment.

How the Sprint Velocity Calculator formula works

The formula adds the three completed-work totals and divides the sum by three. In symbolic form, average velocity equals (Sprint 1 points + Sprint 2 points + Sprint 3 points) ÷ 3. Each input has the unit points, and the divisor represents the three sprint observations, so the resulting unit is points per sprint.

The arithmetic is a simple mean. Each sprint contributes the same weight, whether its total is higher or lower than the others. If the values are 24, 27, and 25, the sum is 76 and 76 ÷ 3 = 25.33. The displayed result uses two decimal places, which helps show the arithmetic precisely. It does not mean the team should plan fractional story points.

Story points are team-defined estimates. Their meaning depends on the team's own reference examples and estimation habits. The calculator does not convert points into hours, tasks, people, or a universal measure of effort. Comparing point totals across different teams can be misleading because each team may use a different scale.

Use cases for the Sprint Velocity Calculator

A team can use its average velocity as one input to a backlog discussion. If a planned sprint contains substantially more estimated points than the recent average, the team can inspect the work and discuss whether the scope fits. If the planned amount is lower, that may leave room for support work, investigation, or uncertainty, depending on the team's context.

Project leads may use the average to support a rough capacity conversation over several upcoming sprints. For instance, a backlog of 100 points divided by an average of 25 points per sprint suggests about four sprints of work under the same assumptions. That rough division does not account for dependencies, changes in scope, holidays, defects, or new information. It should be revisited as the project progresses.

The calculation can also prompt a retrospective discussion. A changing average can lead the team to review whether work was interrupted, stories were split differently, membership changed, or the definition of done was applied consistently. The number provides a starting point for inquiry. It does not explain the reason for a change by itself.

Other factors to consider when calculating sprint velocity

Velocity is most useful when the measurement is consistent over time. Keep sprint duration stable when possible, and use the same point scale and completion criteria. A changed team structure or estimation practice can make historical averages less representative. Mark those changes in planning notes so later readers understand the context.

Completed work should be counted consistently. Teams vary in how they treat partially finished stories, work carried forward, or items that meet most but not all acceptance criteria. Decide on a clear rule and apply it across the input periods. Counting unfinished work as complete can make the average look higher while leaving the team with work still to finish.

Three sprints provide a small sample. A production incident, a large absence, onboarding, or an unusually research-heavy period may shift the mean. For a more stable internal view, teams can calculate averages over a longer period or compare the three individual sprint totals alongside the average. This calculator remains a three-sprint worksheet-style model and does not select a representative period automatically.

Use velocity to support planning, not as a target for individuals or as a reward measure. Pressure to increase the number can change estimation behavior or encourage splitting work differently without improving delivery. Pair the number with conversations about quality, customer outcomes, sustainable pace, and risks. The arithmetic describes past completed estimates, while the team decides what that history means for future work.

Frequently asked questions

What does sprint velocity mean?

Sprint velocity is the total estimated work a team completed during a sprint, commonly recorded in story points. An average across sprints summarizes past completion under the team's own estimation conventions.

Why does this calculator use three sprints?

Three periods provide a simple recent sample while keeping the inputs manageable. Teams can use a longer history for additional context, particularly when individual sprints were unusual. The result only averages the three values entered here.

Should unfinished story points be included?

Use the team's established rule for completed work. Many teams count an item only when it meets their definition of done, then carry unfinished work into a later sprint according to their process. Applying one rule consistently makes the average easier to interpret.

Can I compare velocity between teams?

Point scales and estimation practices are team-specific, so direct comparisons may not be meaningful. Use the calculation to understand one team's history and planning context rather than ranking teams by their totals.

Does the average guarantee how much work a team will finish next sprint?

No. The average is a historical summary, not a guarantee. Incoming work, dependencies, availability, interruptions, and uncertainty can change what a team completes. Use it as one planning reference and update expectations as conditions change.

Written by

facultyproject.org Editorial Team

Editorial team

facultyproject.org publishes practical how-to guides and educational articles with clear steps and useful context.