Sprint Velocity Calculator
Give this calculator three numbers, the story points your team finished, the number of contributors, and the sprint length in days, and it returns your velocity as story points per sprint for the whole team, the Scrum convention. Team size and sprint length stay in the result as context: the average points per contributor per sprint, never as an individual rating.
Velocity is reported to two decimals. Zero story points is a valid entry (a sprint with no finished stories), but team size and sprint length must be positive numbers.
Quick Answer
For the worked example of 80 story points, a 5-person team and a 10-day sprint, the velocity is 80.00 points per sprint for the whole team (average 16.00 points per contributor per sprint). Enter your own three numbers and the calculator shows the team figure with its per-person average at once.
Key takeaways
- Velocity is a team figure: story points finished in one sprint, quoted for the whole team, the way Scrum teams plan.
- The results badge also shows the average points per contributor per sprint as context. That average describes the team shape; it is not an individual productivity rating.
- Velocity becomes reliable after 3 to 5 sprints, and you should compare against your own rolling average, never against another team’s number.
- Count only finished, accepted stories. Incomplete work and carryover inflate the number and poison the next forecast.
- Quick Answer
- How to use the sprint velocity calculator
- The sprint velocity formula, in the Scrum per-sprint convention
- Worked example: 80 points, 5 people, 10 days
- What competing calculators miss
- Using velocity over several sprints, the right way
- Frequently asked questions
- Add This Calculator to Your Website
- References
How to use the sprint velocity calculator
Enter three numbers and click Calculate velocity. The results stay hidden until you calculate, and the Reset button restores the worked-example values.
- Enter total story points completed: every user story finished and accepted in the sprint. The calculator accepts decimals, and 80 is pre-filled as the worked example.
- Enter the number of team members: active contributors only, not managers or stakeholders. This is pre-filled as 5.
- Enter the sprint length in working days: 10 for a standard two-week sprint, 5 for a one-week sprint. Use working days only; calendar days misstate the sprint length.
- Read two numbers, not one: the headline team figure (points per sprint for the whole team) and the average points per contributor per sprint, which is context only and never an individual rating.
If any field is blank, non-numeric, or if story points are negative, or team size or sprint length is zero or negative, the calculator shows “Please enter valid values.” rather than a misleading number. Story points of zero are accepted: a sprint where nothing shipped has a velocity of 0.00, which is honest data, not an error.
The sprint velocity formula, in the Scrum per-sprint convention
The calculator reports the team total directly:
Average per person per sprint = Team velocity ÷ Team members (context only)
This is the Scrum convention, not a normalized rate. The Agile Alliance glossary defines velocity as the amount of work a team completes during a timebox, measured in story points, and Scrum teams normally track it per sprint for the whole team. Team size and sprint length are kept only for the per-person average shown as context. The two readings below show how the worked example maps across both figures.
| Reading | Value (80 pts, 5 people, 10 days) | When you need it |
|---|---|---|
| Team velocity (points per sprint) | 80.00 | Sprint planning with your own team: how much to pull into the next sprint |
| Average per person per sprint | 16.00 | Context on team shape: the average load per contributor, never an individual rating |
Worked example: 80 points, 5 people, 10 days
The calculator is pre-filled with this case, so click Calculate velocity and you get 80.00 points per sprint immediately.
Five more real runs, each reproducible in the tool above:
| Points / team / days | Pts/person/sprint | Pts/sprint (team) |
|---|---|---|
| 120 / 6 / 10 | 20.00 | 120.00 |
| 33 / 7 / 14 | 4.71 | 33.00 |
| 60 / 3 / 10 vs 60 / 6 / 10 | 20.00 vs 10.00 | 60.00 vs 60.00 |
| 7.5 / 3 / 10 | 2.50 | 7.50 |
| 1000 / 12 / 20 | 83.33 | 1000.00 |
The third row is the comparability check: two sprints can deliver identical team velocity (60 points) with different team sizes, so the per-person average (20.00 vs 10.00) shows the shape difference. Plan on the team figure; use the average only to sense-check comparability, never to rate individuals.
What competing calculators miss
Velocity tools on the web fall into three camps, and each leaves a gap this page closes:
- Per-sprint tools (Savvy Calculator’s sprint velocity page): average velocity as points per sprint, the Scrum convention this page now follows. Useful for planning with your own team; the per-person average is context for team shape, not a cross-team league table.
- Capacity planners (sprint capacity calculators): start from hours, PTO and focus factors to answer how many points to commit to. Rich for one team’s planning, but they never reduce the result to a portable rate, so cross-team benchmarking is out of reach.
- Guide pages (story-points-to-hours articles): explain how to derive hours-per-point from historical velocity. The guidance is sound, but there is no testable number on the page: you cannot enter your sprint data and get a figure.
- The gap this page fills: one instant team figure, points per sprint, the Scrum convention, with the per-person average shown only as context, so you get the plannable figure without inviting individual-productivity misuse.
Using velocity over several sprints, the right way
One sprint’s velocity is a data point, not a verdict. Mature Scrum practice treats velocity as a rolling average over 3 to 5 sprints, because a single sprint is easily distorted by holidays, onboarding or one nasty production incident. The practical workflow is: run each sprint through this calculator, keep the points-per-sprint figure, and plan the next sprint on the average, not the latest.
Here is what that looks like. Suppose your last three sprints each had 5 people and 10 days, delivering 70, 85 and 76 points. The calculator gives 70, 85 and 76 points per sprint; the average of 77 points is your next-sprint commitment guide. When team size changes between sprints, do not treat raw points as directly comparable: check the per-person average for shape, then plan on the team figure for the team you actually have.
Velocity also works as an early-warning instrument and as a productivity measure. A steady decline over two or three sprints usually means growing blockers, mounting tech debt or a team losing focus, not lazier engineers. Like any labor productivity figure, the number is most useful as a trend against your own history, not as a target to chase.
Investigate the cause before you touch estimates: shrinking the number by fiat, or inflating story points to flatter the trend, turns the metric into a vanity chart and lost productivity into an invisible tax. A scrum master who can put a figure on throughput, and on how much it moved, has a much stronger conversation with stakeholders about sprint capacity planning than one armed with anecdotes.
Frequently asked questions
Sprint velocity is the amount of work a team completes during one sprint, measured in story points. In Scrum practice, velocity is normally quoted as points per sprint for the whole team. The number this calculator reports is exactly that team figure: story points per sprint for the whole team. The per-person average shown beside it is context on team shape, not an individual rating.
Team velocity is the story points your team finished and accepted in the sprint: 80 points finished means 80.00 points per sprint. Team members and sprint length give the average per contributor per sprint (80 divided by 5 equals 16.00), shown as context only.
To record the sprint shape and to show the average per contributor per sprint as context. Sixty points from 3 people and 60 points from 6 people are the same team velocity for planning, but the averages (20.00 vs 10.00) tell you the teams were shaped differently. Never use that average to rate an individual: Scrum velocity is a team planning figure.
It is the team velocity divided by team members: 80.00 divided by 5 equals 16.00 points per contributor per sprint for the worked example. It describes the average shape of the team, not any one person’s output, and planning still uses the 80.00 team figure.
There is no universal target. The useful comparison is with your own past sprints: track 3 to 5 sprints and look for a stable range. A typical two-week team often lands somewhere like 30 to 50 points per sprint, but the number depends entirely on your team’s pointing scale, so never compare across teams.
No. Count only stories that are fully finished and accepted in the sprint. Half-done work carried into the number inflates it and wrecks the next forecast; unfinished stories belong in the sprint where they actually ship.
Not necessarily. Story points are a team-relative scale, so a rising number can simply mean bigger estimates rather than more output. Stable, predictable velocity with good quality is the goal, not an ever-larger number.
Yes, with care. Kanban teams usually track throughput, the number of cards finished per week, instead of velocity. Enter your completed items per period in place of story points and the calculator still gives a fair per-period team throughput figure for capacity discussions.
Add This Calculator to Your Website
Embed this calculator on your own site with the code below. Pick a size to preview it live, then copy the code.
Powered by Calculator Zilo
References
- Agile Alliance. Velocity (Agile Glossary). Accessed October 23, 2026.
- Schwaber, K. and Sutherland, J. The Scrum Guide: The Definitive Guide to Scrum. Accessed October 23, 2026.
- Atlassian. What is the velocity report?, Jira Software Cloud documentation. Accessed October 23, 2026.
- Atlassian Community. Velocity vs Capacity: What’s the Difference and Why Both Matter. Accessed October 23, 2026.
- Scrum Alliance. An Overview of Scrum. Accessed October 23, 2026.
