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

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