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