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

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