Ralph triesto hog theincidentticketsSomeoneuses ashapesmemeRalphmanagesto dodgean incidentSomeonementions thatthe original leaddev for an issueis inactiveSomeoneaccidentallyshows thewrong appwhilescreensharingDeavensays"drinktime"Deavenmakes a6-7referenceSomeoneforgets toentercomp timeMSOutageAlerting/MonitoringfailedColumnadd/dropbefore codechange isreleasedSomeonementionsCherokeeknowingChadA Time andAttendancebug causedan incidentSomeonebringsCIM treatsIncidentcaused bya CiscobugREVERT(outsideofJSD/JSW)IWantis slowFloorlightsadjustrandomlySomeoneblames adatabaseA podneedsrolled butwas notSomeoneblamesnetworkingThe phrase"missed inspec" isused.A newduckspawnsTeam Sync getscancelled/movedIncidenttriggered byJoe lookingat syntheticsTechTalk/Webinarcauses an issueDeavenargues aboutservicesimpacted orcomponentsSomeoneis doublemutedCherokeesummonsanincidentChristian/Deavenworks a 'secretincident'Someonemissestheir PCPSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeoneasks"where isChristian"A devclaims itworked ontheir localPTEgoingto LiveNTH hasa networkissueHOTFIX(outsideofJSD/JSW)Incident isrelated toaCHANGEChristiansays hi tothe stepsfirstConfigchangeswent outbefore codeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketMore than3incidentsin a dayDerekcomes byand asks"how are welooking?"MantleMismatch!FeatureFlag!Cherokeesays "I amsoconfused"Someonemakes aquestionablejokeLarge clientis impactedby anincidentSomeonesuggestsDerek is arobotNetworkOutage!Someonethankssomeone elsefor somethingCIM said/didOpenCode/Chatty/Kimiproduced code causesan issueRequired point ofcontact is atlunch/gym/walkingthe trackCIM makes astatement thatis ignored butends up beingcorrectAn incidentcauses PD to bepaused/disabledThe phrase"perfect storm"is used toexplain why anissue occurred.Someonementions our"Silly LittleReports"Deavenis ontimeSomeoneescalatesin an oldchatRalph triesto hog theincidentticketsSomeoneuses ashapesmemeRalphmanagesto dodgean incidentSomeonementions thatthe original leaddev for an issueis inactiveSomeoneaccidentallyshows thewrong appwhilescreensharingDeavensays"drinktime"Deavenmakes a6-7referenceSomeoneforgets toentercomp timeMSOutageAlerting/MonitoringfailedColumnadd/dropbefore codechange isreleasedSomeonementionsCherokeeknowingChadA Time andAttendancebug causedan incidentSomeonebringsCIM treatsIncidentcaused bya CiscobugREVERT(outsideofJSD/JSW)IWantis slowFloorlightsadjustrandomlySomeoneblames adatabaseA podneedsrolled butwas notSomeoneblamesnetworkingThe phrase"missed inspec" isused.A newduckspawnsTeam Sync getscancelled/movedIncidenttriggered byJoe lookingat syntheticsTechTalk/Webinarcauses an issueDeavenargues aboutservicesimpacted orcomponentsSomeoneis doublemutedCherokeesummonsanincidentChristian/Deavenworks a 'secretincident'Someonemissestheir PCPSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeoneasks"where isChristian"A devclaims itworked ontheir localPTEgoingto LiveNTH hasa networkissueHOTFIX(outsideofJSD/JSW)Incident isrelated toaCHANGEChristiansays hi tothe stepsfirstConfigchangeswent outbefore codeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketMore than3incidentsin a dayDerekcomes byand asks"how are welooking?"MantleMismatch!FeatureFlag!Cherokeesays "I amsoconfused"Someonemakes aquestionablejokeLarge clientis impactedby anincidentSomeonesuggestsDerek is arobotNetworkOutage!Someonethankssomeone elsefor somethingCIM said/didOpenCode/Chatty/Kimiproduced code causesan issueRequired point ofcontact is atlunch/gym/walkingthe trackCIM makes astatement thatis ignored butends up beingcorrectAn incidentcauses PD to bepaused/disabledThe phrase"perfect storm"is used toexplain why anissue occurred.Someonementions our"Silly LittleReports"Deavenis ontimeSomeoneescalatesin an oldchat

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