DeploysareslowUnmergedPR to fixthisLow codecoverageblamedA thirdpartyservicewas faultyTherewereno logs"It'sdocumentedinConfluence"Seeddata islacking"That'son thebacklog"Packageupdate brokethings inprodThe relevanttest wascommentedoutTimepressures(imagined orotherwise)RequirementschangedThedeveloperresponsiblewent onholiday"It's afeature,not a bug"Thedocumentationwas out ofdateMicroservicecommunicationissuesThe stagingenvironmentis sharedA QAwould'vecaughtthisWe werenotified ofthis issue bya customer[new tech]would fixthisFeaturebranchdeploysThe logsdid notshow anerrorAWSservices aredifferentbetweenenvironmentsTypecheckingwould'vecaught thisDeploysareslowUnmergedPR to fixthisLow codecoverageblamedA thirdpartyservicewas faultyTherewereno logs"It'sdocumentedinConfluence"Seeddata islacking"That'son thebacklog"Packageupdate brokethings inprodThe relevanttest wascommentedoutTimepressures(imagined orotherwise)RequirementschangedThedeveloperresponsiblewent onholiday"It's afeature,not a bug"Thedocumentationwas out ofdateMicroservicecommunicationissuesThe stagingenvironmentis sharedA QAwould'vecaughtthisWe werenotified ofthis issue bya customer[new tech]would fixthisFeaturebranchdeploysThe logsdid notshow anerrorAWSservices aredifferentbetweenenvironmentsTypecheckingwould'vecaught this

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