A newduckspawnsDeavensays"drinktime"Incidenttriggered byJoe lookingat syntheticsLarge clientis impactedby anincidentSomeonementions thatthe original leaddev for an issueis inactiveFloorlightsadjustrandomlyCherokeesummonsanincidentSomeoneaccidentallyshows thewrong appwhilescreensharingSomeoneblames adatabaseSomeonementionsCherokeeknowingChadSomeonemissestheir PCPRalph triesto hog theincidentticketsThe phrase"perfect storm"is used toexplain why anissue occurred.FeatureFlag!A Time andAttendancebug causedan incidentTechTalk/Webinarcauses an issueIWantis slowDeavenis ontimeCIM makes astatement thatis ignored butends up beingcorrectChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeoneforgets toentercomp timeMantleMismatch!PTEgoingto LiveCherokeesays "I amsoconfused"Someonementions our"Silly LittleReports"Team Sync getscancelled/movedNetworkOutage!More than3incidentsin a dayColumnadd/dropbefore codechange isreleasedSomeonemakes aquestionablejokeThe phrase"missed inspec" isused.Someone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeNTH hasa networkissueConfigchangeswent outbefore codeRequired point ofcontact is atlunch/gym/walkingthe trackSomeoneis doublemutedSomeoneasks"where isChristian"Derekcomes byand asks"how are welooking?"Incidentcaused bya CiscobugRalphmanagesto dodgean incidentSomeoneblamesnetworkingMSOutageOpenCode/Chatty/Kimiproduced code causesan issueIncident isrelated toaCHANGEA devclaims itworked ontheir localAlerting/MonitoringfailedSomeoneuses ashapesmemeREVERT(outsideofJSD/JSW)Deavenargues aboutservicesimpacted orcomponentsChristian/Deavenworks a 'secretincident'SomeonesuggestsDerek is arobotA podneedsrolled butwas notSomeoneescalatesin an oldchatSomeonebringsCIM treatsHOTFIX(outsideofJSD/JSW)Someonethankssomeone elsefor somethingCIM said/didDeavenmakes a6-7referenceChristiansays hi tothe stepsfirstAn incidentcauses PD to bepaused/disabledA newduckspawnsDeavensays"drinktime"Incidenttriggered byJoe lookingat syntheticsLarge clientis impactedby anincidentSomeonementions thatthe original leaddev for an issueis inactiveFloorlightsadjustrandomlyCherokeesummonsanincidentSomeoneaccidentallyshows thewrong appwhilescreensharingSomeoneblames adatabaseSomeonementionsCherokeeknowingChadSomeonemissestheir PCPRalph triesto hog theincidentticketsThe phrase"perfect storm"is used toexplain why anissue occurred.FeatureFlag!A Time andAttendancebug causedan incidentTechTalk/Webinarcauses an issueIWantis slowDeavenis ontimeCIM makes astatement thatis ignored butends up beingcorrectChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeoneforgets toentercomp timeMantleMismatch!PTEgoingto LiveCherokeesays "I amsoconfused"Someonementions our"Silly LittleReports"Team Sync getscancelled/movedNetworkOutage!More than3incidentsin a dayColumnadd/dropbefore codechange isreleasedSomeonemakes aquestionablejokeThe phrase"missed inspec" isused.Someone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeNTH hasa networkissueConfigchangeswent outbefore codeRequired point ofcontact is atlunch/gym/walkingthe trackSomeoneis doublemutedSomeoneasks"where isChristian"Derekcomes byand asks"how are welooking?"Incidentcaused bya CiscobugRalphmanagesto dodgean incidentSomeoneblamesnetworkingMSOutageOpenCode/Chatty/Kimiproduced code causesan issueIncident isrelated toaCHANGEA devclaims itworked ontheir localAlerting/MonitoringfailedSomeoneuses ashapesmemeREVERT(outsideofJSD/JSW)Deavenargues aboutservicesimpacted orcomponentsChristian/Deavenworks a 'secretincident'SomeonesuggestsDerek is arobotA podneedsrolled butwas notSomeoneescalatesin an oldchatSomeonebringsCIM treatsHOTFIX(outsideofJSD/JSW)Someonethankssomeone elsefor somethingCIM said/didDeavenmakes a6-7referenceChristiansays hi tothe stepsfirstAn incidentcauses PD to bepaused/disabled

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