The Kama Sutra of RetrospectivesPresentation Transcript
The Kama Sutra of Retrospectives
Who are you to @#$%^& lecture me? www.ciklum.net 2 Alexander Lutsaevsky
Ciklum Technical Consultant
Certified Scrum Product Owner, ISTQB Certified Tester, Certified Owner of Other Useless Papers
Founder and speaker at agile.kh.ua
Speaker at misc. conferences: PM Zone, Agile Base Camp, QA Club, Agileee, etc.
Cross-functional Project Manager with more than 5 years of experience managing distributed and multinational teamsboth for agile and complex industry regulated projects. Alexander has proven track record of successful on-time and on-budget project delivery from different business domains: accounting and finance controlling, healthcare informatics and medical devices, enterprise resource planning, transportation management and many more.
Technique: Dot Vote
6 Thinking Hats
Goal: Effectively organize discussing emotional, rational, positive, negative feedbacks. Time: approximately 1 hour 6 Thinking Hats
Brief summary of De Bono’s Six Thinking Hats process.
Blue Hat – objectives for the session.
White Hat – generating facts from the last iteration.
Yellow Hat – focus on positive things.
Black Hat – focus on negative things.
Green Hat – ideas about improvement from the helicopter view.
Red Hat – emotive statements.
Conclusions and actions.
Goal: Measure important areas of the process by the team. Time: approximately 1 hour Spider Web
Explain idea and how to rate areas
Define important areas of discussion
Draw the spider web on the white board
Distribute the pieces of paper to everyone to draw the same spider web and rate the areas
Gather papers and accumulate the results from everyone
Discuss each area
Work out the improvement plan
Goal: Focus on improvements, instead of fixing problems. Time: approximately 1 hour Appreciative Retrospective
Setting stage and check in
Gather information (group brainstorm or individual post-it notes):
Group the post-its or facts
Goal: Expose the most pressing issues in an anonymous manner Time: approximately 45 minutes Top 5
Gather top 5 issues from people via email
Draw all the issues on the whiteboard
Ask the team to group the issues
Generate actions to solve problems (effective when working in pairs and then escalating the results to the group)
Plan of Actions Retrospective
Goal: Focus on generating clear plan and taking actions Time: approximately 40 minutes Plan of Actions Retrospective
Gather information from the team members
Long-term goal: e.g. have test automation on acceptance-test level
Now-Action: e.g. Vasya will automate one test using Selenium
Objectives, Activities, Deliveries
Bass Vode’s (http://bit.ly/KamaSutra_ActionPlan) plan of action – individual action generation, pairs select top actions, whole group discuss top actions
Goal: Make the retrospective meeting short. Time: 10-25 minutes. Start/Stop/Continue/More/Less
Draw a circle on a poster, divide it into 5 sections and write the words "start", "stop", "continue", "more of" and "less of" around each section.
Generate action plan.
Force Field Analysis
Goal: Focus on specific area, discuss drivers and restrains Time: approximately 60 minutes Force Field Analysis
Pick a topic
Set the timer and give the team five minutes to list all the supporting/driving factors for the topic
Identify top drivers
List all the inhibiting/restraining factors for the topic.
Identify top restrains
Try to find relations between drivers and restrains factors
Generate action plan
Description is here http://bit.ly/KamaSutra_ForceField
Goal: Focus on specific topics, shorten the time for retrospective Time: approximately 30 minutes Pomodoro Retrospective
Generate the list of topics to discuss
5 minutes to discuss each topic
2-3 minutes to get summary
Goal: Focus on specific topics, shorten the time for retrospective Time: approximately 30 minutes Question Retrospective
Before the retro, prepare sheets of paper for each team member each having a different question on the top, for example:
In this sprint, what things happened that were unusual?
In this sprint, what things did we do well?
In this sprint, what did we do that we should avoid doing in the future?
The questions will be distributed at random to team members.
Each person writes something, then passes the sheet to their left, then writes something on the next sheet…
Process: Works Well/Needs Improvement MAX UPGRADE NEEDS TO BE UPGRADED
Who? How? When? How to verify?
Retrospective of Retrospectives
Decision Log http://bit.ly/KamaSutra_Self
Distributed Retrospectives Separate individual vs. joint improvements Individual meeting before joint Offline part: use surveys More time to check in Use wiki to store results!