Ralph triesto hog theincidentticketsThe phrase"missed inspec" isused.A newduckspawnsLarge clientis impactedby anincidentSomeoneblamesnetworkingSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeA podneedsrolled butwas notColumnadd/dropbefore codechange isreleasedSomeonesuggestsDerek is arobotSomeonementions thatthe original leaddev for an issueis inactiveSomeoneaccidentallyshows thewrong appwhilescreensharingTechTalk/Webinarcauses an issueMantleMismatch!MSOutageSomeoneis doublemutedCherokeesummonsanincidentDeavenis ontimeChristiansays hi tothe stepsfirstSomeoneescalatesin an oldchatRalphmanagesto dodgean incidentSomeonementions our"Silly LittleReports"Deavenargues aboutservicesimpacted orcomponentsThe phrase"perfect storm"is used toexplain why anissue occurred.SomeonementionsCherokeeknowingChadSomeonebringsCIM treatsOpenCode/Chatty/Kimiproduced code causesan issueRequired point ofcontact is atlunch/gym/walkingthe trackIWantis slowSomeonemissestheir PCPChristian/Deavenworks a 'secretincident'Deavenmakes a6-7referenceSomeonemakes aquestionablejokeDerekcomes byand asks"how are welooking?"Incidentcaused bya CiscobugA devclaims itworked ontheir localHOTFIX(outsideofJSD/JSW)Christiandoesn't makean incidentticket/assignsDeaven anincident ticketDeavensays"drinktime"A Time andAttendancebug causedan incidentIncident isrelated toaCHANGENetworkOutage!Team Sync getscancelled/movedIncidenttriggered byJoe lookingat syntheticsSomeoneasks"where isChristian"An incidentcauses PD to bepaused/disabledFloorlightsadjustrandomlyAlerting/MonitoringfailedMore than3incidentsin a daySomeoneforgets toentercomp timeSomeoneblames adatabaseREVERT(outsideofJSD/JSW)Someonethankssomeone elsefor somethingCIM said/didConfigchangeswent outbefore codeFeatureFlag!Cherokeesays "I amsoconfused"Someoneuses ashapesmemePTEgoingto LiveCIM makes astatement thatis ignored butends up beingcorrectNTH hasa networkissueRalph triesto hog theincidentticketsThe phrase"missed inspec" isused.A newduckspawnsLarge clientis impactedby anincidentSomeoneblamesnetworkingSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeA podneedsrolled butwas notColumnadd/dropbefore codechange isreleasedSomeonesuggestsDerek is arobotSomeonementions thatthe original leaddev for an issueis inactiveSomeoneaccidentallyshows thewrong appwhilescreensharingTechTalk/Webinarcauses an issueMantleMismatch!MSOutageSomeoneis doublemutedCherokeesummonsanincidentDeavenis ontimeChristiansays hi tothe stepsfirstSomeoneescalatesin an oldchatRalphmanagesto dodgean incidentSomeonementions our"Silly LittleReports"Deavenargues aboutservicesimpacted orcomponentsThe phrase"perfect storm"is used toexplain why anissue occurred.SomeonementionsCherokeeknowingChadSomeonebringsCIM treatsOpenCode/Chatty/Kimiproduced code causesan issueRequired point ofcontact is atlunch/gym/walkingthe trackIWantis slowSomeonemissestheir PCPChristian/Deavenworks a 'secretincident'Deavenmakes a6-7referenceSomeonemakes aquestionablejokeDerekcomes byand asks"how are welooking?"Incidentcaused bya CiscobugA devclaims itworked ontheir localHOTFIX(outsideofJSD/JSW)Christiandoesn't makean incidentticket/assignsDeaven anincident ticketDeavensays"drinktime"A Time andAttendancebug causedan incidentIncident isrelated toaCHANGENetworkOutage!Team Sync getscancelled/movedIncidenttriggered byJoe lookingat syntheticsSomeoneasks"where isChristian"An incidentcauses PD to bepaused/disabledFloorlightsadjustrandomlyAlerting/MonitoringfailedMore than3incidentsin a daySomeoneforgets toentercomp timeSomeoneblames adatabaseREVERT(outsideofJSD/JSW)Someonethankssomeone elsefor somethingCIM said/didConfigchangeswent outbefore codeFeatureFlag!Cherokeesays "I amsoconfused"Someoneuses ashapesmemePTEgoingto LiveCIM makes astatement thatis ignored butends up beingcorrectNTH hasa networkissue

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