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