Demo: spotting a metric that is being gamed
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
detect and discuss a gamed metric without blaming a team; prepares SRB-014-LAB1.
Draft outline details
Step by step
- Notice that deployment frequency jumped for one team while features delivered stayed flat.
- Check companions: change size, lead time, failure rate, incident data.
- Read the deploys: many trivial or empty releases found.
- Planned mistake: confront the team with accusations. Fix: ask what the metric pressure felt like and what made frequent releases attractive.
- Remove incentives that created it and adjust the definition (count meaningful changes), or add a companion metric.
- Record what changed and recheck next month.
Check your understanding
How do companion metrics help?
Show answer
A gamed number diverges from the others, exposing the problem.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.