Microservicecommunicationissues"It's afeature,not a bug"A QAwould'vecaughtthis[new tech]would fixthisLow codecoverageblamedA thirdpartyservicewas faultyAWSservices aredifferentbetweenenvironmentsSeeddata islackingTherewereno logsUnmergedPR to fixthisThedeveloperresponsiblewent onholidayTimepressures(imagined orotherwise)Typecheckingwould'vecaught thisRequirementschangedThe relevanttest wascommentedoutDeploysareslowFeaturebranchdeploys"That'son thebacklog"The logsdid notshow anerrorWe werenotified ofthis issue bya customer"It'sdocumentedinConfluence"The stagingenvironmentis sharedPackageupdate brokethings inprodThedocumentationwas out ofdateMicroservicecommunicationissues"It's afeature,not a bug"A QAwould'vecaughtthis[new tech]would fixthisLow codecoverageblamedA thirdpartyservicewas faultyAWSservices aredifferentbetweenenvironmentsSeeddata islackingTherewereno logsUnmergedPR to fixthisThedeveloperresponsiblewent onholidayTimepressures(imagined orotherwise)Typecheckingwould'vecaught thisRequirementschangedThe relevanttest wascommentedoutDeploysareslowFeaturebranchdeploys"That'son thebacklog"The logsdid notshow anerrorWe werenotified ofthis issue bya customer"It'sdocumentedinConfluence"The stagingenvironmentis sharedPackageupdate brokethings inprodThedocumentationwas out ofdate

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