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