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