worked oncustomerissues.sharedknowledge withthe teamthrough a demoor session.helpedanotherteammember.gaveconstructivefeedbackduringretrospectives.worked onreducingsilos withinthe team.worked extrato ensure wemet a sprintgoal.Worked onNFRrequirements,likeperformance,security.participated insprint planning.,explored a newdomain orfeature area.activelylistenedduringdiscussionsand meetingsparticipated inteam-buildingactivities,participated incross-teamcollaboration.Free!celebratedateammate’ssuccess.gaveconstructivefeedbackduringretrospectives.participatedin sprintplanningreviewedcode andprovidedconstructivefeedback.contributed tosprintretrospectivesor sharedfeedback.Free!contributedto a teamdiscussion.,worked wellwithout TSM.proposed aprocessimprovementfor the team.completed allstoriesassigned tome., worked ona critical issue.completedall storiesassignedto me.worked onreducingsilos withinthe team.Focused onimprovingcodereadability ormaintainability.Utilized toolsorautomationto improveworkflow.learneda newthing.explorednewtechnologyresolvedablocker.TakenmoreleavesEffectivelymanagedtime acrossmultipletasks.proactivelycommunicatedblockers.improvedmy technicalskills duringthe release.WorkedwellwithoutTSMHelpedidentify rootcauses forrecurringissues.pair-programmedwith ateammate.I spilledmystory/iescontributedto reducingtechnicaldebt.worked oncustomerissues.sharedknowledge withthe teamthrough a demoor session.helpedanotherteammember.gaveconstructivefeedbackduringretrospectives.worked onreducingsilos withinthe team.worked extrato ensure wemet a sprintgoal.Worked onNFRrequirements,likeperformance,security.participated insprint planning.,explored a newdomain orfeature area.activelylistenedduringdiscussionsand meetingsparticipated inteam-buildingactivities,participated incross-teamcollaboration.Free!celebratedateammate’ssuccess.gaveconstructivefeedbackduringretrospectives.participatedin sprintplanningreviewedcode andprovidedconstructivefeedback.contributed tosprintretrospectivesor sharedfeedback.Free!contributedto a teamdiscussion.,worked wellwithout TSM.proposed aprocessimprovementfor the team.completed allstoriesassigned tome., worked ona critical issue.completedall storiesassignedto me.worked onreducingsilos withinthe team.Focused onimprovingcodereadability ormaintainability.Utilized toolsorautomationto improveworkflow.learneda newthing.explorednewtechnologyresolvedablocker.TakenmoreleavesEffectivelymanagedtime acrossmultipletasks.proactivelycommunicatedblockers.improvedmy technicalskills duringthe release.WorkedwellwithoutTSMHelpedidentify rootcauses forrecurringissues.pair-programmedwith ateammate.I spilledmystory/iescontributedto reducingtechnicaldebt.

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