Therewereno logsThe relevanttest wascommentedoutThedeveloperresponsiblewent onholidayThe stagingenvironmentis sharedWe werenotified ofthis issue bya customerA QAwould'vecaughtthisPackageupdate brokethings inprodAWSservices aredifferentbetweenenvironments"It'sdocumentedinConfluence"Thedocumentationwas out ofdateTimepressures(imagined orotherwise)Typecheckingwould'vecaught thisUnmergedPR to fixthisThe logsdid notshow anerrorLow codecoverageblamedRequirementschangedFeaturebranchdeploysA thirdpartyservicewas faulty"That'son thebacklog"[new tech]would fixthisSeeddata islackingDeploysareslowMicroservicecommunicationissues"It's afeature,not a bug"Therewereno logsThe relevanttest wascommentedoutThedeveloperresponsiblewent onholidayThe stagingenvironmentis sharedWe werenotified ofthis issue bya customerA QAwould'vecaughtthisPackageupdate brokethings inprodAWSservices aredifferentbetweenenvironments"It'sdocumentedinConfluence"Thedocumentationwas out ofdateTimepressures(imagined orotherwise)Typecheckingwould'vecaught thisUnmergedPR to fixthisThe logsdid notshow anerrorLow codecoverageblamedRequirementschangedFeaturebranchdeploysA thirdpartyservicewas faulty"That'son thebacklog"[new tech]would fixthisSeeddata islackingDeploysareslowMicroservicecommunicationissues"It's afeature,not a bug"

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