A thirdpartyservicewas faultyDeploysareslowFeaturebranchdeploysUnmergedPR to fixthisTypecheckingwould'vecaught thisTherewereno logsMicroservicecommunicationissues"It's afeature,not a bug"Thedeveloperresponsiblewent onholiday"It'sdocumentedinConfluence"Low codecoverageblamed[new tech]would fixthisThe stagingenvironmentis sharedRequirementschanged"That'son thebacklog"The logsdid notshow anerrorTimepressures(imagined orotherwise)Thedocumentationwas out ofdateWe werenotified ofthis issue bya customerAWSservices aredifferentbetweenenvironmentsPackageupdate brokethings inprodThe relevanttest wascommentedoutSeeddata islackingA QAwould'vecaughtthisA thirdpartyservicewas faultyDeploysareslowFeaturebranchdeploysUnmergedPR to fixthisTypecheckingwould'vecaught thisTherewereno logsMicroservicecommunicationissues"It's afeature,not a bug"Thedeveloperresponsiblewent onholiday"It'sdocumentedinConfluence"Low codecoverageblamed[new tech]would fixthisThe stagingenvironmentis sharedRequirementschanged"That'son thebacklog"The logsdid notshow anerrorTimepressures(imagined orotherwise)Thedocumentationwas out ofdateWe werenotified ofthis issue bya customerAWSservices aredifferentbetweenenvironmentsPackageupdate brokethings inprodThe relevanttest wascommentedoutSeeddata islackingA QAwould'vecaughtthis

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