Using Velocity Honestly: A Field Guide for Scrum Teams
Velocity is one of the most useful numbers a Scrum Team has and one of the easiest to misuse. At its core it is simply the amount of work a team finishes in a Sprint, measured in whatever unit the team estimates with — usually story points. Used well, it helps a team forecast how much it can realistically take on. Used badly, it becomes a stick managers wave to demand more, and teams quietly inflate their estimates until the number means nothing. The difference is entirely in how honestly you treat it.
It is worth being precise about what the Scrum Guide does and does not say. Velocity is not a Scrum artefact and the guide does not mandate it. It is a complementary practice many teams adopt. That matters, because it means velocity serves the team's planning — not the other way around.
What velocity is actually for
Velocity answers one question: based on what we have completed before, roughly how much can we commit to next Sprint? Take the average of your last several Sprints and use it as a sanity check during Sprint Planning. If the team is pulling in twenty points when its average is twelve, that is a conversation, not a target to celebrate.
Forecasting how many Sprints a body of work may take, as a range rather than a promise
Spotting trends — a steady decline often signals growing technical debt or unclear requirements
Giving the team a reality check during Sprint Planning, so commitments stay achievable
How to keep it honest
Only count work that meets the Definition of Done. Partially finished items earn zero velocity, not partial credit. Counting half-done work is the fastest way to make the number lie, because it hides carry-over and inflates the average.
Never compare velocity between teams. Points are calibrated locally; one team's eight is another team's three. Comparing teams' velocities punishes honest estimators and rewards point inflation. Velocity is meaningful only as a team's own trend over time.
Keep it out of performance reviews. The moment velocity is tied to appraisals or bonuses, it stops measuring delivery and starts measuring how good the team is at gaming the number. Protect it as a planning tool the team owns.
Expect it to wobble, and read the wobble. A drop after holidays, illness, or — in 2022 — a stretch of hybrid disruption is normal. Don't smooth it away; ask what it is telling you about capacity and flow.
Re-baseline after big changes. When members join or leave, or the team re-estimates its scale, old velocity no longer compares cleanly. Treat the next few Sprints as recalibration rather than regression.
A quiet test of a healthy team
Here is a simple signal. On a team that uses velocity honestly, people will openly say a Sprint went slowly and explain why. On a team where velocity has been weaponized, the number stays suspiciously smooth and nobody admits a bad Sprint, because admitting it carries a cost. If your velocity never dips, that is not a sign of excellence — it is a sign that estimates are absorbing the variance the metric is supposed to reveal. Used honestly, velocity is a mirror the team holds up to its own delivery. The Scrum Master's job is to keep that mirror from being turned into a scoreboard.
If your teams are wrestling with metrics that have drifted from planning into pressure, XNM's program & project delivery advisory can help you rebuild forecasting your people trust.