From Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
Talkat SREcon19 Europe/Middle East/Africa · on Wednesday, 2019-10-02· at 14:30· Track 2: The Liffey A·
summary
Built SRE from zero inside a ~30‑engineer edtech company, growing an SRE team to 2–4 people and discovering a sustainable on‑call needs ~8 people (~40% of engineers) so the chosen solution is to make everyone is an SRE by returning ownership to developers and creating a small platform/production engineering layer. That layer provides shared CI/CD, monitoring and instrumentation frameworks, enables blameless postmortems, reduces gates, measures positive signals like cycle time and user satisfaction rather than incident counts, and proves to increase deployment speed and team autonomy.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:00Where do I start
- 1:40Oncall
- 2:43Why SRE is relevant
- 3:21Common challenges
- 3:32IT Software Engineering
- 4:01Complexity
- 4:50Risk
- 5:46Where do we start
- 6:13Culture
- 6:52The Conventional Way
- 7:44The Alternative Way
- 8:37The Handoff Word
- 9:49Ryan Kitchens Netflix
- 11:31Reliability
- 12:46Incentives
- 13:35Gates
- 15:15SRE is a force multiplier
- 16:09How users feel matters
- 17:17Unsolved problems
- 17:43Architecture
- 17:59SRE Community
- 18:39Questions
related talks
25mSRE Guiding Principles & Transformational Framework
41mBuilding an SRE Capability Inside a Large Organization
18mDeploying Humans at the Edge of SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
23mSite Reliability Evangelism: Practice Start-up within an Established...
18mSRE Engagement Model Transition in Building and Expanding SRE Team
30mThe Path to SRE