What the Sprint Velocity Calculator does
The Sprint Velocity Calculator estimates how much work a team completes in an average sprint. It divides the total story points completed across several sprints by the number of sprints in that period. The result is expressed in story points per sprint, which gives a team one simple reference for discussing upcoming work.
For example, if a team completed 60 story points across three sprints, its average velocity is 20 story points per sprint. The calculation describes completed work from the period entered. It does not tell a team how many points it must accept next, or promise that a future sprint will finish the same amount.
Velocity is most useful as an internal planning measure for a team that estimates work consistently. Story points are relative estimates chosen by the team. They are not standardized units, elapsed hours, or a way to compare one team’s performance with another’s. This calculator does not assess the quality, value, or difficulty of the completed work.
How to use the Sprint Velocity Calculator
Enter the total story points completed during a selected set of sprints, then enter how many sprints are included. Use the same team and a consistent definition of completed work for both inputs. The calculator divides the first value by the second and returns the Average Velocity.
- Add completed points. Sum the story points for work that met the team’s agreed completion criteria during the period. Avoid counting unfinished items as completed.
- Count the sprints. Enter the number of completed sprints covered by that total. The allowed range is one to twelve.
- Read the average. The result is points per sprint. Keep the displayed decimal places for arithmetic clarity, but use sensible judgment when discussing work items, which may be estimated in whole points.
Suppose a team finished 60 points across three sprints. Enter 60 for total completed story points and 3 for the number of sprints. The calculation is 60 ÷ 3, producing an average velocity of 20 story points per sprint.
Choose a period that reflects the team’s current way of working. A longer period can smooth out a sprint affected by unusual circumstances, while a shorter period can reflect recent changes sooner. The number alone does not explain why output changed, so review the underlying work and conditions with it.
How the Sprint Velocity Calculator formula works
The formula is total completed story points ÷ number of sprints. In symbols, average velocity equals completed_points divided by sprint_count. The calculator requires at least one sprint, so the denominator cannot be zero. Its result label, Average Velocity, describes an arithmetic mean rather than a forecast of guaranteed capacity.
In the worked example, 60 completed points divided by 3 sprints equals 20 points per sprint. If the same 60 points were completed across four sprints, the average would be 15 points per sprint. The total work has not changed, but the period length has, so the average per sprint differs.
This is a simple average. Each sprint contributes equally to the calculation. The calculator does not adjust for sprint length, holidays, team size, scope changes, or interruptions. If the selected sprints had different lengths or the team changed substantially, the result may be harder to interpret as a guide for the next sprint. Use comparable periods when possible and note any important differences.
Use cases for the Sprint Velocity Calculator
A team can use its recent average as one input during backlog refinement and sprint planning. For instance, the average may help start a conversation about how much work to consider, while the team checks item size, dependencies, availability, and uncertainty. It can also help a project lead explain recent delivery patterns using a consistent calculation.
- Planning conversations: Review the recent average before selecting candidate work, then adjust based on the people and tasks actually available.
- Trend review: Calculate averages over comparable windows to spot a change that deserves discussion.
- Retrospectives: Pair the number with observations about blockers, scope changes, estimation practices, and work completion.
- Scenario checking: See how including another sprint in the measured period changes the average, while keeping the selected period explicit.
Velocity is a team-level planning aid. Using it to rank individuals or pressure a team to increase its points can undermine estimation and make comparisons misleading. Teams may estimate differently, and even one team’s practices can change over time. The number is most informative when it helps the team understand its own work.
Other factors to consider when calculating sprint velocity
Before interpreting the result, check whether the inputs use a stable definition of “completed.” Some teams count an item only after it meets a shared Definition of Done. Others may have different conventions. Mixing conventions can make a multi-sprint average appear consistent while combining unlike measures.
Also consider what changed during the selected period. Team membership, sprint duration, leave, incidents, dependencies, and shifts in work type can affect completed points. These details do not change the calculator’s arithmetic, but they can explain why an average may not represent the next sprint. A new team or a team revising its estimation approach may need time to establish a useful historical baseline.
Keep the result in context by recording the sprint dates, team, point total, and any unusual conditions. Use a window that is long enough to include more than one observation when that fits the purpose, while recognizing that older sprints may reflect a different operating context. Discuss the work behind the number instead of treating the average as a target or commitment.
Frequently asked questions
What does sprint velocity measure?
It measures the average number of story points a team completed per sprint across the sprints included in the calculation. It reflects that team’s estimation and completion practices.
Should unfinished work count in the total?
Use the team’s agreed completion rules consistently. If an item did not meet the team’s completion criteria in a sprint, do not count its full estimate as completed for that sprint. Apply the same convention to every sprint in the selected period.
How many sprints should I include?
There is no universal number that fits every team. Use a clearly defined period that is relevant to the planning question, and consider whether the included sprints are comparable. The calculator accepts one through twelve sprints.
Can I compare velocity between teams?
Direct comparisons are usually misleading because teams create and apply story-point estimates differently. Treat velocity as a local planning measure for the team that produced the estimates.
Does the average guarantee what the team will finish next?
No. It summarizes past completed work. Future results can differ when work, availability, dependencies, or conditions change. Use the average as context for a planning discussion, not as a delivery guarantee.