• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Distributed Retrospectives
 

Distributed Retrospectives

on

  • 2,695 views

Distributed Retrospectives talk done for Agile Brazil, June 2011.

Distributed Retrospectives talk done for Agile Brazil, June 2011.

Statistics

Views

Total Views
2,695
Views on SlideShare
2,694
Embed Views
1

Actions

Likes
5
Downloads
0
Comments
1

1 Embed 1

https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi - I've been working on a online web application to help teams run distributed agile retrospective activities - GroupMap http://www.groupmap.com/agile-retrospectives . We'd appreciate your thoughts or if you'd like to give it a try. Thanks
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • AntipatternsOur focus is to help you envision the first beta of the business concept as quickly as you can and then understand what it will take to get the software into liveWe’ll bring our experience designers, business analysts and technicians together to help you envision the concept in 1-3 weeksWe call this EnvisioningWe’ll then bring this team plus project managers and QA in to do some technical spiking, some lightweight design and to estimate the first releaseWe call this an InceptionWe will integrate the experience designers with the delivery teams to continuously design, get feedback through showcases, multi-variant testing etc. and continuously improve the product being delivered- We call this Continuous DesignAnd we combine the holistic agile delivery – both at the project management level (utilising techniques such as Scrum) and at the practitioner level (utilising techniques such as Extreme Programming) – with the newer “last mile” techniques coming out of the DevOps movement to get high quality software into production as quickly as possibleWe call this Continuous DeliveryWhen you combine the Continuous Design with the Continuous Delivery you enable completely new possibilities for business people. Avoiding spending months trying to think through how to “get it right” but getting something out there quickly, starting to derive some value, adapting to customer needs and reactions and continuously improving to deliver more and more benefit as you evolve.
  • Why distributed? How does this happen?
  • My craziest distributed project?
  • My craziest distributed project?
  • Why distributed? How does this happen?
  • Why distributed? How does this happen?
  • AntipatternsOur focus is to help you envision the first beta of the business concept as quickly as you can and then understand what it will take to get the software into liveWe’ll bring our experience designers, business analysts and technicians together to help you envision the concept in 1-3 weeksWe call this EnvisioningWe’ll then bring this team plus project managers and QA in to do some technical spiking, some lightweight design and to estimate the first releaseWe call this an InceptionWe will integrate the experience designers with the delivery teams to continuously design, get feedback through showcases, multi-variant testing etc. and continuously improve the product being delivered- We call this Continuous DesignAnd we combine the holistic agile delivery – both at the project management level (utilising techniques such as Scrum) and at the practitioner level (utilising techniques such as Extreme Programming) – with the newer “last mile” techniques coming out of the DevOps movement to get high quality software into production as quickly as possibleWe call this Continuous DeliveryWhen you combine the Continuous Design with the Continuous Delivery you enable completely new possibilities for business people. Avoiding spending months trying to think through how to “get it right” but getting something out there quickly, starting to derive some value, adapting to customer needs and reactions and continuously improving to deliver more and more benefit as you evolve.
  • My craziest distributed project?
  • My craziest distributed project?
  • My craziest distributed project?
  • Collaborative Tools
  • Collaborative Tools
  • Collaborative Tools

Distributed Retrospectives Distributed Retrospectives Presentation Transcript

  • Distributed Retrospectives
  • Today’s Objectives…
    Learn about Distributed Retrospectives
    Learn about team structure and location in planning
    Learn strategies for setting up a distributed retrospective
    Learn about various activities and tools
    Plan a Distributed Retrospective
  • About the Speaker…
  • My craziest retrospective?
  • Questions?
    Who has facilitated a retrospective before?
    Who has been involved in a distributed retrospective?
  • Why Distributed?
    Economical
    Location of people
    Regions specialize in skill areas
    Easier for people to collaborate from a distance
    Diverse teams
  • Why do Retrospectives?
    Regardless of where people are, they are still part of the team.
    Regardless of where people are, the team still needs to communicate.
    Retrospectives make teams better.
    Resolve issues.
  • Dos
    Understand your audience
    Trust your team
    Use technology
    See each other
    Be creative
    Communicate
  • Common Problems
    One group dominates
    Location specific issues
    Ignore content
    Distribution amplifies problems
  • Cultural Factors
    When teams are split geographically, they are often also split culturally and this split can manifest itself in many ways.  
  • For Example…
  • Cultural Disconnect…
  • Team A: Before Retrospective
    Sent materials ahead of time
    Sent activities ahead of time
    Team practiced what to say
    Explained situation
  • Team A: During Retrospective
    Picked a scribe
    Encouraged equal participation
    Use of video
    Used technology to gather thoughts and views
    Had two facilitators
  • Team A: After Retrospective
    Send out notes and set up time to clarify
    Set up video feed
    Moved documentation online
    Set up more retrospectives
  • Three Key Areas
    What is done before the retrospective: preparation.
    What is done during the retrospective.
    What is done after the retrospective.
  • Three Key Areas
    What is done before the retrospective: preparation.
    What is done during the retrospective.
    What is done after the retrospective.
  • Part 1: Preparation for a Distributed Retrospective
  • What is the Objective?
    What are you trying to achieve?
  • What is the Team Structure?
    How you run a distributed retrospective depends on where the team is located and how the team is structured. For example…
    Two large teams separated geographically
    One large team and a individual stragglers
    A fully distributed team (everyone works in different locations)
    Numerous smaller teams
  • Where is your team located?
    You also need to consider the location of the team. For example…
    Located in the same country
    Located in different countries
    People in different time zones
    People speaking multiple languages
  • Possible Strategies… One Group Retro
    The whole team is involved in the retrospective.
  • Possible Strategies… Separate
    Have two independent retrospectives and have a short “sharing” retrospective.
    Divide and conquer
  • Possible Strategies… Parallel
    A facilitator in each location runs the retrospective in parallel (with video on and microphone muted).
    At points the two teams synch to compare findings.
  • Possible Strategies…Time-Boxed
    Plan short activities.
    Time box the activities to keep the team focused.
  • Possible Strategies… Issue Triggered
    What if the team considered not having retrospectives at a dedicated time (e.g. at the end of each iteration)?
    Run an issue triggered retrospective.
  • The Activity
  • Activity: Before the Retrospective
    You are going to plan and prepare for a distributed retrospective. This is Part 1.
  • Part 1: Instructions
    Break into groups of 8 people.
    Choose which of the 5 scenarios you would like to do.
    Determine the objective of your chosen retrospective.
    Determine the strategy you would like to use (or create one!)
    Determine logistics you will need to plan for.
    You have 30 minutes.
  • Part 2: Activities and Mechanics
  • Supporting the Objective
    What are some of the objectives for the retrospectives in the room?
  • Traditional Activities
  • Art Gallery
  • Photo Sharing
  • Photoshop Ping Pong/Tennis
  • Three Color Vote
  • Appreciative Exercise
  • Online Games
  • Tools and Mechanics: Online Games
    For activities that require card gathering (e.g. helps/hinders, anchors/balloons, hopes/fears, and moving forward) you can use online tools.
  • Twiddla (twiddla.com)
  • Innovation Games (innovationgames.com)
  • Card Meeting (cardmeeting.com)
  • Edistorm (edistorm.com)
  • Cacoo (cacoo.com)
  • Tools and Mechanics: Video
    How are you going to communicate during the retrospective?
  • Video
  • Skype
  • Google Video
  • ooVoo
  • Vidyo
  • Capturing Ideas
  • Tools and Mechanics: Capturing Ideas
    For capturing information during the retrospective.
  • Webex (webex.com)
  • Google Docs (google.com)
  • Basecamp (basecamphq.com)
  • Mind Meister (mindmeister.com)
  • Bubbl.us (bubbl.us)
  • Activity: During the Retrospective
    You are going to plan activities and logistics that support the objective and team. This is Part 2.
  • Part 2: Instructions
    Determine activities that support your objective?
    Determine what materials you can send ahead of time.
    Determine how to communicate.
    Determine how to capture information during the retrospective. Who is the scribe?
    You have 30 minutes.
  • Part 3: Sharing
  • Activity: Sharing the Retrospective
    Share your retrospective and learnings with the people in the room.
    You have 2-minutes to prepare what to say and who will say it.
    Each team will present to the group.