Backup isset to thewrongownerMakingchanges toapi-gwinstead ofe5-apiBackup isin thewrongformatCustomdeploymentstaking weeksBentonpointingout oddmetricsGoing to thewrongresource fora productUpdatingthe wrongsystemGettingYelled@Dev havingto debugcloud issuesCloud restartssystem beforedev candebug issueSAPCertexpiringLooking atthe wrongdatabaseBlamingapplicationas theissueSending acorruptdatabasebackupprod outagesput in ticketqueue"If this wasanotherinfrastructure,it would beway easier"Backup totake 3hours togetArgueonpriorityHaving toemailoutages toget attentionHaving toexplain clouddynatraceresultsHal having tojump in todebug cloudissuesRyan sayshe knowswhat's goingon (when hedoesnt)Will T havingto solve acloud issueNo logsfromdynatraceBackup isset to thewrongownerMakingchanges toapi-gwinstead ofe5-apiBackup isin thewrongformatCustomdeploymentstaking weeksBentonpointingout oddmetricsGoing to thewrongresource fora productUpdatingthe wrongsystemGettingYelled@Dev havingto debugcloud issuesCloud restartssystem beforedev candebug issueSAPCertexpiringLooking atthe wrongdatabaseBlamingapplicationas theissueSending acorruptdatabasebackupprod outagesput in ticketqueue"If this wasanotherinfrastructure,it would beway easier"Backup totake 3hours togetArgueonpriorityHaving toemailoutages toget attentionHaving toexplain clouddynatraceresultsHal having tojump in todebug cloudissuesRyan sayshe knowswhat's goingon (when hedoesnt)Will T havingto solve acloud issueNo logsfromdynatrace

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