How Do You Measure Devel...
summary
Panelists argue developer productivity equals measurable system outcomes not lines of code, centering on time to impact, low cognitive load and fast feedback loops; they cite DX Core, DORA/SPACE research, Backstage/IDP adoption and a case that improved delivery by months (target Sept moved to Aug) as proof of ROI. Metrics combine tool telemetry with surveys, emphasize aggregate signals (never per-person), and translate into business measures like cost of delay and revenue per engineer via a developer experience index while pursuing incremental 2% improvements and a firm rule: don't measure individuals.
AI-written summary · about
chapters (14)
- 0:00Welcome and panel
- 1:05Defining productivity
- 8:06Why productivity is controversial
- 13:45Productivity as a system
- 15:10Language matters
- 17:41Developer experience and culture
- 19:06Convincing stakeholders
- 21:12Measure system not individual
- 22:16Qualitative and quantitative data
- 24:21Bringing developers into conversation
- 25:45Normalizing feedback loops
- 27:29Metrics for investing in DX
- 29:17Cost of delay and revenue per engineer
- 30:22Closing remarks
related talks
47mCan We Measure Developer Productivity?
43mMeasuring Developer Productivity: The Good, the Bad and the Data
33mMeasuring Developer Productivity: the good, the bad and the data
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
33mBeyond developer productivity: what's next?
18mFrom developer productivity to engineering impact
10mAchieving engineering velocity by optimising developer experience
28m05 how we do developer productivity panel