A newduckspawnsSomeoneblamesnetworkingIWantis slowIncidenttriggered byJoe lookingat syntheticsMantleMismatch!Someonemakes aquestionablejokeREVERT(outsideofJSD/JSW)Christiansays hi tothe stepsfirstThe phrase"missed inspec" isused.NTH hasa networkissuePTEgoingto LiveIncident isrelated toaCHANGESomeoneaccidentallyshows thewrong appwhilescreensharingFeatureFlag!Deavenis ontimeSomeonethankssomeone elsefor somethingCIM said/didRequired point ofcontact is atlunch/gym/walkingthe trackSomeoneforgets toentercomp timeA devclaims itworked ontheir localSomeonemissestheir PCPSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeRalph triesto hog theincidentticketsAlerting/MonitoringfailedColumnadd/dropbefore codechange isreleasedDerekcomes byand asks"how are welooking?"CIM makes astatement thatis ignored butends up beingcorrectSomeonementionsCherokeeknowingChadHOTFIX(outsideofJSD/JSW)FloorlightsadjustrandomlyRalphmanagesto dodgean incidentTechTalk/Webinarcauses an issueMSOutageA Time andAttendancebug causedan incidentThe phrase"perfect storm"is used toexplain why anissue occurred.Deavenmakes a6-7referenceA podneedsrolled butwas notChristiandoesn't makean incidentticket/assignsDeaven anincident ticketNetworkOutage!An incidentcauses PD to bepaused/disabledDeavensays"drinktime"Christian/Deavenworks a 'secretincident'Team Sync getscancelled/movedSomeoneuses ashapesmemeConfigchangeswent outbefore codeSomeonebringsCIM treatsSomeoneescalatesin an oldchatIncidentcaused bya CiscobugCherokeesays "I amsoconfused"OpenCode/Chatty/Kimiproduced code causesan issueSomeonementions thatthe original leaddev for an issueis inactiveMore than3incidentsin a dayDeavenargues aboutservicesimpacted orcomponentsSomeoneis doublemutedSomeonesuggestsDerek is arobotSomeoneasks"where isChristian"Someonementions our"Silly LittleReports"Someoneblames adatabaseLarge clientis impactedby anincidentCherokeesummonsanincidentA newduckspawnsSomeoneblamesnetworkingIWantis slowIncidenttriggered byJoe lookingat syntheticsMantleMismatch!Someonemakes aquestionablejokeREVERT(outsideofJSD/JSW)Christiansays hi tothe stepsfirstThe phrase"missed inspec" isused.NTH hasa networkissuePTEgoingto LiveIncident isrelated toaCHANGESomeoneaccidentallyshows thewrong appwhilescreensharingFeatureFlag!Deavenis ontimeSomeonethankssomeone elsefor somethingCIM said/didRequired point ofcontact is atlunch/gym/walkingthe trackSomeoneforgets toentercomp timeA devclaims itworked ontheir localSomeonemissestheir PCPSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeRalph triesto hog theincidentticketsAlerting/MonitoringfailedColumnadd/dropbefore codechange isreleasedDerekcomes byand asks"how are welooking?"CIM makes astatement thatis ignored butends up beingcorrectSomeonementionsCherokeeknowingChadHOTFIX(outsideofJSD/JSW)FloorlightsadjustrandomlyRalphmanagesto dodgean incidentTechTalk/Webinarcauses an issueMSOutageA Time andAttendancebug causedan incidentThe phrase"perfect storm"is used toexplain why anissue occurred.Deavenmakes a6-7referenceA podneedsrolled butwas notChristiandoesn't makean incidentticket/assignsDeaven anincident ticketNetworkOutage!An incidentcauses PD to bepaused/disabledDeavensays"drinktime"Christian/Deavenworks a 'secretincident'Team Sync getscancelled/movedSomeoneuses ashapesmemeConfigchangeswent outbefore codeSomeonebringsCIM treatsSomeoneescalatesin an oldchatIncidentcaused bya CiscobugCherokeesays "I amsoconfused"OpenCode/Chatty/Kimiproduced code causesan issueSomeonementions thatthe original leaddev for an issueis inactiveMore than3incidentsin a dayDeavenargues aboutservicesimpacted orcomponentsSomeoneis doublemutedSomeonesuggestsDerek is arobotSomeoneasks"where isChristian"Someonementions our"Silly LittleReports"Someoneblames adatabaseLarge clientis impactedby anincidentCherokeesummonsanincident

CIM Bingo - Call List

(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
  1. A new duck spawns
  2. Someone blames networking
  3. IWant is slow
  4. Incident triggered by Joe looking at synthetics
  5. Mantle Mismatch!
  6. Someone makes a questionable joke
  7. REVERT (outside of JSD/JSW)
  8. Christian says hi to the steps first
  9. The phrase "missed in spec" is used.
  10. NTH has a network issue
  11. PTE going to Live
  12. Incident is related to a CHANGE
  13. Someone accidentally shows the wrong app while screensharing
  14. Feature Flag!
  15. Deaven is on time
  16. Someone thanks someone else for something CIM said/did
  17. Required point of contact is at lunch/gym/walking the track
  18. Someone forgets to enter comp time
  19. A dev claims it worked on their local
  20. Someone misses their PCP
  21. Someone uses a GIF/meme/reaction to say 'jinx' when they message something at the same time
  22. Ralph tries to hog the incident tickets
  23. Alerting/Monitoring failed
  24. Column add/drop before code change is released
  25. Derek comes by and asks "how are we looking?"
  26. CIM makes a statement that is ignored but ends up being correct
  27. Someone mentions Cherokee knowing Chad
  28. HOTFIX (outside of JSD/JSW)
  29. Floor lights adjust randomly
  30. Ralph manages to dodge an incident
  31. TechTalk/Webinar causes an issue
  32. MS Outage
  33. A Time and Attendance bug caused an incident
  34. The phrase "perfect storm" is used to explain why an issue occurred.
  35. Deaven makes a 6-7 reference
  36. A pod needs rolled but was not
  37. Christian doesn't make an incident ticket/assigns Deaven an incident ticket
  38. Network Outage!
  39. An incident causes PD to be paused/disabled
  40. Deaven says "drink time"
  41. Christian/Deaven works a 'secret incident'
  42. Team Sync gets cancelled/moved
  43. Someone uses a shapes meme
  44. Config changes went out before code
  45. Someone brings CIM treats
  46. Someone escalates in an old chat
  47. Incident caused by a Cisco bug
  48. Cherokee says "I am so confused"
  49. OpenCode/Chatty/Kimi produced code causes an issue
  50. Someone mentions that the original lead dev for an issue is inactive
  51. More than 3 incidents in a day
  52. Deaven argues about services impacted or components
  53. Someone is double muted
  54. Someone suggests Derek is a robot
  55. Someone asks "where is Christian"
  56. Someone mentions our "Silly Little Reports"
  57. Someone blames a database
  58. Large client is impacted by an incident
  59. Cherokee summons an incident