focused onimprovingcodereadability ormaintainabilityparticipatedin cross-teamcollaborationlearneda newthingbettervisibilityonprioritiesresolvedablockersharedknowledge withthe teamthrough a demoor sessionworked extrato ensure wemet a sprintgoalcelebratedateammate’ssuccessproposeda creativesolution *one recurringproblemfollowed usacrosssprintscontributedto reducingtechnicaldebt *improvedmy technicalskills duringthe releasedailystand-upsstayedfocusedworked ona criticalissueFree!helpedidentify rootcauses forrecurringissuescontextswitchingtested ourpatienceproposed aprocessimprovementfor the teamcontributed tosprintretrospectivesor sharedfeedbackeffectivelymanagedtime acrossmultipletaskstakenmoreleavesparticipatedin sprintplanninghelpedanotherteammemberwe needmorefocus timeimproveddocumentationfor the teamdefinitionof donewasrespectedstorieswereclearerthan beforespilledmystory/iespair-programmedwith ateammateautomation/testingimprovedworked onreducingsilos withinthe teamparticipatedin team-buildingactivitiesa mistaketurnedinto alearning*reviewedcode andprovidedconstructivefeedbackutilized toolsorautomationto improveworkflowcontributedto a teamdiscussionexplored anew domainor featureareaworkedwellwithoutTSMcompletedall storiesassignedto meactivelylistenedduringdiscussionsand meetingsfocused onimprovingcodereadability ormaintainabilityparticipatedin cross-teamcollaborationlearneda newthingbettervisibilityonprioritiesresolvedablockersharedknowledge withthe teamthrough a demoor sessionworked extrato ensure wemet a sprintgoalcelebratedateammate’ssuccessproposeda creativesolution *one recurringproblemfollowed usacrosssprintscontributedto reducingtechnicaldebt *improvedmy technicalskills duringthe releasedailystand-upsstayedfocusedworked ona criticalissueFree!helpedidentify rootcauses forrecurringissuescontextswitchingtested ourpatienceproposed aprocessimprovementfor the teamcontributed tosprintretrospectivesor sharedfeedbackeffectivelymanagedtime acrossmultipletaskstakenmoreleavesparticipatedin sprintplanninghelpedanotherteammemberwe needmorefocus timeimproveddocumentationfor the teamdefinitionof donewasrespectedstorieswereclearerthan beforespilledmystory/iespair-programmedwith ateammateautomation/testingimprovedworked onreducingsilos withinthe teamparticipatedin team-buildingactivitiesa mistaketurnedinto alearning*reviewedcode andprovidedconstructivefeedbackutilized toolsorautomationto improveworkflowcontributedto a teamdiscussionexplored anew domainor featureareaworkedwellwithoutTSMcompletedall storiesassignedto meactivelylistenedduringdiscussionsand meetings

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