Sprint Velocity

The typical amount of work a team finishes in a sprint, expressed in the same units used for estimation, such as story points or ideal time.

Key Points

  • Velocity counts only work that meets the Definition of Done at the end of the sprint.
  • It is measured in consistent estimation units (e.g., story points or ideal time) and often averaged across recent sprints for forecasting.
  • Velocity is not a productivity KPI and should not be used to compare different teams.
  • Capacity changes, scope clarity, and team stability influence velocity; adjust forecasts for holidays, new members, or disruptions.

Example

Across the last three sprints the team completed 24, 20, and 22 story points. Their average velocity is about 22 points per sprint. With a backlog of 110 points, the release is forecast to take roughly 5 sprints (110 / 22).

PMP Example Question

A Scrum team has an average velocity of 30 story points. The product backlog for the next release totals 150 story points. What is the best forecast for the number of sprints needed, assuming stable capacity?

  1. 5 sprints, based on the current average velocity
  2. 4 sprints, if the team works overtime
  3. 3 sprints, because velocity should increase each sprint
  4. Cannot estimate until tasks are broken into hours

Correct Answer: A — 5 sprints, based on the current average velocity

Explanation: Velocity is used for empirical forecasting. Dividing 150 by the average velocity of 30 yields an estimate of 5 sprints, assuming conditions remain similar.

Agile Project Management & Scrum — With AI

Ship value sooner, cut busywork, and lead with confidence. Whether you’re new to Agile or scaling multiple teams, this course gives you a practical system to plan smarter, execute faster, and keep stakeholders aligned.

This isn’t theory—it’s a hands-on playbook for modern delivery. You’ll master Scrum roles, events, and artifacts; turn vision into a living roadmap; and use AI to refine backlogs, write clear user stories and acceptance criteria, forecast with velocity, and automate status updates and reports.

You’ll learn estimation, capacity and release planning, quality and risk management (including risk burndown), and Agile-friendly EVM—plus how to scale with Scrum of Scrums, LeSS, SAFe, and more. Downloadable templates and ready-to-use GPT prompts help you apply everything immediately.

Learn proven patterns from real projects and adopt workflows that reduce meetings, improve visibility, and boost throughput. Ready to level up your delivery and lead in the AI era? Enroll now and start building smarter sprints.



Stop Managing Admin. Start Leading the Future!

HK School of Management helps you master AI-Prompt Engineering to automate chaos and drive strategic value. Move beyond status reports and risk logs by turning AI into your most capable assistant. Learn the core elements of prompt engineering to save hours every week and focus on high-value leadership. For the price of lunch, you get practical frameworks to future-proof your career and solve the blank page problem immediately. Backed by a 30-day money-back guarantee-zero risk, real impact.

Enroll Now