OPINION

The Lead Developer is the Wrench in the Works of Outsourcing

Written by Heartcrossings
Published April 15, 2006

Though its well-known, acknowledged old news, every once in a while the "real" cost savings from outsourcing makes headlines. That it may take "research" to derive the obvious, common sense, conclusion is quite baffling.

This research proves that the promise of massive operational savings is unrealistic when you take into account the costs of procurement and ongoing contract management.

One small detail that researchers don't seem to uncover is the role that fear of unemployment plays. Most places I have consulted typically have a local resource that acts as the lead developer and designer - the number of such resources is proportional to the size, "presumed complexity," and budget of the project. More often than not, these individuals act as a major bottleneck in the process and play havoc with planned expenses.

The typical lead developer/designer (from my experience) has not had an opportunity to keep up with latest technology because they were too busy trying to keep their jobs. The technology skills they have are at least ten years too old and will not be any use to them once they lose their current job. It does not help that they are in their late 30s, sometimes early 40s - the twilight zone of a development career in IT.

Their modus operandi on outsourced projects is to provide minimal information upfront to the team offsite and zero oversight through the development and testing cycles. When at last all is done, they begin complaining bitterly about the abominable end product that they now have to work overtime to fix and render acceptable.

I have heard the line "The offshore code sucks so bad that it needs a full re-write" more times than I remember. Clueless middle management does not recognize that code cutting is not rocket science and that, if the lead developer/designer had done their job, code would be the least of anyone's concerns. Instead, they have this person work overtime to "fix" what should not have been broken to begin with. Not once does anyone question why they had not anticipated the extent of damage until the final product was delivered. Is that not their role ?

After all is said and done, everyone bemoans the lack of savings from the deal, powers-that-be proceed to switch vendors to remediate the situation and researchers write up thesis on the failed promises of outsourcing. In failing to take the human element of the problem into account, everyone gets it wrong and we as consumers pay for expensive mistakes.

Keep reading for information and comments on this article, and add some feedback of your own!
The Lead Developer is the Wrench in the Works of Outsourcing
Published: April 15, 2006
Type: Opinion
Section: Sci/Tech
Writer: Heartcrossings
Heartcrossings's BC Writer page
Heartcrossings's personal site
Spread the Word
Like this article?
Email this
Submit to del.icio.us Save to del.icio.us
RSS Feeds
All RSS Feeds (240+)
Comments on this article
BC articles by Heartcrossings
All Sci/Tech Articles
All Opinion articles
All BC articles
All BC Comments

Comments

Want comments emailed to you? No spam, promise! Address:

Add your comment, speak your mind

(Or ping: http://blogcritics.org/mt/tb/46415)

Personal attacks are not allowed. Please read our comment policy.





Remember Name/URL?

Please preview your comment!

Fresh
Articles
Fresh
Comments