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