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

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