>5) Around-the-clock development. The reason outsourcing is effective is not because it's cheaper (it's only marginally), not because they're better (they're th

>5) Around-the-clock development. The reason outsourcing is effective is not because it's cheaper (it's only marginally), not because they're better (they're the same as us), it's because you can do around-the-clock development. They check in code at 6 AM your time, you check in code at 6 AM their time. That's how you get ahead. If you simply transfer a single development team to a different time-zone, all you bought yourself is a 20-30% cost savings and a bunch of frequent flier miles. I'm highly curious on how this executes well in a high control environment. I've only seen this work at all well in very very loosely coupled codebases with huge amounts of responsibility division, and even that said, the technical and project leads seemed fully utilized handling the two teams. Care to share the howto on this?