Collocation in Distributed Scrum Teams - Lessons Learned

2,309 views
2,140 views

Published on

In the case of a Distributed Scrum setup where your development locations are within close proximity, it is recommended that your distributed Scrum team is occasionally collocated. Though, it comes with the risk that team members misleadingly perceive their distributed team as a collocated team with occasional remote work by certain team members. In this context, YMC AG could gather some helpful Lessons Learned.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,309
On SlideShare
0
From Embeds
0
Number of Embeds
372
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Collocation in Distributed Scrum Teams - Lessons Learned

  1. 1. Colocation in Distributed Scrum TeamsLessons LearnedPicturebydhaun,licensedundertheCCBY2.0
  2. 2. About meAgilist for 5+ years in the roles of developer and Agile/Scrum MasterSenior Software Engineer / Agile Evangelist@ YMC AG Kreuzlingen, SwitzerlandFabian KissTwitter: @head_revision
  3. 3. DefinitionsDistributed ScrumScrum Teams in different locationsdistributed Scrum Teamdistributed team membersDistributed Scrum Teamdistributed Scrum Teamorteam per locationormix of both
  4. 4. Types of Distributed Scrumby Jeff Sutherland et al., Distributed Scrum: Agile Project Management with Outsourced Development Teams, 2006
  5. 5. Levels of distributionby Elizabeth Woodward, Steffan Surdek, Matthew Ganis, Distributed Scrum: Agile Project Management with Outsourced DevelopmentTeams, IBM Press, 2010
  6. 6. ColocationIn general: as much colocation as possible« The most efficient and effective method of conveying information to and within adevelopment team is face-to-face conversation. »6thprinciple from the Agile Manifesto
  7. 7. ColocationRecommendation: occasional colocation in Distributed ScrumDanger:PicturebyUSFWS/Southeast,licensedundertheCCBY2.0
  8. 8. What?
  9. 9. ColocationRecommendation: occasional colocation in Distributed ScrumDanger: of distributed Scrum Team(= of team members who are distributed otherwise)PicturebyUSFWS/Southeast,licensedundertheCCBY2.0
  10. 10. Why?
  11. 11. Scrum setuporiginally: “classic” Scrum1 location3 Scrum TeamsDistributed Scrum2 locations (on-site / off-site)3 distributed Scrum TeamstransformationPicturebySamHowzit,licensedundertheCCBY2.0
  12. 12. Types of Distributed Scrumby Jeff Sutherland et al., Distributed Scrum: Agile Project Management with Outsourced Development Teams, 2006
  13. 13. Levels of distributionby Elizabeth Woodward, Steffan Surdek, Matthew Ganis, Distributed Scrum: Agile Project Management with Outsourced DevelopmentTeams, IBM Press, 2010
  14. 14. Scrum setupCharacteristicsDisparity: Product Owner / Project stakeholders on-siteSmall distance: Metropolitan area of ZürichPicturebyPeriColeman,licensedaspublicdomain
  15. 15. Best PracticesBest Practice: on-site colocation of all team members for important Scrum EventsSprint Planning, Review, Retro
  16. 16. more Best Practices?
  17. 17. Best PracticesProblem: vast part of Distributed Scrum references implicates certain motives
  18. 18. Best PracticesNeglected: Distributed Scrum within regional boundaries
  19. 19. more Best Practices?Discover them by your own!
  20. 20. Observationsoccasional colocation new challenge: different (self-)perceptionDistributed Scrumvs.“Remote Scrum”
  21. 21. Distributed Scrum vs. Remote ScrumDistributed Scrum Remote Scruma distributed team with occasionalcolocation of all team membersa colocated team with occasional remotework by certain team memberspossibly caused by...fewer “colocated days” than “distributeddays”regularity of colocated days
  22. 22. Distributed Scrum vs. Remote ScrumDue to perception “Remote Scrum”: recurring impediments, identified after several Sprints
  23. 23. Impediment #1off-sitelocation only“exists”during remoteworkRemote Scrum Distributed Scrum
  24. 24. Impediment #2off-sitelocation is notlikewiseequippedRemote Scrum Distributed Scrum
  25. 25. Impediment #3onlyface-to-facecommunicationRemote Scrum Distributed Scrum
  26. 26. Lessons Learnedprevent perception “Remote Scrum”byestablishing a team+organization-wide awareness of Distributed Scrum from scratch
  27. 27. Lessons Learnedrefer to Distributed Scrum (instead of only Scrum)whenever possibleavoid the term “remote”
  28. 28. Lessons Learneddo not successively add isolated practices for remotework to your classic Scrumexample:VC tool for face-to-face communicationvs.VC tool for team communication
  29. 29. Lessons Learnedconsider to abandon colocation at the beginning to makethe change to Distributed Scrum more noticeable
  30. 30. « At scale, all agile development is distributed development. »Dean Leffingwell in Scaling Software Agility: Best Practices for Large Enterprises

×