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