Challenges of Starting an SRE Team from Scratch in an Enterprise
summary
Large enterprise (100k+ employees) starts SRE work in March 2020 by reallocating existing engineers rather than hiring, creates BT Sentinel for automated discovery and remediation (example: 90‑day unused credential disable with Slack notice then auto-remediate), aligns standards to the AWS Well-Architected pillars, runs chaos engineering in non‑prod, reports scores of level two maturity with BT=16 and traditional SRE=11, focuses on automation, cost reductions and faster, safer cloud self‑service.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:45Presentation Overview
- 2:25BT Background
- 3:27Waynes Background
- 3:54Waynes Story
- 5:19Where to Start
- 7:24Challenges
- 13:58Management
- 14:37The Solution
- 15:01Goals
- 21:45Planning and Organizing
- 22:35Cloud Sprawl
- 23:04Cloud Computing Standards
- 27:44Chaos Engineering
- 28:19SRE at BT
- 28:57SRE in Engineering
- 30:25Summary
- 31:42Conclusion
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
30mThe Path to SRE
41mBuilding an SRE Capability Inside a Large Organization
28mEvolution of SRE and Rising Need of SRE Catalyzers
18mSRE Engagement Model Transition in Building and Expanding SRE Team
23mSite Reliability Evangelism: Practice Start-up within an Established...
45mClearing the Way for SRE in the Enterprise
25mSRE Guiding Principles & Transformational Framework