DO, RE, Me: Measuring the Effectiveness of Site Reliability Engineering
summary
DORA adds SRE-specific survey items (a “duck‑typing” checklist) and finds a small majority of teams practice SRE to some degree; SRE adoption predicts higher reliability and better business outcomes. Success uses the four key metrics (deployment frequency, lead time for changes, change failure rate, time to restore), elite teams deploy roughly ~1000x more often, and teams high in both delivery and reliability are 1.8x more likely to meet commercial goals.
AI-written summary · about
chapters (15)
- 0:00THE ADVANCED COMPUTING SYSTEMS ASSOCIATION
- 0:40SRE implements DevOps
- 2:10What's DevOps?
- 2:45What do we do with that?
- 3:06ADORA +G DEVOPS RESEARCH & ASSESSMENT
- 9:15What's SRE?
- 9:30SRE vs(?) DevOps
- 11:492021: DORA tackles SRE
- 13:50What did we learn?
- 14:1252% of respondents reported the use of SRE practices
- 14:46SRE is good for humans and systems
- 15:10Humans - SRE mitigates burnout - SRE enables balance between coding and ops work Systems - Shared responsibility for operations predicts better røy outcomes - SRE predicts higher reliability Business - Higher reliability predicts better business outcomes
- 15:59Reliability is a force
- 16:47There's room for growth
- 17:18Dave's Hot Takes
related talks
25mCapabilities for Building High-performing Technology Teams
41mSRE in Enterprise
58mEnterprise Roadmap for SRE
43mThe SRE I Aspire to Be
49mWhat SRE Could Be: Systems Reliability Engineering
05mHow do Devops and SRE relate?
30mWhen Is SRE Right For You?
25mUnleashing the potential of SRE for modern operations