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

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