What is "velocity" in Scrum? Please define velocity, how is it calculated, what is…
- User
What is "velocity" in Scrum? Please define velocity, how is it calculated, what is velocity used for? (For planning future sprints), and why should velocity not be used as a performance metric to compare different teams.
- Assistant
Okay, the user is asking about "velocity" in Scrum. They want a clear definition, calculation method, usage for future sprint planning, and an explanation of why it shouldn't be used as a cross-team performance metric.
First, I need to define velocity as a measure of completed story points per sprint. It's a team-specific metric, not a speed benchmark. Then, explain how it's calculated: sum of story points for all "Done" backlog items in a sprint. Emphasize it's an average over time, not a single sprint's value.
For usage, stress that velocity helps with forecasting and capacity planning, not as a target. Teams use it to estimate how much they can commit in future sprints.
The most critical part is explaining why it's bad for cross-team comparisons. Need to highlight that each team's point scale is unique, comparing them is like comparing apples to oranges. Also, velocity reflects past performance with varying contexts, and pressures to inflate points undermine its purpose.
Should warn against managing to a velocity target because it leads to gaming the system. The core message: velocity is a tactical tool for the team itself, not a performance scoreboard. Keep it practical and avoid jargon where possible. Excellent question. "Velocity" is one of the most commonly discussed and often misunderstood metrics in Scrum. Here’s a clear breakdown.
1. Definition
Velocity is a metric that measures the amount of work (in abstract units, usually Story Points) a Scrum Team completes and delivers in a single Sprint. It is a historical average that indicates the team's sustainable throughput or capacity over time.
Key idea: It's a planning tool, not a performance target. It answers the question: "Based on our recent past, how much work can we realistically commit to in the next Sprint?"
2. How is Velocity Calculated?
The calculation is straightforward but must be done precisely:
- At the end of a Sprint, during the Sprint Review/Retrospective, sum the Story Points of all Product Backlog items that were fully completed (met the Definition of "Done").
- Items that were partially done but not "Done" by the end of the Sprint are not counted. Points are only counted for value delivered.
- The velocity for that specific Sprint is that sum.
- The team's velocity is the average of these Sprint velocities over a period (typically 3-5 sprints) to smooth out anomalies (e.g., a sprint with holidays, an unusually high-priority bug fix that consumed capacity).
Example:
- Sprint 1: 23 points completed
- Sprint 2: 30 points completed
- Sprint 3: 27 points completed
- Average Velocity = (23 + 30 + 27) / 3 = 26.7 points
3. What is Velocity Used For? (Sprint Planning)
The primary purpose is forecasting and capacity planning for future Sprints.
- Forecasting the Sprint Backlog: During Sprint Planning, the Product Owner presents the ordered Product Backlog. The Development Team uses its historical velocity to determine how many story points they can likely select from the top of the backlog for the upcoming Sprint. They pull in items up to their average velocity (or a slightly adjusted number based on team availability, holidays, etc.).
- Creating a Release Plan: By knowing the team's average velocity and the total remaining points in the Product Backlog (for a specific release goal), a rough estimate of how many Sprints the release will take can be calculated. This is a forecast, not a guarantee.
- Identifying Trends: A stable or slightly improving velocity suggests a predictable, sustainable pace. A wildly fluctuating or declining velocity is a signal for the team to inspect their process in the Retrospective (Are there impediments? Is the Definition of Done changing? Is the team composition stable?).
4. Why Velocity Should NOT Be Used as a Performance Metric to Compare Different Teams
This is the most critical and frequently violated principle. Using velocity to compare teams is meaningless and dangerous. Here’s why:
Reason Explanation 1. Point Scales are Arbitrary & Local A "5-point story" in Team A is not the same as a "5-point story" in Team B. Each team defines their own point scale based on their unique context, technology, skills, and past work. There is no universal standard. Comparing them is like comparing "green" of two different paint brands. 2. Velocity Reflects Context, Not Just Skill A team's velocity is influenced by:• Domain/Product Complexity: Working on a legacy banking system vs. a new marketing website.• Technical Debt & Architecture: A team drowning in debt will have lower velocity.• Team Size & Composition: A team of 7 vs. a team of 4.• Definition of Done: "Done" for one team might include security review, performance testing, and documentation; for another, it might be just code complete.• Dependencies & External Factors: How many other teams does this team depend on? How often are they interrupted by production issues? 3. It Encourages Game-Playing ("Point Inflation") If management starts comparing velocities, teams will artificially inflate their point estimates to look better. This completely destroys the purpose of the metric—planning based on realistic historical throughput. A team that inflates points will consistently "fail" to meet their forecast, leading to the wrong conclusions about their performance. 4. It Violates the Scrum Value of "Respect" Comparing teams creates competition, blame, and shame. Scrum emphasizes team accountability, not individual or team competition. The goal is for each team to improve their own effectiveness and predictability. Comparing teams undermines collaboration, knowledge sharing, and the systemic view of value delivery. 5. It Measures Output, Not Outcome or Value High velocity does not mean a team is delivering more value or better outcomes. It might mean they are building the wrong thing faster, or cutting quality (which eventually slows velocity). The ultimate measure is the value of the product to the customer and business. TL;DR Summary
- Velocity is: A team-specific measure of completed story points over time.
- Use it for: Internal forecasting and capacity planning for that team's next Sprint or release.
- Never use it to: Compare teams, evaluate performance, or set targets. It is a tactical planning aid, not a strategic performance scoreboard.
The golden rule: A team's velocity is only meaningful to itself. If you see an organization comparing velocities across teams, it's a strong sign that Scrum is not being understood or implemented correctly, and the metric is being subverted for toxic management purposes.