Deavenargues aboutservicesimpacted orcomponentsCIM makes astatement thatis ignored butends up beingcorrectRalph triesto hog theincidentticketsA podneedsrolled butwas notFeatureFlag!A Time andAttendancebug causedan incidentChristian/Deavenworks a 'secretincident'Someonementions thatthe original leaddev for an issueis inactiveTeam Sync getscancelled/movedSomeoneescalatesin an oldchatCherokeesummonsanincidentMSOutageDeavenis ontimeSomeonementions our"Silly LittleReports"NetworkOutage!SomeonebringsCIM treatsChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeonemakes aquestionablejokeDeavensays"drinktime"An incidentcauses PD to bepaused/disabledIncidentcaused bya CiscobugMantleMismatch!SomeonesuggestsDerek is arobotHOTFIX(outsideofJSD/JSW)Configchangeswent outbefore codeIncident isrelated toaCHANGEDeavenmakes a6-7referenceChristiansays hi tothe stepsfirstSomeonethankssomeone elsefor somethingCIM said/didCherokeesays "I amsoconfused"Someoneforgets toentercomp timeThe phrase"missed inspec" isused.Required point ofcontact is atlunch/gym/walkingthe trackSomeoneis doublemutedTechTalk/Webinarcauses an issueThe phrase"perfect storm"is used toexplain why anissue occurred.Someoneblames adatabaseDerekcomes byand asks"how are welooking?"Someoneuses ashapesmemeLarge clientis impactedby anincidentSomeonementionsCherokeeknowingChadNTH hasa networkissueSomeoneaccidentallyshows thewrong appwhilescreensharingFloorlightsadjustrandomlyAlerting/MonitoringfailedPTEgoingto LiveA newduckspawnsIWantis slowRalphmanagesto dodgean incidentREVERT(outsideofJSD/JSW)Someone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeMore than3incidentsin a dayOpenCode/Chatty/Kimiproduced code causesan issueA devclaims itworked ontheir localSomeoneblamesnetworkingSomeoneasks"where isChristian"Columnadd/dropbefore codechange isreleasedSomeonemissestheir PCPIncidenttriggered byJoe lookingat syntheticsDeavenargues aboutservicesimpacted orcomponentsCIM makes astatement thatis ignored butends up beingcorrectRalph triesto hog theincidentticketsA podneedsrolled butwas notFeatureFlag!A Time andAttendancebug causedan incidentChristian/Deavenworks a 'secretincident'Someonementions thatthe original leaddev for an issueis inactiveTeam Sync getscancelled/movedSomeoneescalatesin an oldchatCherokeesummonsanincidentMSOutageDeavenis ontimeSomeonementions our"Silly LittleReports"NetworkOutage!SomeonebringsCIM treatsChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeonemakes aquestionablejokeDeavensays"drinktime"An incidentcauses PD to bepaused/disabledIncidentcaused bya CiscobugMantleMismatch!SomeonesuggestsDerek is arobotHOTFIX(outsideofJSD/JSW)Configchangeswent outbefore codeIncident isrelated toaCHANGEDeavenmakes a6-7referenceChristiansays hi tothe stepsfirstSomeonethankssomeone elsefor somethingCIM said/didCherokeesays "I amsoconfused"Someoneforgets toentercomp timeThe phrase"missed inspec" isused.Required point ofcontact is atlunch/gym/walkingthe trackSomeoneis doublemutedTechTalk/Webinarcauses an issueThe phrase"perfect storm"is used toexplain why anissue occurred.Someoneblames adatabaseDerekcomes byand asks"how are welooking?"Someoneuses ashapesmemeLarge clientis impactedby anincidentSomeonementionsCherokeeknowingChadNTH hasa networkissueSomeoneaccidentallyshows thewrong appwhilescreensharingFloorlightsadjustrandomlyAlerting/MonitoringfailedPTEgoingto LiveA newduckspawnsIWantis slowRalphmanagesto dodgean incidentREVERT(outsideofJSD/JSW)Someone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeMore than3incidentsin a dayOpenCode/Chatty/Kimiproduced code causesan issueA devclaims itworked ontheir localSomeoneblamesnetworkingSomeoneasks"where isChristian"Columnadd/dropbefore codechange isreleasedSomeonemissestheir PCPIncidenttriggered byJoe lookingat synthetics

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