(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
Incident caused by a Cisco bug
NTH has a network issue
Cherokee says "I am so confused"
Deaven says "drink time"
Team Sync gets cancelled/moved
Column add/drop before code change is released
Someone forgets to enter comp time
Someone mentions our "Silly Little Reports"
Config changes went out before code
Large client is impacted by an incident
Ralph manages to dodge an incident
Deaven makes a 6-7 reference
Someone mentions that the original lead dev for an issue is inactive
Someone brings CIM treats
MS Outage
Someone thanks someone else for something CIM said/did
Ralph tries to hog the incident tickets
The phrase "perfect storm" is used to explain why an issue occurred.
More than 3 incidents in a day
CIM makes a statement that is ignored but ends up being correct
Someone uses a GIF/meme/reaction to say 'jinx' when they message something at the same time
Someone mentions Cherokee knowing Chad
Network Outage!
Someone is double muted
Mantle Mismatch!
Someone blames networking
A pod needs rolled but was not
IWant is slow
Someone misses their PCP
Incident is related to a CHANGE
REVERT (outside of JSD/JSW)
Someone blames a database
Christian/Deaven works a 'secret incident'
A dev claims it worked on their local
Someone asks "where is Christian"
Someone accidentally shows the wrong app while screensharing
The phrase "missed in spec" is used.
Alerting/Monitoring failed
PTE going to Live
Cherokee summons an incident
Christian says hi to the steps first
An incident causes PD to be paused/disabled
Christian doesn't make an incident ticket/assigns Deaven an incident ticket
HOTFIX (outside of JSD/JSW)
Deaven is on time
Someone makes a questionable joke
Required point of contact is at lunch/gym/walking the track
Floor lights adjust randomly
Someone escalates in an old chat
Someone uses a shapes meme
Incident triggered by Joe looking at synthetics
OpenCode/Chatty/Kimi produced code causes an issue
Feature Flag!
Deaven argues about services impacted or components
