Enhancing the Performance of Engineering Teams
summary
Practical checklist: adopt DORA metrics (lead time, deploy frequency, change-failure rate, MTTR) and grade against Elite vs low performers — elites deploy multiple times per day, some teams deploy < once per six months; measure percentage strategic vs tactical work via Jira to stop firefighting; cut context switching (one example: people spending 6.5 hours in meetings), shift quality ownership toward developers with automated tests and CI/CD, invest in onboarding and living documentation to reduce bus factor, and treat metrics as guides not targets.
AI-written summary · about
chapters (20)
- 0:00Team performance enhancement
- 3:25Team productivity factors
- 5:57Organizational setup impact
- 7:43Context switching and flow
- 9:53Workload and burnout risks
- 10:58Code quality impact
- 12:45Communication and planning issues
- 13:06Engineering productivity metrics debate
- 17:48Qualitative team metrics
- 21:03Measuring context switching
- 22:28DORA metrics and deployments
- 26:43Empowered engineering environment
- 28:07Transparent communication
- 30:17Output and customer impact
- 31:20Onboarding best practices
- 34:10Effective performance reviews
- 35:14Processes and quality ownership
- 37:20Managing technical debt
- 40:52Avoiding hype and real impact
- 43:19Summary and call to action
related talks
22mLeading software teams with context (visibility)
39mDev Team Metrics that Matter
30mThe Sociotechnical Path to High-Performing Teams
14mI don't think these metrics mean what you think they mean!
33m7 habits of a high performing team
15mDev Team Metrics that Matter
10mAchieving engineering velocity by optimising developer experience
15mOptimizing the engineering value stream