Key Success Factors for Distributed Software Development Teams

Here’s one with more to follow in coming days.

What’s good for software development in general also builds great teams, collocated -and distributed. Take pairing, continuous builds and code reviews just to name a few. Don’t you want to know the technical and domain knowledge of your team members? Why should the fact that they aren’t physically next to or near to you make a difference? With remote collaboration tools (many free ones at that) giving you access to output (code, database and other artifacts) and to frequent daily/intra-daily voice interaction, you now have the ability (+/- time zone differences) to continually monitor and steer quality and requirement synchronicity. My suggestion. “Master” your SD practices with your current physically located team first, then you’ll know exactly how to direct distributed team members.