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

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