Thedocumentationwas out ofdateA QAwould'vecaughtthisPackageupdate brokethings inprodAWSservices aredifferentbetweenenvironmentsDeploysareslowSeeddata islackingThedeveloperresponsiblewent onholidayA thirdpartyservicewas faultyThe stagingenvironmentis sharedMicroservicecommunicationissuesThe logsdid notshow anerror"It's afeature,not a bug""That'son thebacklog"FeaturebranchdeploysLow codecoverageblamedWe werenotified ofthis issue bya customerThe relevanttest wascommentedoutTherewereno logsTypecheckingwould'vecaught thisUnmergedPR to fixthis[new tech]would fixthisRequirementschangedTimepressures(imagined orotherwise)"It'sdocumentedinConfluence"Thedocumentationwas out ofdateA QAwould'vecaughtthisPackageupdate brokethings inprodAWSservices aredifferentbetweenenvironmentsDeploysareslowSeeddata islackingThedeveloperresponsiblewent onholidayA thirdpartyservicewas faultyThe stagingenvironmentis sharedMicroservicecommunicationissuesThe logsdid notshow anerror"It's afeature,not a bug""That'son thebacklog"FeaturebranchdeploysLow codecoverageblamedWe werenotified ofthis issue bya customerThe relevanttest wascommentedoutTherewereno logsTypecheckingwould'vecaught thisUnmergedPR to fixthis[new tech]would fixthisRequirementschangedTimepressures(imagined orotherwise)"It'sdocumentedinConfluence"

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