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