What this Team Velocity Calculator does
The Team Velocity Calculator estimates how quickly a team completes planned work during a sprint. It divides completed work, measured in points, by the sprint’s working days. The result is a simple daily rate that can help a project group describe recent delivery in consistent terms.
This calculation is a planning aid. It does not predict a deadline, judge a team’s performance, or account for differences in how teams define and assign points. Story points are relative estimates, so the result is most useful when the same team uses the same estimation approach and work-point scale over time.
For example, a team that completes 20 points in a 10-working-day sprint has a rate of 2 points per working day. That figure summarizes the selected sprint. It should be interpreted alongside the work completed, changes in scope, and any interruptions that affected the period.
How to use the Team Velocity Calculator
Enter the total points for work completed during one sprint, then enter the number of working days in that sprint. The calculator divides the first value by the second and displays the result in points per working day.
- Completed work means the points for items that met the team’s definition of done within the sprint.
- Sprint duration means the working days in the sprint. Do not include weekends unless your team treats them as normal working days.
- Use matching records. The points and duration should refer to the same sprint.
Suppose the team finished 26 points over 10 working days. Enter 26 and 10. The displayed rate is 2.60 points per working day. If work was carried over, count only the portion the team’s agreed process recognizes as completed. Apply that rule consistently rather than changing it to improve a particular result.
The calculator accepts positive whole-number inputs within its displayed limits. For a sprint with no completed points, the rate is zero mathematically, but this version requires at least one point. You can treat zero-completion periods separately in your planning notes, since dividing zero by the duration produces a different kind of signal about what happened during that sprint.
How the Team Velocity Calculator formula works
The formula is completed work points ÷ sprint working days. Its output is a rate, so the unit is points per working day. The numerator describes completed work, while the denominator describes the length of the period in which the work was completed.
Worked example: a team completes 30 points in a 15-working-day sprint.
- Completed work = 30 points
- Sprint duration = 15 working days
- Calculation = 30 ÷ 15
- Result = 2.00 points per working day
The arithmetic is straightforward, but the input definitions matter. Points do not represent hours, and two teams’ point values may not be comparable. A rate calculated from one team’s estimates should be used for that team’s planning context. It is not a universal productivity score.
The result also averages across the sprint. It does not show when items were finished, how many were in progress, or whether all work had equal importance. The calculator uses only the two supplied values and assumes the completed points were recorded consistently for that sprint.
Use cases for the Team Velocity Calculator
A daily rate can support a few practical conversations in people and project planning. It gives a team a compact way to summarize a completed sprint and compare periods that use the same units and conventions.
- Sprint retrospectives: Review the rate beside changes in scope, dependencies, staffing, and interruptions.
- Capacity discussions: Use recent results as one reference when deciding how much work to consider for a future sprint.
- Project updates: Explain a completed period using a rate with clear units, rather than presenting an unexplained point total.
- Process reflection: Ask whether estimation, completion criteria, or work intake changed between periods.
For future planning, the average daily rate can be multiplied by the number of working days in a proposed period. That additional estimate assumes the team’s capacity and working conditions remain comparable. This calculator does not perform that projection, and a projection should be treated as a rough planning scenario rather than a commitment.
When reviewing several sprints, calculate each period on its own before summarizing a trend. A single average can hide variation. Also consider whether sprint lengths differ, since a total point count from a longer sprint cannot be compared directly with one from a shorter sprint without accounting for duration.
Other factors to consider when calculating team velocity
Velocity is shaped by how work is selected, estimated, and considered complete. A number can move because the team’s circumstances changed, even when its underlying skills and effort did not. Interpret it as a planning observation rather than a verdict about people.
Before drawing conclusions, consider:
- Whether the team’s point scale and estimation practices stayed consistent.
- Whether the definition of done changed or work was accepted under different criteria.
- Whether the sprint included holidays, absences, onboarding, urgent support, or unusual interruptions.
- Whether scope was added or removed after planning began.
- Whether external reviews, approvals, or dependencies delayed completion.
Do not compare individual workers by assigning their work a share of the team’s velocity. The metric describes a team’s completed work under a particular process, and individual comparisons can distort collaboration and estimation. For staffing or delivery decisions, combine the calculation with direct discussion of scope, risks, and capacity.
Consistent recording makes the result more useful. Keep a brief note of meaningful conditions for each sprint, such as a major dependency or a change in team membership. That context helps explain variation without treating a number as a complete account of project health.
Team Velocity Calculator FAQ
What does points per working day mean?
It is the number of completed work points divided by the sprint’s working days. It summarizes the average rate for that period. It does not mean the team completes the same fraction of a point every day.
Should I count unfinished work?
Use the team’s established completion rules. Many teams count an item only after it meets the agreed definition of done. Apply the same rule each sprint and document exceptions so the resulting rate remains interpretable.
Can I compare velocity across teams?
Usually, the result is best used within one team over time. Point scales and estimation habits differ, so matching numerical rates do not necessarily represent matching amounts of effort or output.
Does a higher velocity mean better performance?
No single rate establishes team performance. A change may reflect scope, sprint duration, staffing, estimation, dependencies, or work mix. Discuss the context and delivery quality before interpreting a change.
How many sprints should inform planning?
Review multiple recent, comparable sprints to understand variation. This calculator uses one sprint at a time. Teams can compare several outputs and use their judgment about which periods reflect current conditions, while keeping estimates flexible.