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

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