Outsourcing fail

We are currently feeling the pain of offshoring policy where I work, its good to know we're not alone. Here are some articles that make interesting reading on this topic

http://www.infoworld.com/d/adventures-in-it/painful-lessons-it-outsourcing-gone-bad-032?page=0,1

"The desire to save big bucks so blinded the executives that they didn't realize they were replacing a group of people experienced with using a product to a group of people who were looking at it for the first time. "We underestimated the loss of knowledge that would take place during the transition,""

This one is a short article with some very true points;
http://www.colosseumbuilders.com/wharton2004.htm

"But keep in mind lower paid programmers do not mean cheaper software development"

"Third, you have to specify down to the smallest detail. What you put down on paper is what you get. If companies created project specifications with enough detail to offshore to begin with, they wouldn't be having the problem of runaway project costs."

This article is more focused on dba's, but has many relevant points;
http://www.dba-oracle.com/n_2010_offshoring_oracle_disaster.htm

"Offshoring is re-shored back to America: A qualified coder can create system 20 times faster than a under-trained offshore developer, and many IT managers misunderstand that offshoring does not necessarily mean that the work is done in a low-cost country."

And someone asks can you do agile with an offshoring policy.
http://www.infoworld.com/d/adventures-in-it/agile-development-offshore-jobs-recipe-disaster-307
Answer is; don't do agile and offshoring


- Posted using BlogPress from my iPad

Location:UK