Having toexplain clouddynatraceresultsMakingchanges toapi-gwinstead ofe5-apiRyan sayshe knowswhat's goingon (when hedoesnt)Cloud restartssystem beforedev candebug issueHaving toemailoutages toget attentionGettingYelled@Bentonpointingout oddmetricsBlamingapplicationas theissueBackup isset to thewrongownerGoing to thewrongresource fora product"If this wasanotherinfrastructure,it would beway easier"Looking atthe wrongdatabaseSAPCertexpiringWill T havingto solve acloud issueDev havingto debugcloud issuesCustomdeploymentstaking weeksHal having tojump in todebug cloudissuesNo logsfromdynatraceArgueonpriorityUpdatingthe wrongsystemBackup isin thewrongformatBackup totake 3hours togetSending acorruptdatabasebackupprod outagesput in ticketqueueHaving toexplain clouddynatraceresultsMakingchanges toapi-gwinstead ofe5-apiRyan sayshe knowswhat's goingon (when hedoesnt)Cloud restartssystem beforedev candebug issueHaving toemailoutages toget attentionGettingYelled@Bentonpointingout oddmetricsBlamingapplicationas theissueBackup isset to thewrongownerGoing to thewrongresource fora product"If this wasanotherinfrastructure,it would beway easier"Looking atthe wrongdatabaseSAPCertexpiringWill T havingto solve acloud issueDev havingto debugcloud issuesCustomdeploymentstaking weeksHal having tojump in todebug cloudissuesNo logsfromdynatraceArgueonpriorityUpdatingthe wrongsystemBackup isin thewrongformatBackup totake 3hours togetSending acorruptdatabasebackupprod outagesput in ticketqueue

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