Agile Retrospective Activities Paulo Caroli agileretroactivities.blogspot.com Paulo Caroli Agile Coach firstname.lastname@example.org Twitter: @paulocaroli
Agenda• Typical Retrospective Agenda• Many activities• Q&A
Typical Retrospective Agenda• Ice breaker• Set the context Opening• Prime directive• Group participation• Data gathering• Data grouping Middle• Selecting notes to talk about• Conversation• Action Items Closing• Next steps
The Prime DirectiveRegardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
ESVP Activity– Explorer • eager to learn new ideas and insights– Shoppers • will look over all the information and will be happy to go how with a new idea– Vacationer • Are not interested in the work, but are happy to be away from the daily grind– Prisoner • Fell like have been forced to attend
Keep Doing• What are the good things you like?• Think about things you would miss if they were removed; a particular practice, technique, technology, person, role, etc.• An example: Running tests locally before committing (This prevented me from breaking the build and delaying the branch cut).
Less Of• What are practices that might need a bit more refining--or reduction--in the current circumstance?• Think about things that do add value, but would be better with a little less.• An example: Stand ups have become status meetings and so there should be less of talking to one person (and more of talking to each other) during them.
More Of• What are the things that you want to try more?• Think about things you believe are not necessarily taking full advantage of.• A good example is that maybe people are pair programming but knowledge transfer might be gained by doing more of swapping programming partners.
Stop Doing• What is not adding much value?• Think about things you believe are not useful anymore.• An example: Perhaps writing status reporting email at the end of the day (because now the team is using an awesome tool which already conveys the current status information)
Start Doing• What are the new things that you want to try?• Think about new things you want to suggest.• An example: Tracking lead time (I read an article about it and believe would provide us precious information regarding process improvement)
Taking notes• Please use one post it per note• Consider using different post it colors for notes: – Team inward (things within our team boundaries) – Team outward (things beyond our team boundaries)
Activities to follow• data grouping• selecting notes to talk about• targeted conversation based on data• creating action itens
Building the Timeline• Decide the timeline start and end (e.g. 05 Jan– Inception Start; 12 Dec – 10 days after Prod)• Add a few noticeable events (e.g. New team members arrival, release 1, release 2)
Timeline Timeline Timeline Start Event A Event B Event C End timeline34
Building the Timeline• Split the timeline into a areas (2 to 4 recommended), and decide upon the areas (e.g. People, process, technology, other)
PeopleProcessTool/ techOther Timeline Timeline Start Event A Event B Event C End timeline 36
Building the Timeline• Decide upon post it colors for the notes (e.g. Green for well, pink for not so well)• Use another color for action items (e.g. Yellow for action items)
Timeline activity instrctions• Use one post it for each note• Follow the color code• Place the note on the area according to the timelime (e.g. A green post it “New load balance server” is added on the Technology area around Release2 timeline)• Timebox the activity (10 minutes recommended)
Activities to follow• data grouping• selecting notes to talk about• targeted reasoning based on data
Open the box A data gathering activity which fosterinnovation and challenges the current activities performed by the team. Retrospective activities Paulo Caroli
“The world as we have created it is a process of our thinking. It cannot be changed without changing our thinking.” ― Albert Einstein“They always say time changes things, but you actually have to change them yourself.” ― Andy Warhol
Inside this box are all activities performed by the team
Taking notes• Please use one post it per note• Use the different post it colors for notes related to: – process – tools and technology – Other• Timing: 10 minutes or less
Next step: validating changes• Executing ideas is often tougher than generating them.• How should we test ideas quickly and cheaply, so that we can afford to experiment?• Please go back to your notes and add new post –its (please use a new color) describing how to test the idea execution.
Activities to follow• data grouping• voting• selecting notes to talk about• targeted conversation based on data• creating action itens