What this Agile Team Velocity Calculator does
The Agile Team Velocity Calculator estimates a team’s average delivery pace using completed story points from three finished sprints. Its result, Average Points per Sprint, is the total completed points divided by three. A project planner can use that figure as one input when discussing how much work may fit into a future sprint.
In Agile planning, velocity is usually expressed as story points completed per sprint. Story points are a team’s relative estimates of the effort, complexity, and uncertainty involved in work. They are not hours, days, or a universal unit. A team that completes 20 points in a sprint has not necessarily done the same amount of work as another team that also completes 20.
This tool takes three sprint totals, adds them, and calculates their simple average. For example, totals of 20, 22, and 18 points produce an average of 20 story points per sprint. The estimate summarizes those past results. It does not guarantee that the same amount will be completed in a coming sprint.
How to use the Agile Team Velocity Calculator
Enter the completed story points for each of the three sprints. Use the totals from work that met your team’s agreed definition of done by the end of each sprint. Leave out unfinished work, even when it is close to completion. If your team splits a story or changes how it estimates work, follow a consistent rule when recording the completed total.
- Choose three recent, completed sprints that reflect the team’s current way of working.
- Enter each sprint’s completed point total in its matching field.
- Read the average points per sprint shown as the result.
- Use the result as a planning reference alongside capacity, priorities, and known constraints.
The calculator accepts whole-number values from zero to 1,000 for each sprint. A zero is valid if no story points were completed in that sprint. The defaults are example values to demonstrate the calculation. Replace them with your own completed totals before using the result in a planning conversation.
Worked example: Suppose a team completed 24 points in Sprint 1, 18 in Sprint 2, and 21 in Sprint 3. The formula is (24 + 18 + 21) / 3. The sum is 63, and dividing by 3 gives 21 story points per sprint. That figure describes the average across those three sprints.
How the Agile Team Velocity Calculator formula works
The formula adds the three sprint totals and divides the sum by three. Each sprint contributes equally to the average. This is a straightforward arithmetic mean, so one unusually high or low sprint can move the result. The displayed two decimal places make the output consistent, though teams may choose to discuss their planning estimates in whole points.
The calculation assumes that the three inputs use the same story-point scale and represent comparable sprint periods. It also assumes that the team has recorded completed work consistently. If one sprint used a different estimation approach, or its total includes work that was not complete, the average may be harder to interpret.
This is a summary of historical delivery, rather than a forecast model. It does not account for sprint length, team availability, holidays, new team members, interruptions, scope changes, or dependencies. It also does not convert points into hours. Treat the result as context for a team discussion, not as a commitment or an individual performance target.
Use cases for the Agile Team Velocity Calculator
Project planners and Agile teams can use a recent average to make early conversations about scope more concrete. For instance, if the next sprint has more planned work than the team’s recent average, the team can review priorities, clarify estimates, or identify dependencies before making a plan. A lower average may prompt questions about changes in capacity or interruptions, rather than an automatic conclusion about performance.
The estimate can also help when discussing a longer backlog. A team may compare the amount of estimated work with its past pace to form a rough planning scenario. Such a scenario should be described as uncertain. Backlog estimates can change, work can be added or removed, and future sprints may differ from the three used here.
Keep the conversation focused on the team’s shared workflow. Story points are most useful when the team defines and applies them consistently. Comparing velocity figures across teams can be misleading because teams may use different scales, practices, sprint lengths, and definitions of completion.
- Use the average to support a sprint scope conversation.
- Review changes in recent delivery with the people doing the work.
- Pair the figure with capacity and dependency information.
- Recalculate after collecting a new set of comparable completed sprints.
Other factors to consider when calculating team velocity
Three sprints provide a compact snapshot, but they may not capture the team’s usual range of outcomes. A sprint affected by an outage, urgent support work, or a major staffing change can shift the mean. When the result seems surprising, inspect the individual sprint totals and the circumstances behind them instead of treating the average as self-explanatory.
Consistency matters more than precision in the point scale. Teams should agree on how to estimate work and what counts as complete. If those practices change, note the change when reviewing historical numbers. A previous average may no longer describe the current team’s workflow.
Capacity should be considered separately. A team with less available time in an upcoming sprint may reasonably plan less work, even if recent velocity was higher. Similarly, dependencies or uncertain work can affect what fits. The calculator does not make those adjustments because it has no inputs for them.
Use velocity to help the team plan its work, not to rank people or pressure a team into increasing its point total. A healthy planning conversation considers quality, sustainable pace, and delivery risks alongside estimated points. The calculation can start that conversation, while the team supplies the context and judgment.
Frequently asked questions
What does velocity mean in Agile project planning?
Velocity is the number of story points a team completes during a sprint, often reviewed across several sprints. It is a team-specific planning measure. Story points do not represent a fixed amount of time or a universal measure of productivity.
Why does this calculator use three sprints?
Three completed sprints provide a simple recent sample for an average. It is a practical summary, not a rule that every team must use exactly three. A team may review a longer history when it wants more context, especially if recent sprints differed substantially.
Should unfinished stories count toward the total?
Use the team’s agreed completion rules and enter only the points credited as completed for each sprint. If a story is unfinished, do not count its points as completed unless the team’s established process explicitly records work another way. Consistent tracking makes the average easier to understand.
Can I use the result to compare two teams?
Usually, a raw comparison is not meaningful. Teams can use different point scales, estimation habits, sprint lengths, and definitions of done. The result is best used by the same team to inform its own planning over time.
Does average velocity promise how much the team will finish next sprint?
No. The result describes the average of the three values entered. Future capacity, scope, interruptions, uncertainty, and dependencies can change what a team completes. Use the figure as a reference during planning, then make a realistic plan with the team’s current conditions in view.