participatedin team-buildingactivitiesFree!learneda newthing.TakenmoreleavesFree!Effectivelymanagedtime acrossmultipletasks.pair-programmedwith ateammate.improveddocumentationfor the team.explored anew domainor featurearea.activelylistenedduringdiscussionsand meetingssharedknowledge withthe teamthrough a demoor session.participatedin cross-teamcollaboration.Utilized toolsorautomationto improveworkflow.improvedmy technicalskills duringthe release.I spilledmystory/ies.proposeda creativesolution.worked extrato ensure wemet a sprintgoal.contributed tosprintretrospectivesor sharedfeedback.helpedanotherteammember.contributedto reducingtechnicaldebt.Worked onNFRrequirements,likeperformance,security.proactivelycommunicatedblockers.worked oncustomerissues.worked onreducingsilos withinthe team.resolvedablocker.completedall storiesassignedto me.participatedin sprintplanning.contributedto a teamdiscussion.gaveconstructivefeedbackduringretrospectives.celebratedateammate’ssuccess.Focused onimprovingcodereadability ormaintainability.Helpedidentify rootcauses forrecurringissues.proposed aprocessimprovementfor the team.workedwellwithoutTSM.worked ona criticalissue.reviewedcode andprovidedconstructivefeedback.participatedin team-buildingactivitiesFree!learneda newthing.TakenmoreleavesFree!Effectivelymanagedtime acrossmultipletasks.pair-programmedwith ateammate.improveddocumentationfor the team.explored anew domainor featurearea.activelylistenedduringdiscussionsand meetingssharedknowledge withthe teamthrough a demoor session.participatedin cross-teamcollaboration.Utilized toolsorautomationto improveworkflow.improvedmy technicalskills duringthe release.I spilledmystory/ies.proposeda creativesolution.worked extrato ensure wemet a sprintgoal.contributed tosprintretrospectivesor sharedfeedback.helpedanotherteammember.contributedto reducingtechnicaldebt.Worked onNFRrequirements,likeperformance,security.proactivelycommunicatedblockers.worked oncustomerissues.worked onreducingsilos withinthe team.resolvedablocker.completedall storiesassignedto me.participatedin sprintplanning.contributedto a teamdiscussion.gaveconstructivefeedbackduringretrospectives.celebratedateammate’ssuccess.Focused onimprovingcodereadability ormaintainability.Helpedidentify rootcauses forrecurringissues.proposed aprocessimprovementfor the team.workedwellwithoutTSM.worked ona criticalissue.reviewedcode andprovidedconstructivefeedback.

Iron Man 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
  1. participated in team-building activities
  2. Free!
  3. learned a new thing.
  4. Taken more leaves
  5. Free!
  6. Effectively managed time across multiple tasks.
  7. pair-programmed with a teammate.
  8. improved documentation for the team.
  9. explored a new domain or feature area.
  10. actively listened during discussions and meetings
  11. shared knowledge with the team through a demo or session.
  12. participated in cross-team collaboration.
  13. Utilized tools or automation to improve workflow.
  14. improved my technical skills during the release.
  15. I spilled my story/ies.
  16. proposed a creative solution.
  17. worked extra to ensure we met a sprint goal.
  18. contributed to sprint retrospectives or shared feedback.
  19. helped another team member.
  20. contributed to reducing technical debt.
  21. Worked on NFR requirements, like performance, security.
  22. proactively communicated blockers.
  23. worked on customer issues.
  24. worked on reducing silos within the team.
  25. resolved a blocker.
  26. completed all stories assigned to me.
  27. participated in sprint planning.
  28. contributed to a team discussion.
  29. gave constructive feedback during retrospectives.
  30. celebrated a teammate’s success.
  31. Focused on improving code readability or maintainability.
  32. Helped identify root causes for recurring issues.
  33. proposed a process improvement for the team.
  34. worked well without TSM.
  35. worked on a critical issue.
  36. reviewed code and provided constructive feedback.