Measuring developer productivity through their own product measurements
summary
Avo instruments teams’ tracking-plan workflow so product changes carry their own analytics: branches define metrics, use typesafe SDK calls (e.g. avo.gameStarted), get peer review, then merge. Productivity is the turnaround from branch open to branch merge within one day with at least one comment to prove collaboration. After shipping branch-collaborators and improved notifications, conversion to that metric rises by 70% in the first week, showing measurable developer speedups.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:59Developer efficiency challenges
- 6:47Qualitative customer learnings
- 9:15Quantifying productivity metrics
- 12:29Metric refinement and results
- 14:39Current measurement approach
related talks
43mMeasuring Developer Productivity: The Good, the Bad and the Data
44mSPACE: Measuring Developer Productivity
36mDeveloper Productivity Engineering: What's in it for me?
34mBuilding a Culture For Developer Productivity
31mDeveloper productivity is waste
27mDevelopers Expose What's Breaking Productivity in Their Companies
41mRethinking Measurement for High-Performing Teams
10mAchieving engineering velocity by optimising developer experience