contributedto reducingtechnicaldebt *Free!explored anew domainor featureareaautomation/testingimprovedspilledmystory/iesdefinitionof donewasrespectedlearneda newthingparticipatedin sprintplanningworked extrato ensure wemet a sprintgoalimprovedmy technicalskills duringthe releaseutilized toolsorautomationto improveworkflowworked onreducingsilos withinthe teamcontextswitchingtested ourpatiencepair-programmedwith ateammatecontributed tosprintretrospectivesor sharedfeedbackeffectivelymanagedtime acrossmultipletaskscompletedall storiesassignedto mesharedknowledge withthe teamthrough a demoor sessionfocused onimprovingcodereadability ormaintainabilitycelebratedateammate’ssuccesstakenmoreleavesparticipatedin team-buildingactivitiesproposed aprocessimprovementfor the teamhelpedanotherteammemberresolvedablockerdailystand-upsstayedfocusedbettervisibilityonprioritiesone recurringproblemfollowed usacrosssprintscontributedto a teamdiscussionhelpedidentify rootcauses forrecurringissueswe needmorefocus timeworkedwellwithoutTSMstorieswereclearerthan beforeparticipatedin cross-teamcollaborationactivelylistenedduringdiscussionsand meetingsproposeda creativesolution *a mistaketurnedinto alearning*improveddocumentationfor the teamreviewedcode andprovidedconstructivefeedbackworked ona criticalissuecontributedto reducingtechnicaldebt *Free!explored anew domainor featureareaautomation/testingimprovedspilledmystory/iesdefinitionof donewasrespectedlearneda newthingparticipatedin sprintplanningworked extrato ensure wemet a sprintgoalimprovedmy technicalskills duringthe releaseutilized toolsorautomationto improveworkflowworked onreducingsilos withinthe teamcontextswitchingtested ourpatiencepair-programmedwith ateammatecontributed tosprintretrospectivesor sharedfeedbackeffectivelymanagedtime acrossmultipletaskscompletedall storiesassignedto mesharedknowledge withthe teamthrough a demoor sessionfocused onimprovingcodereadability ormaintainabilitycelebratedateammate’ssuccesstakenmoreleavesparticipatedin team-buildingactivitiesproposed aprocessimprovementfor the teamhelpedanotherteammemberresolvedablockerdailystand-upsstayedfocusedbettervisibilityonprioritiesone recurringproblemfollowed usacrosssprintscontributedto a teamdiscussionhelpedidentify rootcauses forrecurringissueswe needmorefocus timeworkedwellwithoutTSMstorieswereclearerthan beforeparticipatedin cross-teamcollaborationactivelylistenedduringdiscussionsand meetingsproposeda creativesolution *a mistaketurnedinto alearning*improveddocumentationfor the teamreviewedcode andprovidedconstructivefeedbackworked ona criticalissue

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