FeatureFlag!TechTalk/Webinarcauses an issueA newduckspawnsAlerting/MonitoringfailedOpenCode/Chatty/Kimiproduced code causesan issueA devclaims itworked ontheir localSomeoneblames adatabaseSomeoneblamesnetworkingNetworkOutage!NTH hasa networkissueIncidentcaused bya CiscobugDerekcomes byand asks"how are welooking?"The phrase"missed inspec" isused.Columnadd/dropbefore codechange isreleasedSomeonesuggestsDerek is arobotSomeoneescalatesin an oldchatRalph triesto hog theincidentticketsSomeonemissestheir PCPDeavensays"drinktime"More than3incidentsin a dayIncident isrelated toaCHANGELarge clientis impactedby anincidentSomeonementions our"Silly LittleReports"SomeonebringsCIM treatsSomeoneuses ashapesmemeSomeoneforgets toentercomp timePTEgoingto LiveSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeIncidenttriggered byJoe lookingat syntheticsHOTFIX(outsideofJSD/JSW)Team Sync getscancelled/movedDeavenmakes a6-7referenceSomeonementions thatthe original leaddev for an issueis inactiveCherokeesummonsanincidentCIM makes astatement thatis ignored butends up beingcorrectChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeonethankssomeone elsefor somethingCIM said/didRalphmanagesto dodgean incidentSomeoneis doublemutedThe phrase"perfect storm"is used toexplain why anissue occurred.FloorlightsadjustrandomlyMantleMismatch!IWantis slowA podneedsrolled butwas notSomeonementionsCherokeeknowingChadCherokeesays "I amsoconfused"Someoneaccidentallyshows thewrong appwhilescreensharingRequired point ofcontact is atlunch/gym/walkingthe trackDeavenargues aboutservicesimpacted orcomponentsAn incidentcauses PD to bepaused/disabledChristian/Deavenworks a 'secretincident'REVERT(outsideofJSD/JSW)Configchangeswent outbefore codeA Time andAttendancebug causedan incidentSomeonemakes aquestionablejokeDeavenis ontimeChristiansays hi tothe stepsfirstMSOutageSomeoneasks"where isChristian"FeatureFlag!TechTalk/Webinarcauses an issueA newduckspawnsAlerting/MonitoringfailedOpenCode/Chatty/Kimiproduced code causesan issueA devclaims itworked ontheir localSomeoneblames adatabaseSomeoneblamesnetworkingNetworkOutage!NTH hasa networkissueIncidentcaused bya CiscobugDerekcomes byand asks"how are welooking?"The phrase"missed inspec" isused.Columnadd/dropbefore codechange isreleasedSomeonesuggestsDerek is arobotSomeoneescalatesin an oldchatRalph triesto hog theincidentticketsSomeonemissestheir PCPDeavensays"drinktime"More than3incidentsin a dayIncident isrelated toaCHANGELarge clientis impactedby anincidentSomeonementions our"Silly LittleReports"SomeonebringsCIM treatsSomeoneuses ashapesmemeSomeoneforgets toentercomp timePTEgoingto LiveSomeone uses aGIF/meme/reactionto say 'jinx' whenthey messagesomething at thesame timeIncidenttriggered byJoe lookingat syntheticsHOTFIX(outsideofJSD/JSW)Team Sync getscancelled/movedDeavenmakes a6-7referenceSomeonementions thatthe original leaddev for an issueis inactiveCherokeesummonsanincidentCIM makes astatement thatis ignored butends up beingcorrectChristiandoesn't makean incidentticket/assignsDeaven anincident ticketSomeonethankssomeone elsefor somethingCIM said/didRalphmanagesto dodgean incidentSomeoneis doublemutedThe phrase"perfect storm"is used toexplain why anissue occurred.FloorlightsadjustrandomlyMantleMismatch!IWantis slowA podneedsrolled butwas notSomeonementionsCherokeeknowingChadCherokeesays "I amsoconfused"Someoneaccidentallyshows thewrong appwhilescreensharingRequired point ofcontact is atlunch/gym/walkingthe trackDeavenargues aboutservicesimpacted orcomponentsAn incidentcauses PD to bepaused/disabledChristian/Deavenworks a 'secretincident'REVERT(outsideofJSD/JSW)Configchangeswent outbefore codeA Time andAttendancebug causedan incidentSomeonemakes aquestionablejokeDeavenis ontimeChristiansays hi tothe stepsfirstMSOutageSomeoneasks"where isChristian"

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