we needmorefocus timecompletedall storiesassignedto mecontributed tosprintretrospectivesor sharedfeedbackparticipatedin sprintplanningproposeda creativesolution *contextswitchingtested ourpatienceworked onreducingsilos withinthe teamexplored anew domainor featureareaspilledmystory/iesdefinitionof donewasrespectedeffectivelymanagedtime acrossmultipletasksautomation/testingimprovedone recurringproblemfollowed usacrosssprintsworked ona criticalissueFree!improvedmy technicalskills duringthe releaseutilized toolsorautomationto improveworkflowa mistaketurnedinto alearning*workedwellwithoutTSMproposed aprocessimprovementfor the teamhelpedidentify rootcauses forrecurringissuesresolvedablockerlearneda newthingworked extrato ensure wemet a sprintgoalbettervisibilityonprioritiesimproveddocumentationfor the teampair-programmedwith ateammatecontributedto reducingtechnicaldebt *takenmoreleavescelebratedateammate’ssuccesscontributedto a teamdiscussionreviewedcode andprovidedconstructivefeedbackhelpedanotherteammemberfocused onimprovingcodereadability ormaintainabilityparticipatedin cross-teamcollaborationsharedknowledge withthe teamthrough a demoor sessionparticipatedin team-buildingactivitiesdailystand-upsstayedfocusedstorieswereclearerthan beforeactivelylistenedduringdiscussionsand meetingswe needmorefocus timecompletedall storiesassignedto mecontributed tosprintretrospectivesor sharedfeedbackparticipatedin sprintplanningproposeda creativesolution *contextswitchingtested ourpatienceworked onreducingsilos withinthe teamexplored anew domainor featureareaspilledmystory/iesdefinitionof donewasrespectedeffectivelymanagedtime acrossmultipletasksautomation/testingimprovedone recurringproblemfollowed usacrosssprintsworked ona criticalissueFree!improvedmy technicalskills duringthe releaseutilized toolsorautomationto improveworkflowa mistaketurnedinto alearning*workedwellwithoutTSMproposed aprocessimprovementfor the teamhelpedidentify rootcauses forrecurringissuesresolvedablockerlearneda newthingworked extrato ensure wemet a sprintgoalbettervisibilityonprioritiesimproveddocumentationfor the teampair-programmedwith ateammatecontributedto reducingtechnicaldebt *takenmoreleavescelebratedateammate’ssuccesscontributedto a teamdiscussionreviewedcode andprovidedconstructivefeedbackhelpedanotherteammemberfocused onimprovingcodereadability ormaintainabilityparticipatedin cross-teamcollaborationsharedknowledge withthe teamthrough a demoor sessionparticipatedin team-buildingactivitiesdailystand-upsstayedfocusedstorieswereclearerthan beforeactivelylistenedduringdiscussionsand 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
G
2
G
3
I
4
N
5
O
6
N
7
G
8
G
9
B
10
G
11
N
12
B
13
I
14
O
15
N
16
B
17
B
18
O
19
I
20
B
21
G
22
N
23
I
24
O
25
O
26
G
27
N
28
I
29
O
30
B
31
B
32
O
33
O
34
I
35
I
36
N
37
B
38
I
39
N
40
G
  1. G-we need more focus time
  2. G-completed all stories assigned to me
  3. I-contributed to sprint retrospectives or shared feedback
  4. N-participated in sprint planning
  5. O-proposed a creative solution *
  6. N-context switching tested our patience
  7. G-worked on reducing silos within the team
  8. G-explored a new domain or feature area
  9. B-spilled my story/ies
  10. G-definition of done was respected
  11. N-effectively managed time across multiple tasks
  12. B-automation/testing improved
  13. I-one recurring problem followed us across sprints
  14. O-worked on a critical issue
  15. N-Free!
  16. B-improved my technical skills during the release
  17. B-utilized tools or automation to improve workflow
  18. O-a mistake turned into a learning*
  19. I-worked well without TSM
  20. B-proposed a process improvement for the team
  21. G-helped identify root causes for recurring issues
  22. N-resolved a blocker
  23. I-learned a new thing
  24. O-worked extra to ensure we met a sprint goal
  25. O-better visibility on priorities
  26. G-improved documentation for the team
  27. N-pair-programmed with a teammate
  28. I-contributed to reducing technical debt *
  29. O-taken more leaves
  30. B-celebrated a teammate’s success
  31. B-contributed to a team discussion
  32. O-reviewed code and provided constructive feedback
  33. O-helped another team member
  34. I-focused on improving code readability or maintainability
  35. I-participated in cross-team collaboration
  36. N-shared knowledge with the team through a demo or session
  37. B-participated in team-building activities
  38. I-daily stand-ups stayed focused
  39. N-stories were clearer than before
  40. G-actively listened during discussions and meetings