RE: What are the most important issues during offshore software development
| Newsgroups | gmane.comp.programming.language-of-the-year |
|---|---|
| Message-ID | <[email protected]> |
> On Thu, Jul 3, 2008 at 1:21 AM, shi lin <[email protected]> wrote: > > Yeah, there are some many successful offshore stories. > > And Enron was a "success story" once -- before it wasn't. :-) > Yup. Been there, done that, seen the disasters. > > That is why US or European companies outsourced their projects > > Companies outsource because it's cheaper. In the cases I'm personally > familiar with, the project owners simply didn't care that the end > product > was unmaintainable, barely-usable crap. > Mostly. More often the project owners were forced into it be boardrooms who didn't want to know. Offshoring was "kewl" and made you look "modern" because "everybody does it so it must be good". > Their only goal was to show their boss the project was done, check > it off, look good for the next performance/salary review. > The goal was usually to do it on the cheap, never mind the consequences as I'll no longer be managing the project after it enters maintenance. > Forgive me if I'm skeptical of all the white-paper "success stories"... > Nothing to forgive. While there are successes (I've seen them) those do NOT involve offshoring to Asia and only involve offshoring the mechanical work of turning highly detailed technical designs into code modules.