Downloaded 28 times
Uploaded byFabian Kiss
Collocation in Distributed Scrum Teams - Lessons Learned
The document discusses the challenges and best practices of colocation in distributed Scrum teams, emphasizing the importance of face-to-face communication for effective information exchange. It highlights the distinction between 'distributed Scrum' and 'remote Scrum,' advocating for occasional colocation to enhance collaboration. Key lessons learned include promoting awareness of distributed Scrum and avoiding isolated remote work practices to improve team perception and functionality.
More Related Content
Similar to Collocation in Distributed Scrum Teams - Lessons Learned
![[Thang nguyen] Best practices for Agile dispered team](https://cdn.slidesharecdn.com/ss_thumbnails/thangnguyen-bestpracticesforagiledisperedteam-150520014341-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
Collocation in Distributed Scrum Teams - Lessons Learned
- 1. Colocation in DistributedScrum Teams Lessons Learned Picturebydhaun,licensedundertheCCBY2.0
- 2. About me Agilist for5+ years in the roles of developer and Agile/Scrum Master Senior Software Engineer / Agile Evangelist @ YMC AG Kreuzlingen, Switzerland Fabian Kiss Twitter: @head_revision
- 3. Definitions Distributed Scrum Scrum Teamsin different locations distributed Scrum Team distributed team members Distributed Scrum Team distributed Scrum Team or team per location or mix of both
- 4. Types of DistributedScrum by Jeff Sutherland et al., Distributed Scrum: Agile Project Management with Outsourced Development Teams, 2006
- 5. Levels of distribution byElizabeth Woodward, Steffan Surdek, Matthew Ganis, Distributed Scrum: Agile Project Management with Outsourced Development Teams, IBM Press, 2010
- 6. Colocation In general: asmuch colocation as possible « The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. » 6th principle from the Agile Manifesto
- 7. Colocation Recommendation: occasional colocationin Distributed Scrum Danger: PicturebyUSFWS/Southeast,licensedundertheCCBY2.0
- 8.
- 9. Colocation Recommendation: occasional colocationin Distributed Scrum Danger: of distributed Scrum Team (= of team members who are distributed otherwise) PicturebyUSFWS/Southeast,licensedundertheCCBY2.0
- 10.
- 11. Scrum setup originally: “classic”Scrum 1 location 3 Scrum Teams Distributed Scrum 2 locations (on-site / off-site) 3 distributed Scrum Teams transformation PicturebySamHowzit,licensedundertheCCBY2.0
- 12. Types of DistributedScrum by Jeff Sutherland et al., Distributed Scrum: Agile Project Management with Outsourced Development Teams, 2006
- 13. Levels of distribution byElizabeth Woodward, Steffan Surdek, Matthew Ganis, Distributed Scrum: Agile Project Management with Outsourced Development Teams, IBM Press, 2010
- 14. Scrum setup Characteristics Disparity: ProductOwner / Project stakeholders on-site Small distance: Metropolitan area of Zürich PicturebyPeriColeman,licensedaspublicdomain
- 15. Best Practices Best Practice:on-site colocation of all team members for important Scrum Events Sprint Planning, Review, Retro
- 16.
- 17. Best Practices Problem: vastpart of Distributed Scrum references implicates certain motives
- 18. Best Practices Neglected: DistributedScrum within regional boundaries
- 19. more Best Practices? Discoverthem by your own!
- 20. Observations occasional colocation newchallenge: different (self-)perception Distributed Scrum vs. “Remote Scrum”
- 21. Distributed Scrum vs.Remote Scrum Distributed Scrum Remote Scrum a distributed team with occasional colocation of all team members a colocated team with occasional remote work by certain team members possibly caused by... fewer “colocated days” than “distributed days” regularity of colocated days
- 22. Distributed Scrum vs.Remote Scrum Due to perception “Remote Scrum”: recurring impediments, identified after several Sprints
- 23. Impediment #1 off-site location only “exists” duringremote work Remote Scrum Distributed Scrum
- 24. Impediment #2 off-site location isnot likewise equipped Remote Scrum Distributed Scrum
- 25. Impediment #3 only face-to-face communication Remote ScrumDistributed Scrum
- 26. Lessons Learned prevent perception“Remote Scrum” by establishing a team+organization-wide awareness of Distributed Scrum from scratch
- 27. Lessons Learned refer toDistributed Scrum (instead of only Scrum) whenever possible avoid the term “remote”
- 28. Lessons Learned do notsuccessively add isolated practices for remote work to your classic Scrum example:VC tool for face-to-face communication vs.VC tool for team communication
- 29. Lessons Learned consider toabandon colocation at the beginning to make the change to Distributed Scrum more noticeable
- 30. « At scale,all agile development is distributed development. » Dean Leffingwell in Scaling Software Agility: Best Practices for Large Enterprises