(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Recovery took >1 day
Fix required physical access (no one had keys)
Didn’t have a backup
No runbook available
Power came back... and then went out again
DR plan included a retired employee
DR test failed
Misread a severity alert
Started a DR drill—no one showed up
Oncall during a holiday
External service went down
Saw a mysterious cron job labeled “do not delete”
Got called mid-flight (tried to troubleshoot over airplane Wi-Fi)
Realized the DR test broke something else
Realized you were restoring the wrong day’s backup
Logged incident... to the wrong team
Practiced failover
Couldn’t reach the primary contact
Found passwords in a sticky note
Deployment broke prod
Ignored an alert that was real this time
“It worked in dev”
Backup password was changed but not shared
Ran chaos test in prod
Spent 2 hours debugging—then found it was a typo
Network outage
Deployed during a major incident
Ran a DR stimulation game
Custom script failed with no logs
Tested DR... in prod by accident
Dependency failed silently
Cloud region down
Backup ran... but didn’t include the database
DB migration failed
System alert missed because alert rule was too specific
Lost prod data (even a bit)
The “hot site” was actually cold
Vendor said, “That’s not covered”
Created a backup strategy
Hit restore, regretted immediately
Confused dev and prod environments
DR test passed... because no one actually tested anything
