Sprint Velocity

Velocity measures sustainable delivery throughput for a stable team. QA teams often track a testing velocity (cases or risk items completed) the same way.

Average velocity = sum of completed points ÷ count of sprints in the sample.

Tip: Keep “Total Points Completed” and “Number of Sprints” on the same basis (units, period, and definition) before you calculate.

Cluster: Software Testing hub · Professional KPIs · Percentage guide

Sprint velocity is the average story points (or tickets) a team finishes per sprint. Use it to forecast upcoming capacity—not as a performance weapon.

Enter total points completed across recent sprints and how many sprints you are averaging.

Sum of completed points across the sample sprints
How many sprints are included in the average

Average Velocity (points/sprint)

Understanding Sprint Velocity

How we calculate. Average velocity = sum of completed points ÷ count of sprints in the sample. See our methodology and accuracy policy .

Real-world scenario: A typical Sprint Velocity case uses total points completed 128 and number of sprints 4. Enter the same figures below to reproduce the worked path.

What is Sprint Velocity?

Velocity measures sustainable delivery throughput for a stable team. QA teams often track a testing velocity (cases or risk items completed) the same way.

  • Use 3–5 recent sprints for a smoother average
  • Keep the unit consistent (story points, tickets, or test cases)
  • Do not compare teams — velocity is local to one team’s sizing

The Formula

Sprint Velocity
Velocity = Total points completed ÷ Number of sprints

Worked Example

Scenario: Over 4 sprints the team completed 128 story points.
Step 1: Total points = 128
Step 2: Sprints = 4
Step 3: Velocity = 128 ÷ 4 = 32
Answer: Average sprint velocity is 32 points per sprint.

Common Use Cases

  • Release forecasting: backlog ÷ velocity ≈ sprints needed
  • Sprint planning: pull roughly one velocity of work
  • QA capacity: estimate how much test scope fits a sprint

Pro Tips

  • Exclude abandoned spikes if they did not deliver finished value
  • Note scope changes that inflate or deflate a single sprint
  • Pair with capacity when PTO will change the next sprint
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

Limitations: Sprint Velocity results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

The worked example for sprint velocity was verified with the calculator form on this page—enter the same values to confirm the result.

When to use this calculator

  • Use this page when your wording matches sprint velocity and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about sprint velocity? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this sprint velocity calculator?

For sprint velocity, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for sprint velocity—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking sprint velocity, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

Authoritative References

For Agile and software testing practices, consult: