Understanding Sprint Velocity
How we calculate. Average velocity = sum of completed points ÷ count of sprints in the sample. The form uses the same arithmetic as the worked examples on this page. 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
Worked Example
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
Limitations: Sprint Velocity results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.
FAQ
Should unfinished carry-over count?
Count only work that met the definition of done in that sprint. Carry-over usually lands in the next sprint’s completed total when finished.
Points or hours?
Most agile teams use story points. If your team estimates in hours, use hours as the unit—but do not mix units in one average.
Authoritative References
For Agile and software testing practices, consult:
- Scrum.org — Scrum glossary and sprint practices
- ISTQB — software testing glossary
- Agile Manifesto — values behind iterative delivery