More Thoughts on Distributed Development

Thursday, February 21, 2008 – 8:42 AM

I. M. Wright’s (aka Eric Brechner, Director of Development Excellence at Microsoft) had an interesting post this month. It’s about the big, bad ‘B’s of distributed development—bandwidth, boundaries, and being there.

I thought one of his key points was it’s not about cutting costs, it’s about increasing available talent. Costs will eventually converge but the World’s best talent isn’t always where you are.

Many of the same ideas come up here as I covered in my previous posts which reflected both p&p’s experiences and that of other practitioner’s within the industry (including references):

Choosing an agile process – Part 4a: Offshore development
Choosing an agile process – Part 4: Offshore development

Another thing I’ve heard recently is that “time differences hurt more than distance”. I think this ties in with my experience. 4000 miles North-South (1-3 hour difference) is easier to deal with than the same thing East-West (8 or more hours).

Of course all this begs the question… Why do we still run projects counter to these best practices?

Technorati Tags: ,,,

  1. 4 Responses to “More Thoughts on Distributed Development”

  2. Thanks for sharing this informative post. Good article.

    By Offshore Web Development on Jun 18, 2009

  1. 3 Trackback(s)

  2. Mar 3, 2008: #2782 » Blog Archive » The "High" Cost of Talent?
  3. May 14, 2008: #2782 » Blog Archive » Distributed Development - part 4
  4. Aug 6, 2008: Agile 2008 - Distributed Agile | #2782 - Agile software development and best practices for building Microsoft .NET applications.

Sorry, comments for this entry are closed at this time.