What this Agile Team Velocity Calculator does
The Agile Team Velocity Calculator estimates the average number of story points a team completes in one sprint. Enter completed points for six recent sprints and the calculator adds them, then divides by six. The result is an arithmetic average, expressed in points per sprint. For example, entering 24, 27, 25, 26, 0, and 0 produces 17 points per sprint because the total of 102 is divided by six.
Velocity is a planning measure used within a team’s own estimation system. Story points are relative estimates of work, and their scale is chosen by the team. A result of 17 points per sprint does not mean that one team produces the same amount of work as another team with a result of 17. The number is most useful for looking at one team over time, provided its sprint structure and estimation habits are reasonably consistent.
This tool treats all six entries as actual sprint results. The default values of zero in Sprint 5 and Sprint 6 are placeholders for sprints with no completed points. If you have fewer than six completed sprints, use the same averaging approach over the sprints you do have, with a manual calculation, or enter only comparable sprints and adjust the divisor. Do not interpret placeholder zeros as evidence that a team completed no work.
How to use the Agile Team Velocity Calculator
Gather the completed story point total for each of the six sprints you intend to compare. Use the team’s normal definition of “completed,” such as its agreed acceptance criteria or definition of done. Enter a number for each sprint, including zero only if that sprint genuinely ended with no completed points.
- Choose a consistent period. Compare recent sprints that used similar durations and working practices.
- Use completed work. Do not enter planned points or partially finished work unless your team’s established reporting method explicitly counts it.
- Keep the point scale stable. Re-estimation or a change in how points are assigned can make earlier and later results difficult to compare.
- Review the output in context. The result is an average across the six entries, not a commitment or a productivity score.
Suppose the recorded totals are 24, 27, 25, 26, 28, and 30 points. Their sum is 160. Dividing by six gives 26.67 points per sprint when rounded to two decimal places. The calculator will display that average. A team can use it as one planning reference while still checking the work expected in the next sprint.
How the Agile Team Velocity Calculator formula works
The formula adds the values in Sprint 1 through Sprint 6 and divides the sum by six:
(Sprint 1 + Sprint 2 + Sprint 3 + Sprint 4 + Sprint 5 + Sprint 6) / 6
Every entry is measured in completed story points, so the result is completed story points per sprint. The calculation gives each sprint equal weight. A sprint with a high total contributes as much to the average as one with a low total. The display rounds to two decimal places, but the underlying arithmetic is the sum divided by six.
For the example values 24, 27, 25, 26, 28, and 30, the arithmetic is (24 + 27 + 25 + 26 + 28 + 30) / 6 = 160 / 6 = 26.67. The formula does not infer sprint length, team capacity, work complexity, or the reason a result changed. It simply summarizes the six numbers supplied.
Use cases for the Agile Team Velocity Calculator
A team may use a recent average to start a conversation about how much work to consider during upcoming sprint planning. It can compare the result with the team’s own recent history, then discuss differences in scope, availability, or dependencies before selecting work. The calculation can also help a facilitator explain how several sprint outcomes combine into one simple planning reference.
For example, a team that has recently averaged about 27 points per sprint might review whether a proposed set of work is plausible given upcoming leave, support duties, or known blockers. The average does not decide the sprint plan. The people doing the work still need to examine the items, clarify uncertainty, and decide what they can responsibly take on.
Velocity can also support retrospective discussion. If results vary, the team can look for changes in work size, interruptions, staffing, or acceptance practices. The purpose is to understand the planning conditions and improve shared expectations. Treating a higher number as an automatic target can encourage point inflation or pressure people to change estimates without changing the work.
Other factors to consider when calculating team velocity
The average is only meaningful when the inputs represent comparable periods. A holiday sprint, a major release, or a change in sprint length may lead to a number that needs explanation. Likewise, teams may estimate work differently, so comparing velocity across teams can create a misleading impression of relative performance.
Consider the following before relying on the figure:
- Whether each sprint had the same duration and a similar definition of completion.
- Whether team membership or availability changed during the selected period.
- Whether unplanned work or operational support took time away from planned items.
- Whether estimates remained consistent, or the team changed its point scale.
- Whether a one-off unusually high or low sprint is distorting the average.
When conditions vary, show the individual sprint totals alongside the average and discuss what happened. A rolling average can summarize recent results, while the underlying values preserve useful detail. Use the calculation as a lightweight aid to conversation. It cannot predict exact delivery dates or guarantee that a particular amount of work will be finished.
Frequently asked questions
What does team velocity measure?
It measures the sum of completed story points during a sprint, or an average of those totals across several sprints. It reflects a team’s own estimates and working context rather than a universal unit of output.
Should unfinished work count toward velocity?
Use the team’s consistent completion policy. Many teams count an item only when it meets their agreed definition of done. Counting partial work differently from sprint to sprint makes the average harder to interpret.
Can I compare one team’s velocity with another team’s?
Usually, the figures are not directly comparable because teams use different estimation scales, work types, and practices. Each team’s trend over time is generally more informative than a comparison between teams.
What if I have fewer than six sprint results?
Average only the completed, comparable sprints you have by dividing their total by their count. This calculator’s formula always divides by six, so its result is appropriate only when all six entries represent real sprint results. The zero defaults should not stand in for missing history.
Does the average guarantee what a team will complete next sprint?
No. It summarizes prior results and cannot account for future changes in scope, availability, dependencies, or interruptions. Use it as one input to planning, then make decisions based on current conditions and the team’s judgment.