Gaming Velocity — How Not to Measure Success and What to Avoid¶
Wolpers, S. (2024). Gaming Velocity — How Not to Measure Success and What to Avoid. Scrum.org.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Agile Sprint
- Worse, once "velocity" becomes a target the team is measured on, it stops being a useful measure and starts being gamed: stories get inflated, corners cut, the number climbs while the product stalls.
This sourceWarns that evaluating teams by increasing velocity invites inflated estimates and trivialized stories, raising reported velocity without greater productivity or delivered value.
- Worse, once "velocity" becomes a target the team is measured on, it stops being a useful measure and starts being gamed: stories get inflated, corners cut, the number climbs while the product stalls.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:494fe9451988 · see in the full table