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