Communicating and collaborating how distributed teams can thrive - kilby-horowitz
•Download as PPTX, PDF•
0 likes•247 views
This document discusses strategies for effective communication and collaboration in distributed teams. It begins by outlining the principles of agile methodology as they relate to distributed teams. It then describes three types of distributed team structures - satellite, cluster, and nebula. The document proposes several techniques for distributed teams, including assigning "buddies" for remote members, using backchannel communication like chat, and designating team members as "co-pilots" to facilitate coordination. It presents an exercise called the "marshmallow challenge" that guides teams through collaboratively building a structure and includes debrief questions. The document concludes by providing contact information for the authors.
Recommended
More Related Content
Viewers also liked
Viewers also liked (16)
Similar to Communicating and collaborating how distributed teams can thrive - kilby-horowitz
Similar to Communicating and collaborating how distributed teams can thrive - kilby-horowitz (7)
More from Mark Kilby
More from Mark Kilby (10)
Recently uploaded
Recently uploaded (20)
Communicating and collaborating how distributed teams can thrive - kilby-horowitz
- 1. Communicating and Collaborating: How Distributed Teams can Thrive Mark Kilby David Horowitz Please fill tables to left
- 2. Observations - agile and distributed teams Source: www.agilemanifesto.org
- 3. Observations - agile and distributed teams Source: www.agilemanifesto.org Too much focus
- 4. Observations - agile and distributed teams Source: www.agilemanifesto.org We forget about
- 5. Satisfy the Customer Welcome Change Deliver Frequently Collaborate Daily Support & Trust Motivated Teams Promote Face-to-Face Conversations Measured by Working Software Promote Sustainable Pace Promote Technical Excellence Maximize Through Simplicity Have Self-Organized Teams Reflect & Adjust Regularly Source: www.agilemanifesto.org ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Observations - agile and distributed teams
- 6. Satisfy the Customer Welcome Change Deliver Frequently Collaborate Daily Support & Trust Motivated Teams Promote Face-to-Face Conversations Measured by Working Software Promote Sustainable Pace Promote Technical Excellence Maximize Through Simplicity Have Self-Organized Teams Reflect & Adjust Regularly Source: www.agilemanifesto.org ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Most assume there is only one way Observations - agile and distributed teams
- 7. Satisfy the Customer Welcome Change Deliver Frequently Collaborate Daily Support & Trust Motivated Teams Promote Face-to-Face Conversations Measured by Working Software Promote Sustainable Pace Promote Technical Excellence Maximize Through Simplicity Have Self-Organized Teams Reflect & Adjust Regularly Source: www.agilemanifesto.org ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Consider this principle as Promote Connection Observations - agile and distributed teams
- 8. 3 Types of Distributed Teams (simple) Satellite (one or a few remote from team) Clusters (team is in groups in a few locations) Nebula (whole team dispersed) / @mkilbymore info at http://remotelyagile.info
- 9. Buddy System - each remote person has a “buddy” in the room to make sure they are connected to the team (paired communication) Consider SAFETY on distributed communication Back Channel - always have all hailing frequencies open (chat); someone should always monitor Co-Pilot – someone at another location that can help you coordinate the whole team (paired facilitation) more info at http://remotelyagile.info / @mkilby
- 10. Let’s try it
- 12. 1 1/29/2017 GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource Adapted form http://marshmallowchallenge.com
- 13. 1 1/29/2017 Adapted form http://marshmallowchallenge.com DISTRIBUTED PART 1 - MISSION PREP (10 min) as SATELLITE, CLUSTER or NEBULA team PART 2 – BUILD MISSION! (9 min) Mission Safety Check (3 min) PART 2 – (continued) (9 min) PART 3 – DEBRIEF (35 min) GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource
- 14. 1 1/29/2017 Adapted form http://marshmallowchallenge.com DISTRIBUTED PART 1 - MISSION PREP (10 min) as SATELLITE, CLUSTER or NEBULA team PART 2 – BUILD MISSION! (9 min) Mission Safety Check (3 mins) PART 2 – (continued) (9 min) PART 3 – DEBRIEF (35 min) GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource
- 15. 1 1/29/2017 Adapted form http://marshmallowchallenge.com DISTRIBUTED PART 1 - MISSION PREP (10 min) as SATELLITE, CLUSTER or NEBULA team PART 2 – BUILD MISSION! (9 min) Mission Safety Check (3 mins) PART 2 – (continued) (9 min) PART 3 – DEBRIEF (35 min) GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource
- 16. 1 1/29/2017 Adapted form http://marshmallowchallenge.com DISTRIBUTED PART 1 - MISSION PREP (10 min) as SATELLITE, CLUSTER or NEBULA team PART 2 – BUILD MISSION! (9 min) Mission Safety Check (3 min) PART 2 – (continued) (9 min) PART 3 – DEBRIEF (35 min) GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource
- 17. Buddy System - each remote person has a “buddy” in the room to make sure they are connected to the team (paired communication) Consider SAFETY on distributed communication Back Channel - always have all hailing frequencies open (chat); someone should always monitor Co-Pilot – someone at another location that can help you coordinate the whole team (paired facilitation)
- 18. 1 1/29/2017 Adapted form http://marshmallowchallenge.com DISTRIBUTED PART 1 - MISSION PREP (10 min) as SATELLITE, CLUSTER or NEBULA team PART 2 – BUILD MISSION! (9 min) Mission Safety Check (3 mins) PART 2 – (continued) (9 min) PART 3 – DEBRIEF (35 min) GOAL: Build tallest free-standing structure 1. Entire marshmallow on top 2. Use as much or as little of other materials as you want 3. Free to break, cut, or modify everything except the marshmallow 4. Scissors are a shared resource
- 20. What impact did tools have? What was the impact of your build strategy? Did you adapt it? How did safety procedures work? Mission Debrief What was surprising or helpful?
- 21. Mark Kilby mark@markilby.com more info at http://remotelyagile.info @mkilby Questions? David Horowitz david@retrium.com http://retrium.com @ds_horowitz
Editor's Notes
- Mention close.io using snapchat to promote personal relationships in a remote company. “On a daily basis we use HipChat, Mumble, Zoom, Skype, Gmail, and KnowYourCompany as our main platforms for communication. While these feature rich tools get the job done, they don’t offer much when it comes to bringing us closer together in a more personal way. Instead, we found this in Snapchat. It gives us a more fun and personal way to stay connected and create a team culture that’s not only centered around work, but also life outside it. It allows us to build better relationships between each other not only as a team, but also as individuals.”
- Who has done the marshmallow challenge?
- 9 min – Part 1 9 min – Part 2a 3 min – Safety Check 9 min – Part 2b 30 min TOTAL
- Communications – disperse as far possible or use headphones
- Debrief questions at tables
- Worked with agile software teams since 2003 (over 115 as of 4/2016). 30% of my teams were distributed in some way