What this Team Velocity Calculator does
The Team Velocity Calculator estimates how much accepted work a team completes, on average, in one iteration. It divides the total accepted work points by the number of completed iterations. The result is expressed in points per iteration, giving a compact summary of recent delivery history.
Velocity is a planning measure used in iterative project work. A team first estimates work items in points according to its own conventions, then records which work was accepted by the end of each iteration. This calculator adds up the accepted points across the period and divides by the iteration count. For example, 30 accepted points across three completed iterations yields an average of 10 points per iteration.
The number is meaningful only within the team and estimation approach that produced it. Points are relative estimates, not hours, days, or a universal measure of productivity. Comparing two teams by their velocity alone can be misleading because their point scales, work types, and acceptance practices may differ.
This tool takes two inputs: accepted work completed, in points, and completed iterations. Its formula is accepted work completed ÷ completed iterations. It returns average velocity as points per iteration. It does not forecast an exact delivery date or decide which work should be prioritized.
How to use the Team Velocity Calculator
Gather the team's accepted work totals for a defined set of completed iterations. Use the same point scale and completion rules throughout the period. Enter the total accepted points in the first field and the number of completed iterations in the second field. The iteration count must be at least one because the calculation divides by that value.
- Accepted work completed: Enter the sum of work points that met the team's acceptance criteria during the selected iterations.
- Completed iterations: Enter how many full iterations are included in that total.
- Result: Read the average number of accepted points per iteration.
As a worked example, suppose a project team accepted 42 points of work over six completed iterations. Using the actual formula, 42 points ÷ 6 iterations = 7 points per iteration. If the same 42 points were entered across three iterations, the result would be 14 points per iteration, reflecting a different period of work.
Choose a period that fits the planning discussion. A short window may respond quickly to staffing or workflow changes, while a longer window may smooth out unusually light or heavy iterations. Keep the window clear when sharing the result so that people know which history it summarizes.
How the Team Velocity Calculator formula works
The formula is completed_work / iterations. The numerator represents accepted work, measured in points. The denominator is the number of completed iterations. Dividing points by iterations produces points per iteration.
For instance, entering 30 accepted points and three iterations gives 30 / 3 = 10 points per iteration. The calculator displays two decimal places, but a fractional average does not imply that a team must plan a fraction of a point in a particular iteration. It is a summary across the chosen period.
The calculation assumes the total points and iteration count describe the same team, time window, and definition of done. It also assumes points were assigned consistently enough to make an average useful. The result is not based on a fixed productivity standard. Teams may estimate differently and may revise their practices over time.
Only completed iterations belong in the denominator. Including a current, unfinished iteration can distort the average because its accepted work is still accumulating. Likewise, work that is in progress but has not met acceptance criteria should not be counted as completed unless the team's explicit tracking policy defines otherwise.
Use cases for the Team Velocity Calculator
A project lead can use the average as one input when discussing how much work to consider for a future iteration. The figure is most useful alongside the team's knowledge of upcoming work, availability, dependencies, and risks. It can provide a starting point for a conversation without replacing judgment or team agreement.
Teams may also use a consistent calculation to review changes in their delivery pattern. For example, they might compare averages across successive periods after a process change. That comparison should be interpreted cautiously. A shift could reflect a different mix of work, changes to estimation, holidays, interruptions, or acceptance practices rather than a simple change in effort.
Other reasonable uses include:
- Summarizing accepted work for a retrospective discussion.
- Creating a transparent baseline for iteration planning conversations.
- Checking whether a proposed commitment is broadly consistent with recent completed work.
- Helping a project group explain why estimates and delivery capacity need regular review.
Use the measure to support learning and coordination. Treating it as an individual performance score can encourage point inflation or rushed acceptance, which weakens the quality of the information. A team-level average is best discussed with context and care.
Other factors to consider when calculating velocity
Velocity compresses a complicated project history into one average. It does not show the uncertainty or distribution behind that average. Two teams could have the same result while one delivers a similar amount each iteration and the other alternates between very low and very high totals. Looking at iteration-by-iteration history can reveal that difference.
Scope changes also matter. If a team adds or removes work during an iteration, note how the organization records it. Incomplete items carried forward should be handled consistently to avoid counting the same work more than once. Work accepted in a later iteration belongs in that later period under many tracking approaches, but teams should follow one clear policy.
Availability can vary because of leave, support duties, onboarding, or urgent issues. The calculator does not adjust for those conditions. It is often helpful to record notable events beside the result rather than trying to interpret every fluctuation as a trend. Keep estimation methods stable where possible, and revisit them openly when the team changes its understanding of a point scale.
Finally, velocity is not a measure of business value, quality, or customer impact. A higher point total does not automatically mean that a project is healthier. Pair the average with relevant delivery and outcome information, and use it as one planning signal among several.
Team Velocity Calculator FAQ
What does velocity mean in this calculation?
It means the average accepted work points completed per iteration over the period entered. It is specific to the team's estimation and acceptance practices.
Should unfinished work count as completed points?
Count work according to the team's stated acceptance criteria. If an item has not met those criteria, excluding it keeps the completed-work total aligned with accepted delivery. Apply the same rule consistently.
How many iterations should I include?
Use several completed iterations that represent the period relevant to your planning discussion. A longer period can smooth variation, while a shorter one may reflect recent conditions more closely. State the period when sharing the average.
Can I compare velocity across teams?
Direct comparisons are usually unreliable because teams may use different point scales, work mixes, and acceptance rules. The result is primarily useful for a team interpreting its own history.
Does this result guarantee how much work the team will finish next?
No. It summarizes past work and cannot account for future scope, availability, dependencies, or unexpected events. Use it as a planning reference, then review commitments with the people doing the work.