Seeddata islackingA thirdpartyservicewas faulty"It'sdocumentedinConfluence"A QAwould'vecaughtthisRequirementschangedDeploysareslow"It's afeature,not a bug"The stagingenvironmentis sharedUnmergedPR to fixthisWe werenotified ofthis issue bya customerThe relevanttest wascommentedout[new tech]would fixthisThe logsdid notshow anerrorTherewereno logsTypecheckingwould'vecaught thisAWSservices aredifferentbetweenenvironmentsMicroservicecommunicationissuesThedeveloperresponsiblewent onholiday"That'son thebacklog"Thedocumentationwas out ofdateFeaturebranchdeploysPackageupdate brokethings inprodTimepressures(imagined orotherwise)Low codecoverageblamedSeeddata islackingA thirdpartyservicewas faulty"It'sdocumentedinConfluence"A QAwould'vecaughtthisRequirementschangedDeploysareslow"It's afeature,not a bug"The stagingenvironmentis sharedUnmergedPR to fixthisWe werenotified ofthis issue bya customerThe relevanttest wascommentedout[new tech]would fixthisThe logsdid notshow anerrorTherewereno logsTypecheckingwould'vecaught thisAWSservices aredifferentbetweenenvironmentsMicroservicecommunicationissuesThedeveloperresponsiblewent onholiday"That'son thebacklog"Thedocumentationwas out ofdateFeaturebranchdeploysPackageupdate brokethings inprodTimepressures(imagined orotherwise)Low codecoverageblamed

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