GettingYelled@prod outagesput in ticketqueueNo logsfromdynatrace"If this wasanotherinfrastructure,it would beway easier"Going to thewrongresource fora productLooking atthe wrongdatabaseHal having tojump in todebug cloudissuesDev havingto debugcloud issuesUpdatingthe wrongsystemCloud restartssystem beforedev candebug issueWill T havingto solve acloud issueSAPCertexpiringRyan sayshe knowswhat's goingon (when hedoesnt)Backup totake 3hours togetHaving toexplain clouddynatraceresultsHaving toemailoutages toget attentionMakingchanges toapi-gwinstead ofe5-apiSending acorruptdatabasebackupBackup isset to thewrongownerCustomdeploymentstaking weeksBentonpointingout oddmetricsBackup isin thewrongformatArgueonpriorityBlamingapplicationas theissueGettingYelled@prod outagesput in ticketqueueNo logsfromdynatrace"If this wasanotherinfrastructure,it would beway easier"Going to thewrongresource fora productLooking atthe wrongdatabaseHal having tojump in todebug cloudissuesDev havingto debugcloud issuesUpdatingthe wrongsystemCloud restartssystem beforedev candebug issueWill T havingto solve acloud issueSAPCertexpiringRyan sayshe knowswhat's goingon (when hedoesnt)Backup totake 3hours togetHaving toexplain clouddynatraceresultsHaving toemailoutages toget attentionMakingchanges toapi-gwinstead ofe5-apiSending acorruptdatabasebackupBackup isset to thewrongownerCustomdeploymentstaking weeksBentonpointingout oddmetricsBackup isin thewrongformatArgueonpriorityBlamingapplicationas theissue

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