Blamingapplicationas theissueBackup totake 3hours togetArgueonpriorityGoing to thewrongresource fora productUpdatingthe wrongsystemDev havingto debugcloud issuesCloud restartssystem beforedev candebug issueprod outagesput in ticketqueueBackup isin thewrongformatMakingchanges toapi-gwinstead ofe5-apiBentonpointingout oddmetrics"If this wasanotherinfrastructure,it would beway easier"SAPCertexpiringHaving toemailoutages toget attentionBackup isset to thewrongownerSending acorruptdatabasebackupCustomdeploymentstaking weeksRyan sayshe knowswhat's goingon (when hedoesnt)GettingYelled@Will T havingto solve acloud issueNo logsfromdynatraceHaving toexplain clouddynatraceresultsLooking atthe wrongdatabaseHal having tojump in todebug cloudissuesBlamingapplicationas theissueBackup totake 3hours togetArgueonpriorityGoing to thewrongresource fora productUpdatingthe wrongsystemDev havingto debugcloud issuesCloud restartssystem beforedev candebug issueprod outagesput in ticketqueueBackup isin thewrongformatMakingchanges toapi-gwinstead ofe5-apiBentonpointingout oddmetrics"If this wasanotherinfrastructure,it would beway easier"SAPCertexpiringHaving toemailoutages toget attentionBackup isset to thewrongownerSending acorruptdatabasebackupCustomdeploymentstaking weeksRyan sayshe knowswhat's goingon (when hedoesnt)GettingYelled@Will T havingto solve acloud issueNo logsfromdynatraceHaving toexplain clouddynatraceresultsLooking atthe wrongdatabaseHal having tojump in todebug cloudissues

Deploy Issues - 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
  1. Blaming application as the issue
  2. Backup to take 3 hours to get
  3. Argue on priority
  4. Going to the wrong resource for a product
  5. Updating the wrong system
  6. Dev having to debug cloud issues
  7. Cloud restarts system before dev can debug issue
  8. prod outages put in ticket queue
  9. Backup is in the wrong format
  10. Making changes to api-gw instead of e5-api
  11. Benton pointing out odd metrics
  12. "If this was another infrastructure, it would be way easier"
  13. SAP Cert expiring
  14. Having to email outages to get attention
  15. Backup is set to the wrong owner
  16. Sending a corrupt database backup
  17. Custom deployments taking weeks
  18. Ryan says he knows what's going on (when he doesnt)
  19. Getting Yelled @
  20. Will T having to solve a cloud issue
  21. No logs from dynatrace
  22. Having to explain cloud dynatrace results
  23. Looking at the wrong database
  24. Hal having to jump in to debug cloud issues