A Research Study into DevOps Bottlenecks
summary
A survey of Fortune 500 software delivery leaders identifies three root causes of DevOps bottlenecks—education, automation, and trust—and says addressing them requires investment of money, time, and people. Deployment frequency varied from every two hours to once every two years, with high-frequency teams recovering from incidents in under an hour while low-frequency teams took weeks; effective practices include canary releases, feature flags, a centralized tooling recommendations list that supplies licenses, and funding a pilot team to prove the approach.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:40What is DevOps
- 7:08Release frequency
- 13:36Why fewer releases
- 17:12Top 3 bottlenecks
- 22:20Overcoming change resistance
- 24:28DevOps tools
- 29:08Choosing tools
- 35:38Trust in delivery
- 40:20Summary
- 41:27Q&A
related talks
45mBuilding and Scaling High Performing Technology Organizations
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
34mDevOps: Next
05mInterview
31mThe Data Behind DevOps: What Does It Take To...
50mA Brief History of DevOps
45mDevOps: The Key to IT Performance
33mSecurity, Don't Fear the DevOps