Top Reasons for Offshore Failure: Poor Communication
November 25, 2007 This is the first in a series of posts detailing the reasons for offshore outsourcing failures. The focus is on offshore product development, though many of the points are relevant to offshore IT outsourcing also.
Poor communication is THE biggest reason for failure in an offshore software development project. Even projects developmed in-house are susceptible to mis-communication. Since nearly 50% of offshore projects end in failure, it's critical to establish daily (if not more) communication with your offshore team. Since you're dealing with a host of cultural, technical, and interpersonal issues, daily communication is a must.
Also, most development is highly iterative, especially when using an agile software development methodology. Offshore product development is an entirely different beast than IT outsourcing with its quaint and manicured SLA's. Software development is dirty work and there's a lot of room for error. You need to invest time in communicating with your team and they need to be prepared to do the same.
Reader Comments (1)
It is surprising but a lot of companies miss on the communication part. It should be obvious that constant communication is key to success yet a lot of companies like to think it is automatic and it should work without much input. No wonder 50% offshore engagements end up in a failure.