Dev havingto debugcloud issuesGettingYelled@Having toemailoutages toget attentionHal having tojump in todebug cloudissuesBlamingapplicationas theissueHaving toexplain clouddynatraceresultsMakingchanges toapi-gwinstead ofe5-apiBackup isin thewrongformatSending acorruptdatabasebackupSAPCertexpiringLooking atthe wrongdatabaseWill T havingto solve acloud issueUpdatingthe wrongsystemArgueonpriorityNo logsfromdynatrace"If this wasanotherinfrastructure,it would beway easier"prod outagesput in ticketqueueGoing to thewrongresource fora productCloud restartssystem beforedev candebug issueCustomdeploymentstaking weeksBackup isset to thewrongownerBentonpointingout oddmetricsBackup totake 3hours togetRyan sayshe knowswhat's goingon (when hedoesnt)Dev havingto debugcloud issuesGettingYelled@Having toemailoutages toget attentionHal having tojump in todebug cloudissuesBlamingapplicationas theissueHaving toexplain clouddynatraceresultsMakingchanges toapi-gwinstead ofe5-apiBackup isin thewrongformatSending acorruptdatabasebackupSAPCertexpiringLooking atthe wrongdatabaseWill T havingto solve acloud issueUpdatingthe wrongsystemArgueonpriorityNo logsfromdynatrace"If this wasanotherinfrastructure,it would beway easier"prod outagesput in ticketqueueGoing to thewrongresource fora productCloud restartssystem beforedev candebug issueCustomdeploymentstaking weeksBackup isset to thewrongownerBentonpointingout oddmetricsBackup totake 3hours togetRyan sayshe knowswhat's goingon (when hedoesnt)

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