Distributed vs. Colocated Teams - Isak Styf, LTG-4

1,437 views

Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

Distributed vs. Colocated Teams - Isak Styf, LTG-4

  1. 1. Distributed vs Collocated Scrum Why and how you might want to move from collocation to a dispersed development model Isak Styf, Scrum Master New Product Platform Development Group
  2. 2. Agenda <ul><li>Collocation IS better … </li></ul><ul><li>… except when it isn’t </li></ul><ul><li>What can go wrong? </li></ul><ul><li>There can be distinct advantages to distribution or dispersion! </li></ul><ul><li>Invest in this if you are going to do it </li></ul><ul><ul><li>A trusting and committed team without fear of conflict </li></ul></ul><ul><ul><li>Technical Infrastructure </li></ul></ul><ul><ul><li>Keeping communication flowing </li></ul></ul><ul><ul><li>Continuous improvement </li></ul></ul><ul><li>Reading Material </li></ul><ul><li>Summary </li></ul>
  3. 3. Collocation IS better… <ul><li>In “the agile sweet spot” </li></ul><ul><ul><li>Small team within eye sight of each other </li></ul></ul><ul><ul><li>Minimal dependency on external hard-to-get-hold-of expertise or domain knowledge </li></ul></ul><ul><ul><li>A single customer within reach </li></ul></ul><ul><ul><li>A product that is serving a single homogenous target market </li></ul></ul><ul><ul><li>Short project cycle </li></ul></ul><ul><li>This is Agile 101 and therefore the first thing we learn about how to do Scrum “right” </li></ul><ul><li>But honestly, is your project in this spot? </li></ul><ul><li>Do not force fit this model! </li></ul>
  4. 4. ...except when it isn’t <ul><li>” In an organization designed to serve several distinct markets, it is important to reflect the market structure in the development organization. One frequently overlooked opportunity for a powerful pattern is the conscious design of a &quot;core&quot; organization (framework team), that supports only what is common across all market segments.” Organization Follows Market – Jim Coplien </li></ul><ul><li>That’s Us! </li></ul>
  5. 5. What can go wrong? <ul><li>Lack of trust and buy-in from internal customers </li></ul><ul><ul><li>” Our needs have not been heard” </li></ul></ul><ul><ul><li>” They do not understand our market” </li></ul></ul><ul><ul><li>” We do not get to participate” </li></ul></ul><ul><ul><li>” This is not how we would have done it” </li></ul></ul><ul><ul><li>” Who did this to me!? We would be better off doing it ourselves!” </li></ul></ul><ul><li>Feedback flow is impeeded because there is no natural communication channel </li></ul><ul><li>We end up going really really fast, blindfolded, in the wrong direction! </li></ul>
  6. 6. Distributed advantages <ul><li>Customers can have face time with our developers to resolve issues in their own lingo </li></ul><ul><li>Our feedback response time is minimized </li></ul><ul><li>Our market specific open issues can be resolved quicker because we have people on site </li></ul><ul><li>Increased trust and shorter turnaround time reduces the need for traceability, accountability and up front design reviews </li></ul><ul><li>Not being collocated requires our teams to communicate more and not rely as much on tribal knowledge. This is an advantage! </li></ul>
  7. 7. Invest in this <ul><li>Building a trusting and committed team without fear of conflict </li></ul><ul><li>Technical Infrastructure </li></ul><ul><li>Keeping communication flowing </li></ul><ul><li>Continuous improvement of the development process </li></ul>
  8. 8. Building a distributed team <ul><li>The first three of the five dysfunctions are extra important in a distributed setting </li></ul><ul><ul><li>Trust </li></ul></ul><ul><ul><ul><li>Needs touch! ”You will pay the cost of a face-to-face meeting regardless of whether you have one or not. Not having it may cost more.” - Pugh </li></ul></ul></ul><ul><ul><li>Fear of conflict </li></ul></ul><ul><ul><ul><li>Distance breeds misunderstandings. If your team is afraid of creating a conflict you will not get the value you want out of it! </li></ul></ul></ul><ul><ul><ul><li>Educate the team on cultural differences. </li></ul></ul></ul><ul><ul><ul><li>The Scrum Master must be proactive to seek out potential sources of conflict and deal with the situation before it escalates. </li></ul></ul></ul><ul><ul><li>Lack of commitment </li></ul></ul><ul><ul><ul><li>Does everyone know the vision and goal? Is everyone heading in the same direction? </li></ul></ul></ul>
  9. 9. Technical infrastructure <ul><li>Save your money somewhere else. Not on the technical infrastructure that the success of your distributed team is depending on! </li></ul><ul><li>Continuous integration build servers with build information radiators is an investment that you want to make as early as possible. </li></ul><ul><li>Make sure that the network bandwith is enough to handle video conferencing </li></ul><ul><li>High quality conference phone and headsets for peer to peer calls </li></ul>
  10. 10. Keep communication flowing <ul><li>Visual CI build boards in all team spaces </li></ul><ul><li>Group chat or instant messaging for quick status updates. ”I just broke the build. We should be back to green in 5 mins.” </li></ul><ul><li>Distribution is not an excuse for swim-laning! </li></ul><ul><ul><li>Consider WIP limits if this is a problem for you </li></ul></ul><ul><li>Pair Programming </li></ul><ul><li>Daily standups and cross team SoS via video </li></ul><ul><li>Expatriates regularly travel between sites </li></ul><ul><ul><li>Only traveling at project start is not enough! </li></ul></ul>
  11. 11. Continuous improvement <ul><li>” Success depends upon colleagues addressing communication constraints and barriers in a distributed setting.” – Jutta Eckstein </li></ul><ul><li>Use the retrospective to find ways to improve your communication. </li></ul><ul><li>List your (non human) impediments publically </li></ul><ul><li>Report on the impact from insufficient infrastructure </li></ul><ul><li>Use your metrics to visualize improvements </li></ul>
  12. 12. Reading Material <ul><li>The 5 dysfunctions of a team, Patrick Lencioni </li></ul><ul><li>Agile Software Development with Distributed Teams, Jutta Eckstein </li></ul><ul><li>Practices for Scaling Lean & Agile Development, Craig Larman & Bas Vodde </li></ul><ul><li>Distributed Scrum Primer, Pete Deemer </li></ul>
  13. 13. Summary <ul><li>Collocation is not always the most efficient way of working when you factor in customer satisfaction. </li></ul><ul><li>If you are targeting diverse markets or internal customers you might have quite a lot to gain by distributing your team. </li></ul><ul><li>A very high coordination effort is required so make sure that your technical infrastructure and communication channels can support your teams. </li></ul><ul><li>Always inspect and adapt your process to make sure that it is improving. Focus especially on communication constraints. </li></ul><ul><li>If we can do it. So can you! </li></ul>
  14. 14. www.markem-imaje.com <ul><li>Thank you for your attention. </li></ul>

×