IWantis slowChristiandoesn't makean incidentticket/assignsDeaven anincident ticketNetworkOutage!Someoneuses ashapesmemeSomeoneescalatesin an oldchatThe phrase"perfect storm"is used toexplain why anissue occurred.SomeoneblamesnetworkingOpenCode/Chatty/Kimiproduced code causesan issueDeavenmakes a6-7referenceFeatureFlag!SomeonesuggestsDerek is arobotTechTalk/Webinarcauses an issueSomeonemakes aquestionablejokeSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeonementions thatthe original leaddev for an issueis inactiveAn incidentcauses PD to bepaused/disabledDeavenargues aboutservicesimpacted orcomponentsDeavensays"drinktime"CIM makes astatement thatis ignored butends up beingcorrectChristian/Deavenworks a 'secretincident'Derekcomes byand asks"how are welooking?"SomeonementionsCherokeeknowingChadCherokeesummonsanincidentSomeoneasks"where isChristian"Configchangeswent outbefore codeIncident isrelated toaCHANGEMantleMismatch!A podneedsrolled butwas notSomeonemissestheir PCPSomeonementions our"Silly LittleReports"Someoneblames adatabaseMore than3incidentsin a dayNTH hasa networkissueSomeonebringsCIM treatsRequired point ofcontact is atlunch/gym/walkingthe trackIncidenttriggered byJoe lookingat syntheticsSomeonethankssomeone elsefor somethingCIM said/didA newduckspawnsChristiansays hi tothe stepsfirstThe phrase"missed inspec" isused.Alerting/MonitoringfailedREVERT(outsideofJSD/JSW)Ralph triesto hog theincidentticketsHOTFIX(outsideofJSD/JSW)Someoneforgets toentercomp timeFloorlightsadjustrandomlyCherokeesays "I amsoconfused"A devclaims itworked ontheir localSomeoneis doublemutedSomeoneaccidentallyshows thewrong appwhilescreensharingDeavenis ontimeTeam Sync getscancelled/movedRalphmanagesto dodgean incidentColumnadd/dropbefore codechange isreleasedPTEgoingto LiveIncidentcaused bya CiscobugA Time andAttendancebug causedan incidentMSOutageLarge clientis impactedby anincidentIWantis slowChristiandoesn't makean incidentticket/assignsDeaven anincident ticketNetworkOutage!Someoneuses ashapesmemeSomeoneescalatesin an oldchatThe phrase"perfect storm"is used toexplain why anissue occurred.SomeoneblamesnetworkingOpenCode/Chatty/Kimiproduced code causesan issueDeavenmakes a6-7referenceFeatureFlag!SomeonesuggestsDerek is arobotTechTalk/Webinarcauses an issueSomeonemakes aquestionablejokeSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeonementions thatthe original leaddev for an issueis inactiveAn incidentcauses PD to bepaused/disabledDeavenargues aboutservicesimpacted orcomponentsDeavensays"drinktime"CIM makes astatement thatis ignored butends up beingcorrectChristian/Deavenworks a 'secretincident'Derekcomes byand asks"how are welooking?"SomeonementionsCherokeeknowingChadCherokeesummonsanincidentSomeoneasks"where isChristian"Configchangeswent outbefore codeIncident isrelated toaCHANGEMantleMismatch!A podneedsrolled butwas notSomeonemissestheir PCPSomeonementions our"Silly LittleReports"Someoneblames adatabaseMore than3incidentsin a dayNTH hasa networkissueSomeonebringsCIM treatsRequired point ofcontact is atlunch/gym/walkingthe trackIncidenttriggered byJoe lookingat syntheticsSomeonethankssomeone elsefor somethingCIM said/didA newduckspawnsChristiansays hi tothe stepsfirstThe phrase"missed inspec" isused.Alerting/MonitoringfailedREVERT(outsideofJSD/JSW)Ralph triesto hog theincidentticketsHOTFIX(outsideofJSD/JSW)Someoneforgets toentercomp timeFloorlightsadjustrandomlyCherokeesays "I amsoconfused"A devclaims itworked ontheir localSomeoneis doublemutedSomeoneaccidentallyshows thewrong appwhilescreensharingDeavenis ontimeTeam Sync getscancelled/movedRalphmanagesto dodgean incidentColumnadd/dropbefore codechange isreleasedPTEgoingto LiveIncidentcaused bya CiscobugA Time andAttendancebug causedan incidentMSOutageLarge clientis impactedby anincident

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