How Do You Maintain Long-Distance Projects?

overseer asks: "Recently, I've been working with an increasing number of overseas workers. Regardless of where they are located, or how well they are trained, the common problem that we have is communication across timezones. In a typical 9-6:30 day, none of my working hours overlaps with those of my coworkers in Europe and Asia. If I come in early, or stay late, I can call one or the other but the truth of the matter is that most of my communication is done through email, and results in (at best) a 15 hour turnaround time for even the smallest question. This is OK for large, slow moving projects, but when we are working on 'Now' problems, or doing detail work, it makes it very hard to communicate. It also makes casual communication or constructive feedback next to impossible. Several of my coworkers have adapted by working extended hours, or by taking their work home with them -- this is something that I'd like to avoid. What methods have Slashdot readers found/created to get around the problem of working in multiple timezones?"

Comments

Step #1

[RingDev]

Don't outsource overseas when timing and collaboration are a primary concern. In the world of in house custom app development, any money saved on over seas outsourcing labor will be lost in delays, communication break downs, and lack of understanding. Not saying that developers overseas are worse, just that when you are rebuilding an invoicing system it is much easier if you can talk to the accounting/leasing departments directly and they can tell you immediately if something breaks.

-Rick