Tookinitiativeon a newtask.Identifiedareas ofimprovementin theprocess.Supportedteam moraleduring atough sprint.Participatedin cross-teamcollaboration.Workedon acriticalissue.Worked onreducingsilos withinthe team.Completedall storiesassignedto me.WorkedwellwithoutTSM.Volunteeredfor a stretchtask.Clarifiedacceptancecriteria withPO.Proposed aprocessimprovementfor the team.Spoke upduring dailystand-upswith clarity.Leveraged myleaveseffectively tomaintain work-life balance.Practicedcleancodeprinciples.Gaveconstructivefeedbackduringretrospectives.Builtreusablecomponents.Resolvedablocker.Worked onNFRrequirements,likeperformance,security.Successfullyhandled on-callresponsibilities.Handledfeedbackmaturely.Resolved aproductionissuequickly.Contributedto designdiscussions.Kept PRcycle timeminimal.Enhancedunit/integrationtest coverage.Pair-programmedwith ateammate.Participatedin backlogrefinement.Raisedconcernsproactively.Practicedactiveretrospectionduring thesprint.Participatedin team-buildingactivities.Effectivelymanagedtime acrossmultipletasks.Documenteda recurringprocess forthe team.Shared auseful articleor resourcewith theteam.Explored anew domainor featurearea.Proposeda creativesolution.Contributed tosprintretrospectivesor sharedfeedback.Cleaned upobsoletecode orconfig.Tested ateammate’sfeature.Improvedperformanceof a module.Maintainedpositiveattitudethroughoutthe sprint.Helpedidentify rootcauses forrecurringissues.Contributedto reducingtechnicaldebt.Activelylistenedduringdiscussionsand meetings.Focused onimprovingcodereadability ormaintainability.Proactivelycommunicatedblockers.Improveddocumentationfor the team.Utilized toolsorautomationto improveworkflow.Tookownership ofanunassignedstory.Workedextra toensure wemet a sprintgoal.Improvedmy technicalskills duringthe release.Resolveda long-standingissue.Helped anew teammember getonboarded.Helpedunblock ateammate.Reviewedcode andprovidedconstructivefeedback.Collaboratedeffectivelywith non-tech teams.Sharedknowledge withthe teamthrough a demoor session.Helpedanotherteammember.Celebratedateammate’ssuccess.Acted as abackup inthe absenceof anothermember.Refactoreda complexpiece ofcode.Contributedto a teamdiscussion.Maintainedwork-lifebalanceeffectively.Learneda newthing.Workedoncustomerissues.Participatedin sprintplanning.Tookinitiativeon a newtask.Identifiedareas ofimprovementin theprocess.Supportedteam moraleduring atough sprint.Participatedin cross-teamcollaboration.Workedon acriticalissue.Worked onreducingsilos withinthe team.Completedall storiesassignedto me.WorkedwellwithoutTSM.Volunteeredfor a stretchtask.Clarifiedacceptancecriteria withPO.Proposed aprocessimprovementfor the team.Spoke upduring dailystand-upswith clarity.Leveraged myleaveseffectively tomaintain work-life balance.Practicedcleancodeprinciples.Gaveconstructivefeedbackduringretrospectives.Builtreusablecomponents.Resolvedablocker.Worked onNFRrequirements,likeperformance,security.Successfullyhandled on-callresponsibilities.Handledfeedbackmaturely.Resolved aproductionissuequickly.Contributedto designdiscussions.Kept PRcycle timeminimal.Enhancedunit/integrationtest coverage.Pair-programmedwith ateammate.Participatedin backlogrefinement.Raisedconcernsproactively.Practicedactiveretrospectionduring thesprint.Participatedin team-buildingactivities.Effectivelymanagedtime acrossmultipletasks.Documenteda recurringprocess forthe team.Shared auseful articleor resourcewith theteam.Explored anew domainor featurearea.Proposeda creativesolution.Contributed tosprintretrospectivesor sharedfeedback.Cleaned upobsoletecode orconfig.Tested ateammate’sfeature.Improvedperformanceof a module.Maintainedpositiveattitudethroughoutthe sprint.Helpedidentify rootcauses forrecurringissues.Contributedto reducingtechnicaldebt.Activelylistenedduringdiscussionsand meetings.Focused onimprovingcodereadability ormaintainability.Proactivelycommunicatedblockers.Improveddocumentationfor the team.Utilized toolsorautomationto improveworkflow.Tookownership ofanunassignedstory.Workedextra toensure wemet a sprintgoal.Improvedmy technicalskills duringthe release.Resolveda long-standingissue.Helped anew teammember getonboarded.Helpedunblock ateammate.Reviewedcode andprovidedconstructivefeedback.Collaboratedeffectivelywith non-tech teams.Sharedknowledge withthe teamthrough a demoor session.Helpedanotherteammember.Celebratedateammate’ssuccess.Acted as abackup inthe absenceof anothermember.Refactoreda complexpiece ofcode.Contributedto a teamdiscussion.Maintainedwork-lifebalanceeffectively.Learneda newthing.Workedoncustomerissues.Participatedin sprintplanning.

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