4 ms·
Yep, what the author fails to account for is that even locally run projects have a chance of complete failure, and huge budget overruns. It isn't that outsourci
by grogers 16y ago
Yep, what the author fails to account for is that even locally run projects have a chance of complete failure, and huge budget overruns. It isn't that outsourcing created the problem, poor project management likely created the problem - and it exists regardless of whether your developers are on- or off-site.
- JoeAltmaier 16y agoBut, when they are "offsite" PLUS speak a different language, PLUS have a different work culture PLUS have different cultural expectations about feedback (won't correct the boss even when they're wrong) PLUS massive timezone issues PLUS import/export restrictions PLUS network issues, then perhaps the probability of failure just might be affected a teensy bit?
- mseebach 16y agoYeah, there are challenges, and yes, the risk is higher -- I don't try to pretend otherwise. But those challenges can be addressed if you're aware of them. Writing off outsourcing all together is pretty narrow-minded.
- JangoSteve 16y agoI work constantly on projects with developers across the seas. I very rarely experience any issues with language, culture, feedback, timezone, network, etc. The difference is in management and due-diligence when choosing the developers. Every developer I work with overseas is someone who has come highly recommended or with whom I've worked on a project in the past. And that is a great way to do things, whether working with overseas developers or local.
- nl 16y agoExactly. To quote "Nearly 50% of outsourced projects fail outright, or fail to meet expectations". Compare that to "68% of companies are more likely to have a marginal project or outright failure" http://www.zdnet.com/blog/projectfailures/study-68-percent-of-it-projects-fail/1175 http://www.zdnet.com/blog/projectfailures/study-68-percent-o... In that light, outsourcing actually looks pretty good.