Skip to content
PMPCAPM

Velocity

Velocity is the amount of work a Scrum team completes in a Sprint, typically measured in story points, used to forecast how much work the team can handle in future sprints.

Share:

Know it well enough for the exam? Questions on Velocity are scenario-based, not definitional.

Practice it free

Explanation

Velocity is calculated by summing the story points of all Product Backlog items that meet the Definition of Done at the end of a Sprint. It is a trailing indicator, meaning it reflects past performance. Over several sprints, velocity stabilizes and becomes a useful planning tool for forecasting how much work the team can take on.

Velocity is unique to each team and should never be used to compare teams or as a performance metric for individual team members. Its sole purpose is to help the team and Product Owner plan sprints and releases. Using velocity as a performance measure creates perverse incentives, such as inflating estimates.

A team's average velocity over the last three to five sprints is typically used for release planning. By dividing the total remaining story points in the backlog by the average velocity, the team can forecast how many sprints are needed to complete the remaining work.

Key Points

  • •Measured in story points completed per Sprint
  • •Based on work that meets the Definition of Done
  • •Used for forecasting, not for comparing teams or measuring individual performance
  • •Average of three to five sprints provides the most reliable forecast

Exam Tip

Velocity is a planning tool, not a performance measure. Exam answers that use velocity to compare teams or pressure individuals are incorrect.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Velocity

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.