high performing-distributed-teams
TRANSCRIPT
High Performing Distributed Teams
Debunking the Agile myth that it can’t work
1 Scrum Team
Many Scrum Teams
Agile Team Structure
Time for a Quick Story
Once upon a time, there was a team of individuals
who interacted daily. They found the most efficient
and effective method of conveying information is face-
to-face conversation.
They lived together in one place and they called it…
Pangea
Everyone was happy.
Transparency
Collaboration
Trust
Then one day they noticed everything had changed…
Everyone was
Agile clearly won’t work here
of Agile
Why do companies have distributed teams?
Shout Out Your Answer!
Let’s Look at Some Sample Teams
-2.5 hours
-11.5 hours-13.5 hours
Sample #1Remote Team Member
Dependencies Across Teams
Takeaways
• Create a virtual team room to foster communication throughout the day
• Investment in travel opens communication channels
• Host Scrum of Scrums using video to address inter-team dependencies and alignment
• Keeping teams co-located within an office helps team cohesion
-1.5 hours
Sample #2Remote Product OwnerRemote Team Member
Remote Manager
Distributed Retrospectives
Takeaways
• Invest in network infrastructure to support richer communications
• Online collaborative tools make retrospectives and planning more effective and fun
• When most of the team is remote, make periodic trips to see them
-6 hours
Sample #3Remote Scrum Master
2 Remote Team Members
-7 hours
Takeaways
• Continue working with trusted people that want to live elsewhere
• Remote pair programming is a great way to allow two people to work together across locations
Sample #4Split Teams
Takeaways
• When verbal communication is too cumbersome, supplement with written communication
• Working agreements are crucial when work-life balance is impacted
• Identify and train a proxy for the remote office
• Arrange for early travel to start knowledge transfer and create ongoing plan
Sample #5Telecommuting Team
Takeaways
• Telecommuting cuts down on travel time and can allow for greater focus
• Online presence allows for timely communication and accountability
• Creative use of co-working space allows the team to bond regularly
Common Themes
Strength of Relationships • How well do the members of the team know each other?• How well do they get along?• Have they worked together on assignments?
Timezone Distance • How many overlapping hours are there during the day?• Do overlapping hours cause one or both parties to sacrifice
personal time or present a hardship (too early; too late; weekend overlap)
Communication • How much do the individuals on the team rely on each other?• If they are different teams, how often do they integrate?• How often do the people need to interact to be effective?
Transparency and Feedback Loops
• What kind of information is available online?• Is the work represented there? Do you know what others are
working on?• Is code checked in frequently?• Do people ever duplicate each other's work?• Do people know each others' schedules?
Dependency • How much do the individuals on the team rely on each other?• If they are different teams, how often do they integrate?• How often do the people need to interact to be effective?
Evaluation Criteria
-2.5 hours
-11.5 hours-13.5 hours
Sample #1Remote Team Member
Dependencies Across Teams
Before
-2.5 hours
-11.5 hours-13.5 hours
Sample #1Remote Team Member
Dependencies Across Teams
After
What’s Possible to Improve?
Measure Success Against Objectives
*evaluate periodically
Team Owns the Problem Provide The Team What They Need
Can a Distributed Team be Agile?
The Future
According to Forrester 34 million Americans work from home. This number is expected to reach a staggering 63 million or 43% of the US workforce by 2016.
Teleworkers are 50% more productive than their office bound counterparts.
By 2020 more than 40% of the American workforce or 60 million people will be freelancers, contractors and temp workers (Intuit).
?
??
?
?
?
?
?
??
