Someonementions thatthe original leaddev for an issueis inactiveMantleMismatch!A Time andAttendancebug causedan incidentRalphmanagesto dodgean incidentTechTalk/Webinarcauses an issueDeavenargues aboutservicesimpacted orcomponentsSomeoneuses ashapesmemeSomeonemakes aquestionablejokeAn incidentcauses PD to bepaused/disabledSomeoneblames adatabaseSomeoneblamesnetworkingCIM makes astatement thatis ignored butends up beingcorrectIWantis slowFloorlightsadjustrandomlyIncidentcaused bya CiscobugA newduckspawnsSomeonemissestheir PCPNTH hasa networkissueSomeoneasks"where isChristian"Someonementions our"Silly LittleReports"Required point ofcontact is atlunch/gym/walkingthe trackAlerting/MonitoringfailedConfigchangeswent outbefore codeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketMore than3incidentsin a daySomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeRalph triesto hog theincidentticketsA devclaims itworked ontheir localFeatureFlag!The phrase"missed inspec" isused.A podneedsrolled butwas notSomeoneis doublemutedSomeonebringsCIM treatsIncidenttriggered byJoe lookingat syntheticsNetworkOutage!Columnadd/dropbefore codechange isreleasedSomeonementionsCherokeeknowingChadLarge clientis impactedby anincidentREVERT(outsideofJSD/JSW)Christiansays hi tothe stepsfirstSomeonethankssomeone elsefor somethingCIM said/didSomeoneescalatesin an oldchatPTEgoingto LiveSomeoneaccidentallyshows thewrong appwhilescreensharingMSOutageIncident isrelated toaCHANGEDerekcomes byand asks"how are welooking?"Team Sync getscancelled/movedDeavenis ontimeDeavensays"drinktime"Deavenmakes a6-7referenceHOTFIX(outsideofJSD/JSW)CherokeesummonsanincidentChristian/Deavenworks a 'secretincident'SomeonesuggestsDerek is arobotOpenCode/Chatty/Kimiproduced code causesan issueThe phrase"perfect storm"is used toexplain why anissue occurred.Someoneforgets toentercomp timeCherokeesays "I amsoconfused"Someonementions thatthe original leaddev for an issueis inactiveMantleMismatch!A Time andAttendancebug causedan incidentRalphmanagesto dodgean incidentTechTalk/Webinarcauses an issueDeavenargues aboutservicesimpacted orcomponentsSomeoneuses ashapesmemeSomeonemakes aquestionablejokeAn incidentcauses PD to bepaused/disabledSomeoneblames adatabaseSomeoneblamesnetworkingCIM makes astatement thatis ignored butends up beingcorrectIWantis slowFloorlightsadjustrandomlyIncidentcaused bya CiscobugA newduckspawnsSomeonemissestheir PCPNTH hasa networkissueSomeoneasks"where isChristian"Someonementions our"Silly LittleReports"Required point ofcontact is atlunch/gym/walkingthe trackAlerting/MonitoringfailedConfigchangeswent outbefore codeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketMore than3incidentsin a daySomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeRalph triesto hog theincidentticketsA devclaims itworked ontheir localFeatureFlag!The phrase"missed inspec" isused.A podneedsrolled butwas notSomeoneis doublemutedSomeonebringsCIM treatsIncidenttriggered byJoe lookingat syntheticsNetworkOutage!Columnadd/dropbefore codechange isreleasedSomeonementionsCherokeeknowingChadLarge clientis impactedby anincidentREVERT(outsideofJSD/JSW)Christiansays hi tothe stepsfirstSomeonethankssomeone elsefor somethingCIM said/didSomeoneescalatesin an oldchatPTEgoingto LiveSomeoneaccidentallyshows thewrong appwhilescreensharingMSOutageIncident isrelated toaCHANGEDerekcomes byand asks"how are welooking?"Team Sync getscancelled/movedDeavenis ontimeDeavensays"drinktime"Deavenmakes a6-7referenceHOTFIX(outsideofJSD/JSW)CherokeesummonsanincidentChristian/Deavenworks a 'secretincident'SomeonesuggestsDerek is arobotOpenCode/Chatty/Kimiproduced code causesan issueThe phrase"perfect storm"is used toexplain why anissue occurred.Someoneforgets toentercomp timeCherokeesays "I amsoconfused"

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