spilledmystory/iesstorieswereclearerthan beforeresolvedablockerworked extrato ensure wemet a sprintgoaltakenmoreleavescontributedto a teamdiscussioncontextswitchingtested ourpatiencepair-programmedwith ateammatecontributedto reducingtechnicaldebt *helpedidentify rootcauses forrecurringissuesexplored anew domainor featureareahelpedanotherteammemberdefinitionof donewasrespectedcontributed tosprintretrospectivesor sharedfeedbackFree!proposeda creativesolution *one recurringproblemfollowed usacrosssprintsreviewedcode andprovidedconstructivefeedbackimproveddocumentationfor the teamutilized toolsorautomationto improveworkflowcelebratedateammate’ssuccesseffectivelymanagedtime acrossmultipletasksautomation/testingimproveda mistaketurnedinto alearning*participatedin sprintplanningproposed aprocessimprovementfor the teamwe needmorefocus timeparticipatedin team-buildingactivitiesimprovedmy technicalskills duringthe releasecompletedall storiesassignedto melearneda newthingactivelylistenedduringdiscussionsand meetingsdailystand-upsstayedfocusedbettervisibilityonprioritiessharedknowledge withthe teamthrough a demoor sessionparticipatedin cross-teamcollaborationworked ona criticalissueworkedwellwithoutTSMworked onreducingsilos withinthe teamfocused onimprovingcodereadability ormaintainabilityspilledmystory/iesstorieswereclearerthan beforeresolvedablockerworked extrato ensure wemet a sprintgoaltakenmoreleavescontributedto a teamdiscussioncontextswitchingtested ourpatiencepair-programmedwith ateammatecontributedto reducingtechnicaldebt *helpedidentify rootcauses forrecurringissuesexplored anew domainor featureareahelpedanotherteammemberdefinitionof donewasrespectedcontributed tosprintretrospectivesor sharedfeedbackFree!proposeda creativesolution *one recurringproblemfollowed usacrosssprintsreviewedcode andprovidedconstructivefeedbackimproveddocumentationfor the teamutilized toolsorautomationto improveworkflowcelebratedateammate’ssuccesseffectivelymanagedtime acrossmultipletasksautomation/testingimproveda mistaketurnedinto alearning*participatedin sprintplanningproposed aprocessimprovementfor the teamwe needmorefocus timeparticipatedin team-buildingactivitiesimprovedmy technicalskills duringthe releasecompletedall storiesassignedto melearneda newthingactivelylistenedduringdiscussionsand meetingsdailystand-upsstayedfocusedbettervisibilityonprioritiessharedknowledge withthe teamthrough a demoor sessionparticipatedin cross-teamcollaborationworked ona criticalissueworkedwellwithoutTSMworked onreducingsilos withinthe teamfocused onimprovingcodereadability ormaintainability

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