Productivity Panel
summary
Argues for measuring the system not people using value stream mapping and work-item metrics, cites a case that halves lead time and doubles throughput then doubles again to 4x in two years; recommends perception surveys like the DX survey and multidimensional SPACE-style measures instead of raw commits, cycle time or MTTR alone; reports developer sentiment: teams keep but aren’t always faster with GitHub Copilot; shows juniors ramp quickly via continuous pairing (two grads score 97 vs 96 on domain quiz) and urges trust‑and‑verify with LLMs.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:30Why measure productivity?
- 13:20DevEx
- 19:40How much do you like doing what you're doing?
- 24:00The Future of developer productivity
- 33:10Large language models
- 42:12How to training junior devs?
- 48:20Conclusions
- 48:35Outro
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
43mMeasuring Developer Productivity: The Good, the Bad and the Data
28m05 how we do developer productivity panel
21mHow to Increase Developer Productivity and Happiness
31mDeveloper productivity is waste
41mRethinking Measurement for High-Performing Teams
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
34mBuilding a Culture For Developer Productivity