Timepressures(imagined orotherwise)The stagingenvironmentis sharedDeploysareslow"That'son thebacklog"We werenotified ofthis issue bya customerAWSservices aredifferentbetweenenvironmentsA QAwould'vecaughtthis"It's afeature,not a bug"The relevanttest wascommentedoutA thirdpartyservicewas faultyPackageupdate brokethings inprodLow codecoverageblamedTypecheckingwould'vecaught this"It'sdocumentedinConfluence"FeaturebranchdeploysSeeddata islackingUnmergedPR to fixthisThedocumentationwas out ofdateTherewereno logsRequirementschanged[new tech]would fixthisMicroservicecommunicationissuesThe logsdid notshow anerrorThedeveloperresponsiblewent onholidayTimepressures(imagined orotherwise)The stagingenvironmentis sharedDeploysareslow"That'son thebacklog"We werenotified ofthis issue bya customerAWSservices aredifferentbetweenenvironmentsA QAwould'vecaughtthis"It's afeature,not a bug"The relevanttest wascommentedoutA thirdpartyservicewas faultyPackageupdate brokethings inprodLow codecoverageblamedTypecheckingwould'vecaught this"It'sdocumentedinConfluence"FeaturebranchdeploysSeeddata islackingUnmergedPR to fixthisThedocumentationwas out ofdateTherewereno logsRequirementschanged[new tech]would fixthisMicroservicecommunicationissuesThe logsdid notshow anerrorThedeveloperresponsiblewent onholiday

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