Columnadd/dropbefore codechange isreleasedChristiansays hi tothe stepsfirstCherokeesummonsanincidentTechTalk/Webinarcauses an issueSomeonementions thatthe original leaddev for an issueis inactiveA devclaims itworked ontheir localDeavensays"drinktime"MSOutageRalphmanagesto dodgean incidentREVERT(outsideofJSD/JSW)Incidentcaused bya CiscobugOpenCode/Chatty/Kimiproduced code causesan issueIncident isrelated toaCHANGEFloorlightsadjustrandomlyDeavenis ontimeHOTFIX(outsideofJSD/JSW)IWantis slowMore than3incidentsin a dayCIM makes astatement thatis ignored butends up beingcorrectCherokeesays "I amsoconfused"Alerting/MonitoringfailedThe phrase"missed inspec" isused.SomeonementionsCherokeeknowingChadSomeoneuses ashapesmemeDerekcomes byand asks"how are welooking?"Someoneescalatesin an oldchatA podneedsrolled butwas notTeam Sync getscancelled/movedSomeonebringsCIM treatsSomeoneblames adatabaseA Time andAttendancebug causedan incidentSomeonesuggestsDerek is arobotDeavenmakes a6-7referencePTEgoingto LiveSomeonethankssomeone elsefor somethingCIM said/didDeavenargues aboutservicesimpacted orcomponentsSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeonemakes aquestionablejokeSomeoneis doublemutedNTH hasa networkissueSomeoneaccidentallyshows thewrong appwhilescreensharingNetworkOutage!Someoneforgets toentercomp timeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketAn incidentcauses PD to bepaused/disabledThe phrase"perfect storm"is used toexplain why anissue occurred.A newduckspawnsRequired point ofcontact is atlunch/gym/walkingthe trackRalph triesto hog theincidentticketsMantleMismatch!SomeoneblamesnetworkingIncidenttriggered byJoe lookingat syntheticsLarge clientis impactedby anincidentConfigchangeswent outbefore codeSomeoneasks"where isChristian"Someonemissestheir PCPFeatureFlag!Someonementions our"Silly LittleReports"Christian/Deavenworks a 'secretincident'Columnadd/dropbefore codechange isreleasedChristiansays hi tothe stepsfirstCherokeesummonsanincidentTechTalk/Webinarcauses an issueSomeonementions thatthe original leaddev for an issueis inactiveA devclaims itworked ontheir localDeavensays"drinktime"MSOutageRalphmanagesto dodgean incidentREVERT(outsideofJSD/JSW)Incidentcaused bya CiscobugOpenCode/Chatty/Kimiproduced code causesan issueIncident isrelated toaCHANGEFloorlightsadjustrandomlyDeavenis ontimeHOTFIX(outsideofJSD/JSW)IWantis slowMore than3incidentsin a dayCIM makes astatement thatis ignored butends up beingcorrectCherokeesays "I amsoconfused"Alerting/MonitoringfailedThe phrase"missed inspec" isused.SomeonementionsCherokeeknowingChadSomeoneuses ashapesmemeDerekcomes byand asks"how are welooking?"Someoneescalatesin an oldchatA podneedsrolled butwas notTeam Sync getscancelled/movedSomeonebringsCIM treatsSomeoneblames adatabaseA Time andAttendancebug causedan incidentSomeonesuggestsDerek is arobotDeavenmakes a6-7referencePTEgoingto LiveSomeonethankssomeone elsefor somethingCIM said/didDeavenargues aboutservicesimpacted orcomponentsSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeSomeonemakes aquestionablejokeSomeoneis doublemutedNTH hasa networkissueSomeoneaccidentallyshows thewrong appwhilescreensharingNetworkOutage!Someoneforgets toentercomp timeChristiandoesn't makean incidentticket/assignsDeaven anincident ticketAn incidentcauses PD to bepaused/disabledThe phrase"perfect storm"is used toexplain why anissue occurred.A newduckspawnsRequired point ofcontact is atlunch/gym/walkingthe trackRalph triesto hog theincidentticketsMantleMismatch!SomeoneblamesnetworkingIncidenttriggered byJoe lookingat syntheticsLarge clientis impactedby anincidentConfigchangeswent outbefore codeSomeoneasks"where isChristian"Someonemissestheir PCPFeatureFlag!Someonementions our"Silly LittleReports"Christian/Deavenworks a 'secretincident'

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