Rethinking Measurement for High-Performing Teams
summary
Argues for team-level measures tied to business ROI rather than individual vanity stats, showing concrete tooling and outcomes: tracked PR-review lag via GitHub API to find a reviewer bottleneck; Azure board surfaced worst repos by aggregating merge time, comments and CI data; platform engineers join feature teams to clean repos and platform team fixed repos and metrics improved; uses Datadog, Play Store data and spreadsheets for CI and sprint health, noting one team’s sprint health fell from 95% to 70% and required different metric choices.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:20Developer performance challenges
- 8:10Dangers of individual metrics
- 13:33Team metrics risks
- 16:46Sprint health and communication
- 21:06Wrong behavior incentives
- 22:33Promotion criteria
- 26:10Learning and retention metrics
- 29:48Engineering to business value
- 33:02Detecting anomalies
- 35:11Complexity vs story points
- 38:02Adapting metrics
- 40:10Q&A
related talks
25mRethinking measurement for high-performing teams
33mMeasuring Developer Productivity: the good, the bad and the data
39mDev Team Metrics that Matter
01h 02mMeasuring Performance in Development Teams
47mCan We Measure Developer Productivity?
06mDelivery Metrics: the good, the bad, and the totally ridiculous
43mMeasuring Developer Productivity: The Good, the Bad and the Data
23mMeasure for change