sharedknowledge withthe teamthrough a demoor sessionexplored anew domainor featurearealearneda newthinghelpedanotherteammemberbettervisibilityonprioritiesautomation/testingimprovedcontributed tosprintretrospectivesor sharedfeedbackreviewedcode andprovidedconstructivefeedbacka mistaketurnedinto alearning*participatedin sprintplanningcontributedto reducingtechnicaldebt *effectivelymanagedtime acrossmultipletasksone recurringproblemfollowed usacrosssprintsparticipatedin team-buildingactivitiesworked extrato ensure wemet a sprintgoaltakenmoreleavesworkedwellwithoutTSMwe needmorefocus timeworked ona criticalissueFree!improveddocumentationfor the teamactivelylistenedduringdiscussionsand meetingsstorieswereclearerthan beforeparticipatedin cross-teamcollaborationworked onreducingsilos withinthe teamfocused onimprovingcodereadability ormaintainabilitycontextswitchingtested ourpatiencedefinitionof donewasrespectedresolvedablockerspilledmystory/iesutilized toolsorautomationto improveworkflowhelpedidentify rootcauses forrecurringissuesimprovedmy technicalskills duringthe releasedailystand-upsstayedfocusedcelebratedateammate’ssuccesscompletedall storiesassignedto mepair-programmedwith ateammatecontributedto a teamdiscussionproposeda creativesolution *proposed aprocessimprovementfor the teamsharedknowledge withthe teamthrough a demoor sessionexplored anew domainor featurearealearneda newthinghelpedanotherteammemberbettervisibilityonprioritiesautomation/testingimprovedcontributed tosprintretrospectivesor sharedfeedbackreviewedcode andprovidedconstructivefeedbacka mistaketurnedinto alearning*participatedin sprintplanningcontributedto reducingtechnicaldebt *effectivelymanagedtime acrossmultipletasksone recurringproblemfollowed usacrosssprintsparticipatedin team-buildingactivitiesworked extrato ensure wemet a sprintgoaltakenmoreleavesworkedwellwithoutTSMwe needmorefocus timeworked ona criticalissueFree!improveddocumentationfor the teamactivelylistenedduringdiscussionsand meetingsstorieswereclearerthan beforeparticipatedin cross-teamcollaborationworked onreducingsilos withinthe teamfocused onimprovingcodereadability ormaintainabilitycontextswitchingtested ourpatiencedefinitionof donewasrespectedresolvedablockerspilledmystory/iesutilized toolsorautomationto improveworkflowhelpedidentify rootcauses forrecurringissuesimprovedmy technicalskills duringthe releasedailystand-upsstayedfocusedcelebratedateammate’ssuccesscompletedall storiesassignedto mepair-programmedwith ateammatecontributedto a teamdiscussionproposeda creativesolution *proposed aprocessimprovementfor the team

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