Revolutionizing Incident Response

on YouTube ↗28m

" summary

Argues incidents belong in the daily workflow, not an emergency silo, and offers a concrete replacement for the SDLC: the Revolution model with five concentric role-layers (architecting, developing, automating, deploying, operating) and six considerations—testability, security, reliability, observability, flexibility, scalability. Promotes shared accountability over lone responsibility, recommends automating CI/CD tests and measuring baselines (acknowledging flawed metrics like test coverage), cites PagerDuty guidance and classifies incidents into five severity levels to reduce Sev1/2 fire drills.

AI-written summary · about

" chapters (9)

1. 0:00Incident response philosophy
2. 2:29Tech communication nuance
3. 7:27DevOps unintended effects
4. 10:14Beyond DevOps for resilience
5. 11:59Critiquing the Software Development Life Cycle
6. 13:02Revolution model for dev
7. 18:19Democratizing incident accountability
8. 22:35Incidents as normal work
9. 26:31Future of DevOps accountability

" related talks

• 39mRethinking the SDLCEmily Freeman · SREcon21
• 31mFuturistic Luxury Incident ResponseMandi Walls · SREday 2023 London
• 15mIncident Ready: Chaos Engineer Your Incident ResponseRobert Ross · Conf42 Chaos Engineering 2021
• 39mNavigating the Chaos: A Holistic Approach to Incident ManagementHila Fish · Voxxed Days Zürich 2024
• 32mIncident Management - Talk the Talk, Walk the WalkHila Fish · GopherCon UK 2023
• 33mDon't Panic! Effective Incident ResponseQuintessence Anx · Conf42 Site Reliability Engineering 2021
• 31mThe Art of Turning Incidents into OpportunitiesBusra Koken · devopsdays Amsterdam 2023
• 30mHow To Have An Operational Incident (a crash course)Courtney Eckhardt · PyCon AU 2023