Retrospectives For Distributed Teams
Download as PPTX, PDF2 likes1,702 views
The document discusses the structure and importance of Agile retrospectives, emphasizing the need for participation and shared context among team members. It outlines stages of a retrospective including setting the stage, gathering data, generating insights, deciding on actions, and closing the retrospective. Additionally, it highlights common anti-patterns to avoid and provides resources and tools for facilitating retrospectives, especially in distributed teams.
Retrospectives For Distributed Teams
- 2. About me 2 @DanaPylayeva NYC Scrum User GroupI
- 3. Why Retrospectives? 3 http://pixabay.com/en/globe-earth-magnifying-glass-hand-71443/
- 6. Agile Retrospective Framework Stage Data Insights Action Close 6Adapted from “Agile Retrospectives. Making Good Teams Great”~ Esther Derby, Diana Larsen”
- 7. Goal: Establish a safe container, ensure participation, get everyone’s voice heard in the first 5 min. Activity: 1. Ask participants to take turns in stating their current feelings in 1-2 words. 2. Review working agreements. Set the stage 7 Stage Data Insights Action CloseStage
- 9. Stage Datazzzzz zzzzzzzz Insights ActionClosingStageData Insights Action Close Gather Data 9 Data Stage Goal: Build a shared context. Without it people are working from a narrow set of data – their own. Activity: 1. Build a timeline with data 2. Feelings (Emotion seismograph or labels with emotions)
- 10. Stage DataInsights Action CloseStage Data InsightsActionClosing Generate Insights 10 Insights Insights Goal: Figure out what this information means Activity: 1. Many options: - Plus/Delta - Stop/Start/Continue - Appreciation/Puzzles/Risks/Wishes 2. Route Cause Analysis - Fishbone diagram - 5 Whys
- 11. Stage DataInsights Action CloseStage Data InsightsActionClosing Decide What To Do Goal: Select highest priority improvement item to act on during the next sprint. Action: - Dot Voting - Design the experiment - Select the next steps 11 Action
- 12. Stage Data InsightsActionClosing StageDataInsights Action Closing Close The Retrospective Goal: Improve the retrospective, appreciation Activity: 1. Quick retro on retrospective - Plus/Delta or - Helped/Hindered/Hypothesis 2. Thank you! 12 Close
- 13. An Alternative – Six Thinking Hats 13
- 15. #1 - A whining session 15
- 16. #2 - A witch hunt 16 She broke the build! Did not finish her story!
- 17. #3 - Skipping retrospectives 17 Scrum Master Image by Pitke http://en.wikipedia.org/wiki/Lead_(tack)#mediaviewer/File:Strong_little_thing.jpg Scrum Team
- 18. #4 - Boredom 18 Image by Roman Barshay http://barshay.org/p602909396/h477e29d8#h477e29d8
- 19. #5- Do NOTHING Retrospective 19 Photo by Sali Sasaki https://www.flickr.com/photos/salisasaki/6920798999/
- 20. #6- Make The Whole World a Better Place 20http://pixabay.com/en/district-about-arched-human-circle-291098/
- 22. 22 Simulating Face To Face Communication
- 23. Simulating In-Room Experience With GoogleDocs 23
- 25. Getting Creative.. 25 In the room: On a WebEx( in GoogleDocs): Combined: Frogs that annoyed us last Sprint Remember the future: The amazing way we worked together in next Sprint
- 26. On-line Resources 0 www.innovationgames.com 0 http://retrospectivewiki.org/index.php?title=Main_Pa ge 0 http://www.strongandagile.co.uk/index.php/facilitati ng-distributed-team-retrospectives/ 0 http://en.wikipedia.org/wiki/Six_Thinking_Hats 26
- 27. Tools For Distributed Retrospectives 0 GoogleDoc Template from Ilio Krumins-Beens & Terrence McGovern https://docs.google.com/drawings/d/17cyx7QZJLpM IoVHsdlAldXfgU-cPdIg9v_XlVhhtkZU/edit 0 http://padlet.com/ 0 www.seenowdo.com 0 trello.com 27
- 29. Putting It All Together: Let’s Conduct An Experiment! 29
- 30. 30
- 31. Retrospective of NYC Scrum User Group. October 16, 2014 31
Editor's Notes
- #4: One of the most important of all Scrum ceremonies. Allows a team “Inspect and Adapt” their process. A way to continuous improvement
- #30: Let’s look back at 5 years of this group and think about how to make it better. <optional>To start, I’d like to ask all of you to stand up. Now please have a seat if this is your first meeting Have a seat if this is your first year with the group Have a seat if this is 2nd or 3rd. Congratulations to our veterans! <optional> Stage: - 5 min ( 3 + 2 to report) Now I would like to ask you to self-organize around our veterans in the groups of x. In the groups lets’ take 5 Min and ask everyone to describe how they feel about this meeting so far. We will use Explorer/shopper/vacationer/prisoner framework. Let’s count the number of people in each category and report back to everyone. Gather data: 10 min. Let’s take 10 min to built the group timeline together. Think about number of people in the group, different locations, any significant events, key initiative or speakers. Now use the color coding label to indicate your felling's about these milestones on the timeline. Debrief all together– 5 min Looking at the data that we collected, lets take 12 min and use the 4 hats to brainstorm on Appreciation, Puzzles, Risks and Wishes. I would like to ask each team to share with the rest of us top 2 in each category. ( 10 min ) Action items . What are some of the action items from each team? let’s vote with the show of hands which items we would like to action on as a group. ( you can only vote twice) Who would like to take ownership on this? In the last few minutes, I’d like to thank all of you for our active participation – this retrospective and this group would not have been the same without each of you! Please give yourself a round of applause.