What this Agile Team Velocity Calculator does
The Agile Team Velocity Calculator estimates a team's average completed story points per sprint. It divides the total story points completed across a set of finished sprints by the number of those sprints. The result is an average in points per sprint, which can help a team describe its recent delivery pace during project planning.
The calculator uses two inputs: total completed story points and the number of completed sprints. Its formula is total completed story points / completed sprints. For example, a team that completed 120 points across six sprints has an average velocity of 20 points per sprint.
Velocity is a team-specific planning measure. Story points are estimates used by a particular team, so the result does not make one team directly comparable with another. It also summarizes past work. Changes in staffing, work type, interruptions, estimation habits, or sprint conditions can make future results differ.
How to use the Agile Team Velocity Calculator
Enter the total story points that the team completed within the chosen set of finished sprints. Then enter how many completed sprints those points cover. Use the same team's point scale and a consistent definition of completed work throughout the period.
- Total completed story points: Add the points for work that met the team's completion criteria during the selected sprints.
- Number of completed sprints: Count the finished sprints included in that total.
- Average Velocity: Read the result as points per sprint, not as hours, people, or a measure of individual productivity.
Worked example: suppose a project team completed 18, 22, 17, 21, 20, and 22 story points in six sprints. The total is 120 points. Substituting the inputs into the formula gives 120 points / 6 sprints = 20 points per sprint. The calculator's result uses two decimal places, so whole-number results appear with trailing zeros.
The input ranges allow positive totals from 1 to 1,000 points and from 1 to 20 completed sprints. If your tracking system uses a larger total or a longer period, calculate with a suitable subset or use a method that accommodates your data. Keep the units and period clear in any planning notes.
How the Agile Team Velocity Calculator formula works
The formula is completed_points / sprint_count. Division turns a cumulative total into a per-sprint average. If 96 completed points came from four sprints, the calculation is 96 / 4 = 24 points per sprint.
This is an arithmetic mean. Each included sprint contributes equally to the average, regardless of how many working days it had or why its output varied. A sprint with unusually high or low completion can shift the result, especially when the period contains only a few sprints. Looking across several recent sprints may give a broader summary, while still reflecting the conditions in that period.
For a meaningful calculation, count completed work consistently. A team might count an item only after it satisfies its definition of done. Partially finished work should be handled according to the team's established tracking rules, rather than counted differently from sprint to sprint. The calculation itself cannot determine whether the input data follow those rules.
The result is descriptive rather than predictive. It does not account for planned leave, new work, dependencies, changing scope, defects, or uncertainty. It also does not estimate a delivery date. Those questions require additional project information and discussion with the people doing the work.
Use cases for the Agile Team Velocity Calculator
A team can use its average velocity as one reference when discussing how much work might fit into a future sprint. The number can support a planning conversation when the team has a reasonably consistent way to estimate and complete work. It should sit alongside current context, such as availability, dependencies, and the shape of the backlog.
Project leads may also use the calculation to summarize a completed planning period. For instance, a retrospective can compare the average from one set of sprints with another and ask what changed in team composition, work size, interruptions, or completion practices. The number can prompt questions, but it does not explain the causes of variation on its own.
Velocity can help make a backlog conversation more concrete. If a team has a set of candidate tasks, its recent pace may help frame a rough discussion about scope. That discussion should preserve room for uncertainty and should be revisited as new information appears. A single average is not a commitment or a guarantee.
Use the result within the team whose estimates produced it. Story points have meaning through local conventions and shared understanding. Comparing raw velocity across teams may reward differences in estimation scales rather than reveal meaningful differences in delivery.
Other factors to consider when calculating team velocity
Before using the average, check that the selected sprints provide a useful picture of the work ahead. A period with major absences, a team reorganization, unusual support load, or a different type of work may not resemble the next sprint. Explain notable conditions alongside the number.
Also consider the consistency of the team's estimation and completion practices. If the point scale or definition of done changed during the period, the inputs may combine unlike measurements. In that case, calculate separate averages for comparable periods or explain the change when sharing the result.
- Use completed sprints and a clearly stated time period.
- Apply the same completion rule to every sprint in the total.
- Keep the team's point scale stable when comparing periods.
- Review capacity and known work conditions before using the average in planning.
- Share the result as a team planning aid, not an individual performance score.
These checks help people interpret the calculation responsibly. The calculator performs a simple division and cannot inspect a project board, judge estimates, or account for circumstances that are not represented in its two inputs.
Frequently asked questions
What does velocity mean in this calculator?
It means the average number of story points completed per sprint across the sprints represented by the inputs. It is specific to the team and its estimation practices.
Should I include unfinished work?
Use the team's consistent completion rule. If unfinished items do not meet that rule, do not add their full points to the completed total. Follow the team's existing method for recording partial work.
How many sprints should I include?
Choose a set of completed sprints that gives useful context for the planning question. The calculator does not prescribe a period. Note unusual conditions and avoid treating a short or atypical sample as a firm forecast.
Can I compare velocity between teams?
Raw point totals are generally team-specific because teams may estimate on different scales and use points differently. The result is most useful for internal planning by the team that supplied the inputs.
Does average velocity predict a delivery date?
No. It summarizes past completed points per sprint. A delivery estimate would also depend on scope, availability, dependencies, future changes, and other project conditions that this calculation does not include.