Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Agile frameworks like Scrum and XP have brought a wealth of transparency and data-driven insights to software delivery. Metrics such as velocity, burndown rates, and throughput are tools for teams to self-assess, plan, and improve. However, these metrics are increasingly being used in ways that were never intended—most notably, as weapons in performance reviews and appraisals. One of the most contentious practices is the comparison of velocity across entirely different teams, a topic that has sparked heated debates in forums and communities worldwide. This blog post explores why comparing the velocity of different Agile teams during performance appraisals is unfair, the damage it causes, and what organizations should do instead.
-Have you witnessed or experienced the weaponization of Agile metrics, like cross-team velocity comparisons, in performance reviews?
-How did it impact your team’s culture, motivation, or reporting practices?
Blog post
Weaponizing Agile Metrics in Performance Reviews: The Unfairness of Comparing Team Velocity
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
An important perspective.
The problem is not simply that velocity comparisons are unfair. The deeper concern is that once a metric becomes a performance target, it stops functioning as a reliable source of learning.
Teams naturally adapt their behavior to the measurement system. The result is often not improved performance, but distorted estimates, degraded data quality and weaker organizational learning.
The greatest damage caused by weaponized metrics is not unfair evaluation. It is the loss of the very signal those metrics were meant to provide.
Metrics should support understanding and improvement, not replace judgment or become instruments of control.
...
1 reply by Stelian ROMAN
Sep 08, 2026 6:15 PM
Stelian ROMAN
...
"The problem is not simply that velocity comparisons are unfair ". It's never that simple :) The problem, like with other tools, is that some teams don't know the context in which the tool was created and how the tool can help them. The Story Points story is fascinating (for me). To be credited with inventing them, and therefore velocity, and apologise for that; it's a very good topic for discussion and a warning for those (mis)using velocity. Any metric can be gamed when there is a reason; therefore, if we remove the reason, we may stop the gaming.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
that's right, velocity comparisons used to evaluate teams, even when the teams had different contexts, types of work, and levels of complexity.
Also individual performance assessed based on the number of story points completed. That approach has always seemed problematic to me because people contribute in different ways. Some take on more complex work, support others, resolve blockers, improve quality, or help the team succeed without necessarily accumulating the most points.
The impact was usually defensive behavior around estimation and less confidence in the metrics themselves. Once people feel they are being judged by the number, the focus can shift from improving delivery to improving the metric.
...
1 reply by Stelian ROMAN
Sep 08, 2026 6:18 PM
Stelian ROMAN
...
Neither comparing teams nor individual performance tracking was considered when story points and velocity were introduced by XP. Story points started as, and are still, an obfuscation of time. The 'ideal days' to complete a task. Relative estimation can be a very powerful tool for a team, but it becomes a huge problem when it is used outside the team or at the individual level.
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jun 19, 2026 6:47 AM
Replying to Luis Branco
...
An important perspective.
The problem is not simply that velocity comparisons are unfair. The deeper concern is that once a metric becomes a performance target, it stops functioning as a reliable source of learning.
Teams naturally adapt their behavior to the measurement system. The result is often not improved performance, but distorted estimates, degraded data quality and weaker organizational learning.
The greatest damage caused by weaponized metrics is not unfair evaluation. It is the loss of the very signal those metrics were meant to provide.
Metrics should support understanding and improvement, not replace judgment or become instruments of control.
"The problem is not simply that velocity comparisons are unfair ". It's never that simple :) The problem, like with other tools, is that some teams don't know the context in which the tool was created and how the tool can help them. The Story Points story is fascinating (for me). To be credited with inventing them, and therefore velocity, and apologise for that; it's a very good topic for discussion and a warning for those (mis)using velocity. Any metric can be gamed when there is a reason; therefore, if we remove the reason, we may stop the gaming. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jun 22, 2026 7:05 PM
Replying to Lissette Indhira Pimentel Sosa
...
that's right, velocity comparisons used to evaluate teams, even when the teams had different contexts, types of work, and levels of complexity.
Also individual performance assessed based on the number of story points completed. That approach has always seemed problematic to me because people contribute in different ways. Some take on more complex work, support others, resolve blockers, improve quality, or help the team succeed without necessarily accumulating the most points.
The impact was usually defensive behavior around estimation and less confidence in the metrics themselves. Once people feel they are being judged by the number, the focus can shift from improving delivery to improving the metric.
Neither comparing teams nor individual performance tracking was considered when story points and velocity were introduced by XP. Story points started as, and are still, an obfuscation of time. The 'ideal days' to complete a task. Relative estimation can be a very powerful tool for a team, but it becomes a huge problem when it is used outside the team or at the individual level. Saving Changes...
Community Champion
