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

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