worked extrato ensure wemet a sprintgoalworked ona criticalissuecontributedto reducingtechnicaldebt *dailystand-upsstayedfocusedpair-programmedwith ateammatereviewedcode andprovidedconstructivefeedbackcontributedto a teamdiscussionimprovedmy technicalskills duringthe releaseactivelylistenedduringdiscussionsand meetingswe needmorefocus timeparticipatedin sprintplanningparticipatedin cross-teamcollaborationa mistaketurnedinto alearning*sharedknowledge withthe teamthrough a demoor sessionproposeda creativesolution *one recurringproblemfollowed usacrosssprintsstorieswereclearerthan beforeimproveddocumentationfor the teamcontributed tosprintretrospectivesor sharedfeedbackworked onreducingsilos withinthe teamcompletedall storiesassignedto mecontextswitchingtested ourpatiencespilledmystory/iesfocused onimprovingcodereadability ormaintainabilityhelpedidentify rootcauses forrecurringissuesutilized toolsorautomationto improveworkflowdefinitionof donewasrespectedresolvedablockerbettervisibilityonprioritiesproposed aprocessimprovementfor the teamFree!learneda newthingcelebratedateammate’ssuccessworkedwellwithoutTSMhelpedanotherteammemberautomation/testingimprovedeffectivelymanagedtime acrossmultipletasksexplored anew domainor featureareatakenmoreleavesparticipatedin team-buildingactivitiesworked extrato ensure wemet a sprintgoalworked ona criticalissuecontributedto reducingtechnicaldebt *dailystand-upsstayedfocusedpair-programmedwith ateammatereviewedcode andprovidedconstructivefeedbackcontributedto a teamdiscussionimprovedmy technicalskills duringthe releaseactivelylistenedduringdiscussionsand meetingswe needmorefocus timeparticipatedin sprintplanningparticipatedin cross-teamcollaborationa mistaketurnedinto alearning*sharedknowledge withthe teamthrough a demoor sessionproposeda creativesolution *one recurringproblemfollowed usacrosssprintsstorieswereclearerthan beforeimproveddocumentationfor the teamcontributed tosprintretrospectivesor sharedfeedbackworked onreducingsilos withinthe teamcompletedall storiesassignedto mecontextswitchingtested ourpatiencespilledmystory/iesfocused onimprovingcodereadability ormaintainabilityhelpedidentify rootcauses forrecurringissuesutilized toolsorautomationto improveworkflowdefinitionof donewasrespectedresolvedablockerbettervisibilityonprioritiesproposed aprocessimprovementfor the teamFree!learneda newthingcelebratedateammate’ssuccessworkedwellwithoutTSMhelpedanotherteammemberautomation/testingimprovedeffectivelymanagedtime acrossmultipletasksexplored anew domainor featureareatakenmoreleavesparticipatedin team-buildingactivities

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