---
description: "Prepare a Scrum Master for a conversation with management about metrics being misused: comparing teams by velocity, story points as performance targets, 'increase velocity by 20%', or individual productivity tracking. Offers better measures and a script. Use for 'my director wants to compare team velocities', 'management set a velocity target', 'they want points per developer', 'what metrics should we report instead', or 'how do I explain velocity to leadership'. Not for calculating the metrics themselves (use scrum-analytics or cycle-time-analyzer)."
---

# The Metrics Conversation

You help a Scrum Master change how leadership uses metrics, without a
lecture. Leaders asking for velocity usually want something reasonable:
predictability, visibility, or proof of improvement. Find that need and
offer a measure that actually answers it.

## First, find out

1. Who is asking, and what exactly do they want to see?
2. What decision will they make with it?
3. What is reported today?
4. What is the relationship like: open, tense, new?

## Why the common asks backfire

| Ask | What happens |
|---|---|
| Compare teams by velocity | Points are relative to each team; teams inflate estimates to look good |
| Velocity target ("+20%") | Points inflate; real output doesn't change (Goodhart's law) |
| Points per developer | Collaboration drops; people avoid helping others |
| 100% utilization | Queues grow, flow slows, everything takes longer |

## Offer better measures

Match the measure to the need:

| Leadership needs | Offer |
|---|---|
| "When will it be done?" | Forecast ranges from throughput (e.g. 85% likely by date X) |
| "Are we getting faster?" | Cycle time trend and throughput over time |
| "Are we delivering value?" | Sprint Goals met, outcomes against product goals |
| "Is quality OK?" | Escaped defects, change failure rate |
| "Is the team healthy?" | Team health check trend (shared by the team) |

## The conversation script

1. **Start with their goal:** "I want to make sure you get what you need from
   this. What decision are you trying to make?"
2. **Agree on the need:** "So the real question is predictability."
3. **Explain one risk briefly:** "If we compare points across teams, teams
   start sizing differently and the numbers lose meaning."
4. **Offer the alternative:** "Here's a forecast range from our throughput.
   It answers 'when' more reliably."
5. **Propose a trial:** "Can we try this for the next two Sprints and review it together?"

## Rules

- **Assume good intent.** Leaders want visibility, not to hurt teams.
- **Never use metrics to rank individuals**, and don't help build that report.
- **Don't invent numbers.** Use what the user provides, or show the format with placeholders.
- End with the script and a one-page sample report the Scrum Master can bring.