Packageupdate brokethings inprodMicroservicecommunicationissues"It's afeature,not a bug"Therewereno logsThe stagingenvironmentis sharedThedeveloperresponsiblewent onholidayDeploysareslow"That'son thebacklog""It'sdocumentedinConfluence"A thirdpartyservicewas faultyThedocumentationwas out ofdateFeaturebranchdeploysThe relevanttest wascommentedoutA QAwould'vecaughtthisRequirementschangedUnmergedPR to fixthisWe werenotified ofthis issue bya customerTimepressures(imagined orotherwise)The logsdid notshow anerrorLow codecoverageblamedTypecheckingwould'vecaught this[new tech]would fixthisSeeddata islackingAWSservices aredifferentbetweenenvironmentsPackageupdate brokethings inprodMicroservicecommunicationissues"It's afeature,not a bug"Therewereno logsThe stagingenvironmentis sharedThedeveloperresponsiblewent onholidayDeploysareslow"That'son thebacklog""It'sdocumentedinConfluence"A thirdpartyservicewas faultyThedocumentationwas out ofdateFeaturebranchdeploysThe relevanttest wascommentedoutA QAwould'vecaughtthisRequirementschangedUnmergedPR to fixthisWe werenotified ofthis issue bya customerTimepressures(imagined orotherwise)The logsdid notshow anerrorLow codecoverageblamedTypecheckingwould'vecaught this[new tech]would fixthisSeeddata islackingAWSservices aredifferentbetweenenvironments

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