25.3 Release Retrospective - 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. Utilized tools or automation to improve workflow.
2. Maintained positive attitude throughout the sprint.
3. Improved performance of a module.
4. Actively listened during discussions and meetings.
5. Focused on improving code readability or maintainability.
6. Helped another team member.
7. Effectively managed time across multiple tasks.
8. Explored a new domain or feature area.
9. Shared a useful article or resource with the team.
10. Identified areas of improvement in the process.
11. Tested a teammate’s feature.
12. Supported team morale during a tough sprint.
13. Refactored a complex piece of code.
14. Proposed a creative solution.
15. Worked on NFR requirements, like performance, security.
16. Completed all stories assigned to me.
17. Participated in backlog refinement.
18. Learned a new thing.
19. Participated in sprint planning.
20. Volunteered for a stretch task.
21. Worked on customer issues.
22. Helped identify root causes for recurring issues.
23. Resolved a blocker.
24. Leveraged my leaves effectively to maintain work-life balance.
25. Handled feedback maturely.
26. Worked on reducing silos within the team.
27. Worked well without TSM.
28. Enhanced unit/integration test coverage.
29. Helped a new team member get onboarded.
30. Shared knowledge with the team through a demo or session.
31. Successfully handled on-call responsibilities.
32. Contributed to a team discussion.
33. Reviewed code and provided constructive feedback.
34. Contributed to sprint retrospectives or shared feedback.
35. Cleaned up obsolete code or config.
36. Improved my technical skills during the release.
37. Took ownership of an unassigned story.
38. Documented a recurring process for the team.
39. Kept PR cycle time minimal.
40. Contributed to design discussions.
41. Contributed to reducing technical debt.
42. Gave constructive feedback during retrospectives.
43. Proactively communicated blockers.
44. Pair-programmed with a teammate.
45. Resolved a long-standing issue.
46. Spoke up during daily stand-ups with clarity.
47. Worked on a critical issue.
48. Acted as a backup in the absence of another member.
49. Improved documentation for the team.
50. Practiced active retrospection during the sprint.
51. Took initiative on a new task.
52. Participated in cross-team collaboration.
53. Clarified acceptance criteria with PO.
54. Helped unblock a teammate.
55. Celebrated a teammate’s success.
56. Practiced clean code principles.
57. Resolved a production issue quickly.
58. Built reusable components.
59. Raised concerns proactively.
60. Worked extra to ensure we met a sprint goal.
61. Maintained work-life balance effectively.
62. Proposed a process improvement for the team.
63. Collaborated effectively with non-tech teams.
64. Participated in team-building activities.