Kickoff + Keynote

on YouTube ↗27m

" summary

Argues for shifting chaos engineering into the SDLC early — start in QA and pre-prod, automate experiments into pipelines and keep “golden copy” certified tests; measures are concrete: count services, teams, experiments, and track chaos coverage and resilience coverage plus resilience score and percent automation. Claims maturity takes two to three years, adoption is under 10% today, and chaos can repurpose DR plans; game days remain useful while Litmus-style resilience probes run automated checks that reduce MTTR when fixes are tracked and fixes block re-running broken experiments.

AI-written summary · about

" chapters (8)

1. 0:00Welcome and introduction to the keynote
2. 1:09Chaos engineering for business growth
3. 3:39Developer efficiency challenges
4. 7:14Chaos engineering in SDLC
5. 10:30Chaos engineering maturity timeline
6. 13:20KPIs for chaos engineering
7. 16:33Best practices for chaos engineering
8. 24:21Q&A

" related talks

• 49mDeveloping a Culture of Reliability & Resilience through ChaosRuss Miles · Agile India 2021
• 44mDeveloping a Culture of Reliability and Resilience through ChaosRuss Miles · Build Stuff 2021
• 36mChaos Engineering in 2021Miko Pawlikowski · Conf42 Chaos Engineering 2021
• 32mTrajectory of ChaosCasey Rosenthal · REdeploy 2019
• 19mFireside Chat with Jason YeeJason Yee · DevOpsDays Chicago 2020
• 26mAchieving Cloud-Native Resiliency: The Evolution of Chaos EngineeringPrithvi Raj Venkat Raj · DevOpsDays Poznań 2021
• 29mImprove Resilience with automated chaos engineeringGunnar Grosch · Conf42 Site Reliability Engineering 2021
• 47mChaos Engineering Bottom UpBart Szulc · Build Stuff 2020