Project Management

Please login or join to subscribe to this thread

Have you witnessed or experienced the weaponization of Agile metrics, like cross-team velocity comparisons, in performance reviews?

linkedin twitter facebook   Agile   Ethics   Leadership  
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, 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

ProjectManagement.com - The Agile Enterprise

Sort By:
avatar
Luis Branco CEO| 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.
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo 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.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I have not failed. I've just found 10,000 ways that won't work."

- Thomas Edison

ADVERTISEMENT

Sponsors