Measuring software delivery performance should focus not just on day-to-day operations, but also on the time it takes to recover from a deployment failure. By asking specific questions about the recovery time after a change or release to production, organizations can gather valuable insights. This includes identifying the time it takes to restore service after a change results in degraded service, which helps to pinpoint the impact of deployment failures on overall performance. Changing the label to 'failed deployment recovery time' signals a shift in focus and highlights the importance of effectively managing recovery from deployment failures.
This week’s episode dives into the DORA research program and this year’s State of DevOps Report. Nathen Harvey, who leads DORA at Google, shares the key findings from the research and what’s changed since previous reports.
Discussion points:
- (1:10) What DORA focuses on
- (2:17) Where the DORA metrics fit
- (4:35) Introduction to user-centric software development
- (8:05) Impact of user-centricity on software delivery
- (9:40) Team performance vs. organizational performance
- (13:50) Importance of internal documentation
- (15:19) Methodology for designing surveys
- (19:52) Impact of documentation on software delivery
- (23:11) Reemergence of the Elite cluster
- (25:55) Advice for leaders leveraging benchmarks
- (28:30) Redefining MTTR
- (33:45) Changing how Change Failure Rate is measured
- (36:45) Impact of AI on software delivery
- (41:25) Impact of code review speed
Mentions and links: