May 19, 2026
6 min read
Metrics anti-patterns
How Teams Misuse Velocity
The most common ways teams misuse velocity, and why a useful planning signal turns toxic surprisingly fast once people ask it to do the wrong job.
Why velocity gets misused so easily
Velocity is attractive because it looks like a clean number that summarizes delivery power. That makes it easy to repeat in planning, status updates, and management conversations.
The problem is that velocity only works well inside a narrow context. It can help one team ask whether a sprint plan is roughly realistic. Once people ask it to compare teams, prove productivity, or guarantee future output, the metric starts doing damage.
Velocity misuse
The metric helps when it stays small and starts hurting when it gets promoted into a score.
Healthy local signal
Velocity can help one team judge whether the current sprint commitment roughly resembles recent delivery reality.
Scoreboard misuse
The number gets repurposed into a productivity story instead of staying a narrow planning input.
Cross-team flattening
Different contexts and point systems get treated like standardized units when they are not.
Behavior distortion
Once the metric becomes a target, teams naturally adapt behavior around the score instead of the workflow.
Context-aware use
Velocity works best alongside readiness, capacity, and known uncertainty rather than pretending it can speak for the whole system.
What velocity is actually good for
In its healthiest form, velocity is a local planning aid. It gives a team one more signal about whether the current sprint commitment resembles what similar work has supported before.
That is a modest job, and it is enough. Velocity does not need to become a universal measure of performance to be useful.
How teams usually misuse it
The most common misuse is turning velocity into a score. Once that happens, the number stops describing the system and starts influencing behavior. Teams begin shaping the metric instead of improving the workflow.
- Using velocity as a productivity scoreboard.
- Treating average velocity like a delivery promise.
- Comparing teams with different contexts and point systems.
- Optimizing the points instead of improving clarity, flow, and scope quality.
Why misuse creates bad behavior
When velocity becomes a target, teams naturally protect themselves. They may inflate story points, push work across sprint boundaries, avoid riskier items, or treat the metric as something to manage politically.
None of that means the people are irrational. It means the system is rewarding the wrong thing. A metric that was supposed to help planning starts distorting planning instead.
Why comparing teams is especially harmful
Team-to-team velocity comparisons are especially misleading because story points are relative, local, and shaped by context. Different teams size differently, work on different problem spaces, and absorb different support load or dependency patterns.
Putting those numbers side by side creates false precision. The comparison feels concrete while hiding the fact that the underlying units are not standardized in a meaningful way.
What healthier use looks like
Healthier teams keep velocity local and interpret it carefully. They use it alongside readiness, capacity, and known uncertainty rather than pretending it can speak for the whole system by itself.
- Use velocity as one planning signal, not as the deciding authority.
- Keep it inside the team context where the point system actually makes sense.
- Let capacity and interruptions modify how strongly the signal should be trusted.
- Watch for behavior changes that suggest the metric is becoming a target.
TL;DR
- Velocity is useful as a local planning signal and harmful as a performance score.
- It gets misused when teams treat it as a promise engine, comparison tool, or target.
- Most bad velocity behavior is a predictable response to asking the metric to do the wrong job.
- Velocity stays useful only when it remains a local planning signal instead of being promoted into promise, score, and comparison system all at once.