Move to Integrated SRE Ops at a Retail organization
summary
16-week proof embeds an SRE into three product teams across two brands on a microservices stack (Azure, Kubernetes, Azure DevOps) and builds a 27-capability maturity framework. Outcomes: dev:ops 3:1 becomes one SRE per product (later shared), monthly incidents drop from double digits to single digits, releases move from monthly to three times weekly then at-will, >80% operational maturity, automated change gate (ServiceNow), Splunk alert→incident and SLIs tied to functional flows for customer-facing metrics.
AI-written summary · about
chapters (9)
- 0:00Introduction to the Presentation
- 0:29Traditional Setup and Divergent Goals
- 3:22Proof of Value: Initial Steps
- 4:53Embedding SRE in Product Teams
- 6:22Assessment and Improvements
- 9:37Outcomes and Benefits
- 13:38Scaling and Sustaining SRE
- 17:42Governance and Future Plans
- 19:36Conclusion and Way Forward
related talks
27mMean Time To SRE: A DevOps story from adidas
30mThe Path to SRE
30mDifferences in SRE Implementations across Companies
18mSRE Engagement Model Transition in Building and Expanding SRE Team
21mOne year of SRE Failures
58mEnterprise Roadmap for SRE
23mThe Why, What, and How of Starting an SRE Engagement
25mUnleashing the potential of SRE for modern operations