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