Featurebranchdeploys"That'son thebacklog"[new tech]would fixthisUnmergedPR to fixthisDeploysareslowThe relevanttest wascommentedout"It's afeature,not a bug"RequirementschangedTherewereno logsThe stagingenvironmentis sharedMicroservicecommunicationissues"It'sdocumentedinConfluence"A thirdpartyservicewas faultyPackageupdate brokethings inprodWe werenotified ofthis issue bya customerSeeddata islackingTimepressures(imagined orotherwise)Thedocumentationwas out ofdateTypecheckingwould'vecaught thisThe logsdid notshow anerrorA QAwould'vecaughtthisThedeveloperresponsiblewent onholidayLow codecoverageblamedAWSservices aredifferentbetweenenvironmentsFeaturebranchdeploys"That'son thebacklog"[new tech]would fixthisUnmergedPR to fixthisDeploysareslowThe relevanttest wascommentedout"It's afeature,not a bug"RequirementschangedTherewereno logsThe stagingenvironmentis sharedMicroservicecommunicationissues"It'sdocumentedinConfluence"A thirdpartyservicewas faultyPackageupdate brokethings inprodWe werenotified ofthis issue bya customerSeeddata islackingTimepressures(imagined orotherwise)Thedocumentationwas out ofdateTypecheckingwould'vecaught thisThe logsdid notshow anerrorA QAwould'vecaughtthisThedeveloperresponsiblewent onholidayLow codecoverageblamedAWSservices aredifferentbetweenenvironments

Engineering Retro - 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. Feature branch deploys
  2. "That's on the backlog"
  3. [new tech] would fix this
  4. Unmerged PR to fix this
  5. Deploys are slow
  6. The relevant test was commented out
  7. "It's a feature, not a bug"
  8. Requirements changed
  9. There were no logs
  10. The staging environment is shared
  11. Microservice communication issues
  12. "It's documented in Confluence"
  13. A third party service was faulty
  14. Package update broke things in prod
  15. We were notified of this issue by a customer
  16. Seed data is lacking
  17. Time pressures (imagined or otherwise)
  18. The documentation was out of date
  19. Type checking would've caught this
  20. The logs did not show an error
  21. A QA would've caught this
  22. The developer responsible went on holiday
  23. Low code coverage blamed
  24. AWS services are different between environments