Metrics and Modeling – Helping Teams See How to Improve
summary
Argues that simple, balanced dashboards beat vanity metrics and gives concrete examples: a public naughty list of developers with 10+ bugs leads to gaming and more production defects; showing throughput across four quadrants causes delivery to fall from about 22 pieces/week down to single digits when quality is overemphasized; converting bug counts into days to zero makes debt personal and improves tradeoffs. Uses Tableau and text clustering of bug descriptions and supplies canned coaching actions tied to trends.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:28Types of Analytics
- 2:51Vanity Metrics
- 6:24Measuring Individuals
- 10:50Balance
- 14:16Impact
- 17:55Box Reviews
- 19:42Data Visualization
- 21:05Top takeaways
related talks
01h 01mFinding Metrics that matter and using them safely
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
14mWhat dashboards don't tell you
20mHow to Communicate Metrics to Build Engagement
39mTest Metrics – a thread or a threat
41mRethinking Measurement for High-Performing Teams
12mGamify the Metrics, Amplify the Impact
06mDelivery Metrics: the good, the bad, and the totally ridiculous