tezvyn:

Why is tracking team velocity as a KPI dysfunctional?

Source: holub.comintermediate

Tests if you know velocity is for planning, not performance. Explain it's easily gamed and measures output, not outcome. Propose metrics focused on value delivery and process improvement like cycle time.

This tests your grasp of agile principles, distinguishing planning tools from performance metrics. It probes your ability to steer leadership toward healthy practices. Start by defining velocity as a team-specific planning tool. Detail its dysfunctions: it's easily gamed (point inflation) and measures output over outcome. Then, propose alternatives focused on value and flow, like cycle time, lead time, and customer satisfaction (NPS). The biggest red flag is defending velocity as a performance metric or comparing it between teams.

Read the original → holub.com

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

Why is tracking team velocity as a KPI dysfunctional? · Tezvyn