The Agile team’s guide to harnessing change and responding to disruption
summary
Practical incident management for Agile teams that claims to cut cost and confusion by prescribing specific roles and artifacts and showing exactly how they use them. Teams spin up a video call, name an incident manager and a decision maker, create an incident status page (template in Google Docs or Confluence) and update every few minutes, use Slack and Zoom for alerts, capture screenshots, run an advice process, and follow a blameless postmortem and incident report. Example restores a healthcare site and prevents repeat failures.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:27What is an incident?
- 7:11Why do we talk about incident management?
- 9:15Benefits of an incident management play + Collaboration
- 12:28You may detect an incident in several ways
- 14:51Tools you'll need for open, honest, frequent communication
- 17:55Determine the incident team
- 20:29Status page
- 24:05Engage in the advice process
- 28:37Closing communications, wrap up
- 34:49The blameless post mortem
- 52:38PLEASE PROVIDE YOUR FEEDBACK!
related talks
39mNavigating the Chaos: A Holistic Approach to Incident Management
27mManaging Incidents
32mIncident Management - Talk the Talk, Walk the Walk
48mIncident Management - Talk the Talk, Walk the Walk
01h 04mIncident Management - Talk the Talk, Walk the Walk
27mLessons from Incident Management and Postmortems at Atlassian
13mThe Incident Is The Way: Using Your Incidents to Win...
15mSustainable Incident Management for happy SRE teams