How to Calculate Sprint Velocity
Velocity measures how much work a scrum team actually finishes per sprint, expressed in the same units it estimates in (usually story points). The agile velocity formula has two parts:
Average velocity = (velocity₁ + velocity₂ + … + velocityₙ) ÷ n
Sprints needed = ⌈ remaining backlog points ÷ average velocity ⌉
Worked Example
| Sprint | 1 | 2 | 3 | 4 | 5 | 6 | Total | Average |
|---|---|---|---|---|---|---|---|---|
| Points done | 21 | 25 | 18 | 27 | 24 | 26 | 141 | 23.5 |
The team completed 141 points over 6 sprints, so its average velocity is 141 ÷ 6 = 23.5 points per sprint. The last three sprints average 25.7, so the team is trending slightly up. With 150 points left in the backlog, the likely forecast is ⌈150 ÷ 23.5⌉ = 7 sprints; the range runs from 6 sprints (best sprint, 27) to 9 sprints (worst sprint, 18).
Capacity-Adjusted Velocity
Raw velocity assumes every sprint has the same people available. When holidays or leave change capacity, divide points by team-days instead. In the example, 141 points over 251 team-days is about 0.56 points per team-day; a sprint with only 30 team-days available should plan for roughly 17 points, not 23.5.
Velocity in Jira
Jira Software calculates velocity for scrum boards automatically. Open your board, go to Reports, and choose the Velocity Chart. It shows the estimate committed at sprint start against the estimate completed for each recent sprint. Copy the completed values into this calculator to see your spread, rolling average and a forecast range, which the Jira chart doesn’t give you directly.
Common Velocity Mistakes
- Counting partial work: Only fully Done items count; carry the rest over
- Comparing teams: Story points are team-relative, so cross-team velocity comparisons are meaningless
- Treating velocity as a target: Pushing for higher velocity leads to point inflation, not more output
- Forecasting with one number: Give stakeholders a range (best/likely/worst), not a single date
- Ignoring capacity changes: Holidays and new joiners change what a sprint can hold
- Re-estimating finished work: Keep original estimates so velocity stays consistent
Improve the Inputs: Better Estimates
Velocity is only as reliable as the estimates behind it. Teams that size stories together with free planning poker tend to get more consistent points and therefore steadier velocity. For a deeper walkthrough, read how to calculate team velocity in agile.
Frequently Asked Questions
How do you calculate sprint velocity?
Add up the story points of every item that met the Definition of Done in each sprint, then average those totals across recent sprints: velocity = total completed points ÷ number of sprints. If a team completed 21, 25 and 18 points, its average velocity is 64 ÷ 3 ≈ 21.3 points per sprint.
What is the agile velocity formula?
Average velocity = (sum of completed story points over the last N sprints) ÷ N. To forecast, divide the remaining backlog by velocity: sprints needed = remaining points ÷ velocity, rounded up.
How many sprints should I use to calculate velocity?
Three to six recent sprints is typical. Fewer than three is noisy; much older sprints may reflect a different team, codebase or definition of done. The last-3 rolling average shows the recent trend.
Should partially completed stories count toward velocity?
No. Only count items that are fully done. Carry unfinished work into the next sprint and count its points when it is completed. Splitting points across sprints inflates velocity and hides problems.
What is capacity-adjusted velocity?
It divides completed points by available team-days (people × working days, minus leave and holidays). Multiplying points per team-day by next sprint’s capacity gives a better plan when holidays or absences change the team’s availability.
Where do I find velocity in Jira?
In Jira Software scrum boards, open Reports and choose the Velocity Chart (or Velocity Report). It shows committed versus completed estimates for recent sprints. Enter the completed values here to get averages, spread and a forecast range.
Can I compare velocity between teams?
No. Story points are relative to each team, so a velocity of 40 for one team is not better than 20 for another. Use velocity only to forecast that same team’s work.
Related Resources
- How to calculate team velocity - full guide
- Fibonacci estimation template - story point reference and printable cards
- Sprint planning guide - use velocity to plan your next sprint
- Meeting cost calculator - see what your sprint ceremonies cost