Velocity Calculator
Calculate Velocity step by step: Velocity = average of completed (done) story points over recent sprints.
In short
Formula: Velocity = average of completed (done) story points over recent sprints.
What this calculator does
Calculate Velocity step by step: Velocity = average of completed (done) story points over recent sprints. Worked example, questions and limitations included.
Use it to turn Completed points — sprint 1, Completed points — sprint 2, Completed points — sprint 3, Completed points — sprint 4 (optional), and the other shown inputs into a checked result you can compare, copy, or rerun with different assumptions.
The page shows the formula, a numeric worked example, and the assumptions that affect this agile delivery calculation.
Inputs and what they mean
- Completed points — sprint 1
- — number value.
- Completed points — sprint 2
- — number value.
- Completed points — sprint 3
- — number value.
- Completed points — sprint 4 (optional)
- — number value.
- Completed points — sprint 5 (optional)
- — number value.
How to use it
- Enter each value in the unit shown next to the box (use the unit converter first if your numbers are in other units).
- Check the breakdown to see every intermediate step.
- Read the limitations before relying on the result.
Formula
Velocity is a common Scrum practice but is not part of the Scrum Guide (2020); it comes from Extreme Programming and team practice.
Count only items meeting the Definition of Done; partly done work earns nothing.
Velocity is specific to one team and its own estimating scale. It is not comparable between teams and is not a productivity benchmark; use it only for that team's own forecasting.
Velocity = average of completed (done) story points over recent sprints.
Inputs used: Completed points — sprint 1, Completed points — sprint 2, Completed points — sprint 3, Completed points — sprint 4 (optional), Completed points — sprint 5 (optional).
Worked example
Three sprints
- (21 + 25 + 23) ÷ 3 = 23 points per sprint.
- Range 21–25.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
- Meaningless across teams.
- Sensitive to changes in team or estimating scale.
- Average hides variation; use the range.
- Results are planning estimates built only from the figures you enter. They are not a guarantee of cost, schedule or delivery, and they do not replace your organisation's own project controls.
- The result depends on the values you enter for this velocity calculator; it does not supply missing rates, rules, prices, dates, or assumptions for you.
Common questions
Can I compare velocity between teams?
No. Each team uses its own point scale, so 30 points for one team says nothing about 30 for another.
Should we try to increase velocity?
Targeting velocity tends to inflate estimates rather than improve delivery. Use it for forecasting only.
How many sprints should I use?
Three to five recent sprints is common practice; drop sprints with unusual disruption only if you note why. Check the formula, example, and limitations on this page before using the result for a real agile delivery decision.
How do I use the Velocity Calculator?
Enter the required values for Completed points — sprint 1, Completed points — sprint 2, Completed points — sprint 3, Completed points — sprint 4 (optional), Completed points — sprint 5 (optional). The calculator applies the formula on this page and shows the main result with any supporting breakdown so you can check the arithmetic.
What formula does the Velocity Calculator use?
Velocity = average of completed (done) story points over recent sprints. The visible formula section above lists the calculation path and the edge cases the page handles, so the result can be checked without relying on the form alone.
Can the Velocity Calculator be used for exact decisions?
Use it as a calculation aid, not as a substitute for checking the underlying rule, contract, policy, or professional advice that applies to your situation. When a result depends on local rules, personal details, prices, or dates, enter those values yourself and confirm them before acting.
Related tools
Calculate Agile Team Capacity step by step: Capacity (hours) = (members × sprint days − absence days) × focus hours per day − members × event hours.
Calculate Sprint Capacity step by step: Sprint capacity (points) = average velocity × available person-days ÷ normal person-days.
Calculate Release Forecast step by step: Sprints = remaining points ÷ velocity, rounded up, using both a low and a high velocity to give a range.
Calculate Agile Throughput step by step: Throughput = items finished ÷ period length.
Calculate agile cycle time step by step: cycle time = finish date − start date, shown as average, median and 85th percentile.
Calculate Lead Time step by step: Lead time = delivery date − request date (when the customer asked).