Velocity

Velocity

Introduction: Why This Matters

In Agile, teams must understand how much work they can realistically complete during a sprint. Velocity provides this measure. It tracks the number of story points (or backlog items) a team successfully completes per iteration. Over time, velocity stabilizes and becomes a reliable forecasting tool.

On the PMP exam, velocity often appears in situational questions about forecasting, planning, or measuring team progress. In practice, velocity helps teams set sustainable commitments, improves predictability, and fosters stakeholder confidence.

Purpose and Objectives

Primary Purpose: To measure the throughput of an Agile team so future work can be forecast with greater accuracy.

Key Objectives:

  • Define velocity and how it is calculated.
  • Understand how velocity is used for sprint planning and release forecasting.
  • Recognize why velocity should never be used as a performance metric.
  • Apply velocity concepts to PMP exam situational questions.
  • Identify pitfalls that undermine the usefulness of velocity.

Overview

Velocity is a practical forecasting tool based on what a team has actually completed in prior sprints, using consistent estimation.

  • Measures: Completed story points (or completed backlog items) per sprint.
  • Used For: Sprint planning, release forecasting, and capacity planning.

Characteristics

  • Completion-based: Only fully completed items count toward velocity.
  • Team-specific: Velocity is unique to each team and should not be compared across teams.
  • Stabilizes over time: Velocity tends to stabilize after about 3 to 5 sprints.
  • Forecasting-focused: Used to predict how much work can be completed in future iterations.
  • Not a performance metric: It measures throughput, not productivity or individual output.

Practical Example

Context: A Scrum team tracks completed story points across four sprints to forecast future capacity.

Activities:

  • Sprint 1: 18 points completed
  • Sprint 2: 22 points completed
  • Sprint 3: 25 points completed
  • Sprint 4: 20 points completed

Outcome: Average Velocity = (18 + 22 + 25 + 20) ÷ 4 = 21.25, which rounds to about 21 points per sprint. The team can plan around 21 points next sprint. If the backlog contains 210 story points, the team will likely need around 10 sprints to complete it.

Common Pitfalls

Misusing Velocity as a Performance Metric

  • Pitfall: Treating velocity as a productivity score for individuals or teams.
  • Prevention: Use velocity for forecasting and planning, not evaluation or compensation.

Comparing Velocity Between Teams

  • Pitfall: Comparing teams as if story points are standardized across the organization.
  • Prevention: Keep velocity comparisons within the same team only, using consistent estimation.

Counting Incomplete Work

  • Pitfall: Including partially completed work to inflate numbers.
  • Prevention: Count only work that meets the Definition of Done.

Expecting Velocity to Stay Constant

  • Pitfall: Assuming velocity will never change, even when team composition or complexity shifts.
  • Prevention: Re-baseline forecasts after meaningful changes (team size, scope, tooling, or interruptions).

Sensei Tip : If the question is really about forecasting, use historical velocity. If it is about “who is performing better,” reject velocity as the metric. That is the trap.

Exam Alert : The PMP exam often tests stakeholder misuse of velocity. Velocity supports forecasting and planning. It is not a performance metric, and it is not valid for comparing teams.

Exam Lens

Patterns on the PMP Exam:

  • Expect questions about forecasting based on historical velocity.
  • Situational questions often highlight stakeholders misunderstanding velocity as a performance measure.
  • Look for context clues such as “team capacity” or “forecasting release dates.”

Sample Question

Question: A Scrum team has an average velocity of 30 story points per sprint. The backlog contains 180 story points. How many sprints are needed to complete the backlog?

  1. 5
  2. 6
  3. 7
  4. 8

Correct Answer: B. 6. 180 ÷ 30 = 6 sprints.

Quick Recap Table

Concept Formula Purpose Exam Watch Point
Velocity Completed story points per sprint Forecast team capacity Only completed items count
Average Velocity Total points ÷ number of sprints Predict future sprints Cannot compare across teams
Release Forecasting Backlog ÷ velocity Estimate total sprints Fluctuations are normal

Key Takeaways

  • Velocity measures team throughput, not individual productivity.
  • Only completed backlog items count toward velocity.
  • Stable velocity supports accurate sprint and release planning.
  • Each team has its own velocity; comparisons are invalid.
  • On the exam, velocity questions often test forecasting and stakeholder communication.

Next Step

With velocity covered, we now proceed to Task Boards and Kanban Boards, which bring transparency and flow management to Agile execution.

Scroll to Top