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