MicroservicecommunicationissuesThedocumentationwas out ofdateTypecheckingwould'vecaught this"It'sdocumentedinConfluence"RequirementschangedThedeveloperresponsiblewent onholidayThe relevanttest wascommentedoutFeaturebranchdeploysTherewereno logsSeeddata islacking"It's afeature,not a bug"DeploysareslowA thirdpartyservicewas faultyPackageupdate brokethings inprodLow codecoverageblamed[new tech]would fixthisTimepressures(imagined orotherwise)The logsdid notshow anerrorAWSservices aredifferentbetweenenvironmentsWe werenotified ofthis issue bya customerThe stagingenvironmentis sharedUnmergedPR to fixthisA QAwould'vecaughtthis"That'son thebacklog"MicroservicecommunicationissuesThedocumentationwas out ofdateTypecheckingwould'vecaught this"It'sdocumentedinConfluence"RequirementschangedThedeveloperresponsiblewent onholidayThe relevanttest wascommentedoutFeaturebranchdeploysTherewereno logsSeeddata islacking"It's afeature,not a bug"DeploysareslowA thirdpartyservicewas faultyPackageupdate brokethings inprodLow codecoverageblamed[new tech]would fixthisTimepressures(imagined orotherwise)The logsdid notshow anerrorAWSservices aredifferentbetweenenvironmentsWe werenotified ofthis issue bya customerThe stagingenvironmentis sharedUnmergedPR to fixthisA QAwould'vecaughtthis"That'son thebacklog"

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