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

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