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