Backup totake 3hours togetWill T havingto solve acloud issueBackup isset to thewrongownerprod outagesput in ticketqueueUpdatingthe wrongsystemSAPCertexpiringHaving toemailoutages toget attention"If this wasanotherinfrastructure,it would beway easier"Going to thewrongresource fora productHaving toexplain clouddynatraceresultsSending acorruptdatabasebackupDev havingto debugcloud issuesHal having tojump in todebug cloudissuesRyan sayshe knowswhat's goingon (when hedoesnt)ArgueonpriorityMakingchanges toapi-gwinstead ofe5-apiGettingYelled@Looking atthe wrongdatabaseCloud restartssystem beforedev candebug issueNo logsfromdynatraceBackup isin thewrongformatBentonpointingout oddmetricsCustomdeploymentstaking weeksBlamingapplicationas theissueBackup totake 3hours togetWill T havingto solve acloud issueBackup isset to thewrongownerprod outagesput in ticketqueueUpdatingthe wrongsystemSAPCertexpiringHaving toemailoutages toget attention"If this wasanotherinfrastructure,it would beway easier"Going to thewrongresource fora productHaving toexplain clouddynatraceresultsSending acorruptdatabasebackupDev havingto debugcloud issuesHal having tojump in todebug cloudissuesRyan sayshe knowswhat's goingon (when hedoesnt)ArgueonpriorityMakingchanges toapi-gwinstead ofe5-apiGettingYelled@Looking atthe wrongdatabaseCloud restartssystem beforedev candebug issueNo logsfromdynatraceBackup isin thewrongformatBentonpointingout oddmetricsCustomdeploymentstaking weeksBlamingapplicationas 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. Backup to take 3 hours to get
  2. Will T having to solve a cloud issue
  3. Backup is set to the wrong owner
  4. prod outages put in ticket queue
  5. Updating the wrong system
  6. SAP Cert expiring
  7. Having to email outages to get attention
  8. "If this was another infrastructure, it would be way easier"
  9. Going to the wrong resource for a product
  10. Having to explain cloud dynatrace results
  11. Sending a corrupt database backup
  12. Dev having to debug cloud issues
  13. Hal having to jump in to debug cloud issues
  14. Ryan says he knows what's going on (when he doesnt)
  15. Argue on priority
  16. Making changes to api-gw instead of e5-api
  17. Getting Yelled @
  18. Looking at the wrong database
  19. Cloud restarts system before dev can debug issue
  20. No logs from dynatrace
  21. Backup is in the wrong format
  22. Benton pointing out odd metrics
  23. Custom deployments taking weeks
  24. Blaming application as the issue