participatedin cross-teamcollaborationeffectivelymanagedtime acrossmultipletasksstorieswereclearerthan beforereviewedcode andprovidedconstructivefeedbackcontributed tosprintretrospectivesor sharedfeedbackworked extrato ensure wemet a sprintgoalimproveddocumentationfor the teamactivelylistenedduringdiscussionsand meetingsproposeda creativesolution *contributedto a teamdiscussiona mistaketurnedinto alearning*utilized toolsorautomationto improveworkflowFree!participatedin team-buildingactivitieswe needmorefocus timedailystand-upsstayedfocusedpair-programmedwith ateammateimprovedmy technicalskills duringthe releaseworked onreducingsilos withinthe teamone recurringproblemfollowed usacrosssprintsworkedwellwithoutTSMautomation/testingimprovedparticipatedin sprintplanningfocused onimprovingcodereadability ormaintainabilitysharedknowledge withthe teamthrough a demoor sessionbettervisibilityonprioritiesdefinitionof donewasrespectedlearneda newthingworked ona criticalissuecelebratedateammate’ssuccesscontributedto reducingtechnicaldebt *resolvedablockercompletedall storiesassignedto mehelpedanotherteammembertakenmoreleavescontextswitchingtested ourpatienceproposed aprocessimprovementfor the teamspilledmystory/ieshelpedidentify rootcauses forrecurringissuesexplored anew domainor featureareaparticipatedin cross-teamcollaborationeffectivelymanagedtime acrossmultipletasksstorieswereclearerthan beforereviewedcode andprovidedconstructivefeedbackcontributed tosprintretrospectivesor sharedfeedbackworked extrato ensure wemet a sprintgoalimproveddocumentationfor the teamactivelylistenedduringdiscussionsand meetingsproposeda creativesolution *contributedto a teamdiscussiona mistaketurnedinto alearning*utilized toolsorautomationto improveworkflowFree!participatedin team-buildingactivitieswe needmorefocus timedailystand-upsstayedfocusedpair-programmedwith ateammateimprovedmy technicalskills duringthe releaseworked onreducingsilos withinthe teamone recurringproblemfollowed usacrosssprintsworkedwellwithoutTSMautomation/testingimprovedparticipatedin sprintplanningfocused onimprovingcodereadability ormaintainabilitysharedknowledge withthe teamthrough a demoor sessionbettervisibilityonprioritiesdefinitionof donewasrespectedlearneda newthingworked ona criticalissuecelebratedateammate’ssuccesscontributedto reducingtechnicaldebt *resolvedablockercompletedall storiesassignedto mehelpedanotherteammembertakenmoreleavescontextswitchingtested ourpatienceproposed aprocessimprovementfor the teamspilledmystory/ieshelpedidentify rootcauses forrecurringissuesexplored anew domainor featurearea

AH - 26.1 Release Retrospective - Call List

(Print) Use this randomly generated list as your call list when playing the game. 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
I
2
N
3
N
4
O
5
I
6
O
7
G
8
G
9
O
10
B
11
O
12
B
13
N
14
B
15
G
16
I
17
N
18
B
19
G
20
I
21
I
22
B
23
N
24
I
25
N
26
O
27
G
28
I
29
O
30
B
31
I
32
N
33
G
34
O
35
O
36
N
37
B
38
B
39
G
40
G
  1. I-participated in cross-team collaboration
  2. N-effectively managed time across multiple tasks
  3. N-stories were clearer than before
  4. O-reviewed code and provided constructive feedback
  5. I-contributed to sprint retrospectives or shared feedback
  6. O-worked extra to ensure we met a sprint goal
  7. G-improved documentation for the team
  8. G-actively listened during discussions and meetings
  9. O-proposed a creative solution *
  10. B-contributed to a team discussion
  11. O-a mistake turned into a learning*
  12. B-utilized tools or automation to improve workflow
  13. N-Free!
  14. B-participated in team-building activities
  15. G-we need more focus time
  16. I-daily stand-ups stayed focused
  17. N-pair-programmed with a teammate
  18. B-improved my technical skills during the release
  19. G-worked on reducing silos within the team
  20. I-one recurring problem followed us across sprints
  21. I-worked well without TSM
  22. B-automation/testing improved
  23. N-participated in sprint planning
  24. I-focused on improving code readability or maintainability
  25. N-shared knowledge with the team through a demo or session
  26. O-better visibility on priorities
  27. G-definition of done was respected
  28. I-learned a new thing
  29. O-worked on a critical issue
  30. B-celebrated a teammate’s success
  31. I-contributed to reducing technical debt *
  32. N-resolved a blocker
  33. G-completed all stories assigned to me
  34. O-helped another team member
  35. O-taken more leaves
  36. N-context switching tested our patience
  37. B-proposed a process improvement for the team
  38. B-spilled my story/ies
  39. G-helped identify root causes for recurring issues
  40. G-explored a new domain or feature area