War Games – prepare for the unexpected
summary
Claims that running tabletop war games with ~15 people and longer environment-based war games (up to 6 hours, 20–30 participants) uncovers real weaknesses, shortens MTTR and protects revenue; concrete exercises include kill an ECS instance via AWS console and scripted third‑party response templates, using Chaos Toolkit and manual steps rather than full automation. Runs cost prep time and test environments but identified fixes, were retested, and organizers report benefits outweigh costs.
AI-written summary · about
chapters (16)
- 0:00intro
- 0:22preamble
- 2:12chaos and systems
- 4:24chaos engineering war games
- 5:49system current state
- 7:29stake holders
- 11:15tabletop war game
- 14:30environment based war game
- 22:18gamification
- 24:23start easy
- 26:23exercises
- 28:54participants
- 32:17goals
- 34:21delivering results
- 36:23publicise
- 38:40thank you!
related talks
33mGames We Play to Improve Incident Response Effectiveness
47mChaos Engineering Bottom Up
46mGames We Play to Improve on Incident Response
01h 08mWorkshop: Run your first game day
20mChaos: breaking your systems to make them unbreakable
38mRunning DRP Tabletop Exercises
31mPlanning for Failure using Chaos Engineering
40mBecoming a Gamemaster: Designing IT Emergency Operations and Drills