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