Outsourcing

Also known as offshoring (but there is a difference, of course).
The roadrunner has second thougths, as he almost always has: seeing brown bears.

But still, see for instance (and is the internet reliable?):
http://en.wikipedia.org/wiki/Outsourcing#Criticisms_of_outsourcing
http://www.mytino.com/tinopedia/detail.php?TinoPedia_ID=111
"Here are 10 common reasons not to outsource and the simple answers to overcome each obstacle."
http://www.artofmoney.org/10-reasons-why-i-wont-outsource/
Just another copy?
http://pragmaticoutsourcing.com/2009/01/22/top-10-reasons-not-to-outsource/
"If your organization is process free or still straggling to achieve CMM1 inviting outsourcing is likely to cost you an arm and a leg, so stay away from offshore, unless of course you’ve got spares."

It's good to be critical and to tick off the highest risks to not burn your ships before you can rely on foreign ships ...
It is far better to have one bird in ones hand then see ten birds flying away in the sky.
This is not to be confused with being reluctant to change:


If the only main reason to out/offshore is to save money on what is your core business, creating software, better think twice.
Core business given to third party!
This does not sound as a wise decision!

Certainly if this software is not bespoken work but an application to be delivered to numberous local customers.
Outsourcing could very well be the fastest way to lose your (key) accounts.
The golden rule applies also here:
do nothing without consulting your stakeholders, the companies using your software:
never forget your stakeholders!



Because they pay your way of life.
And they have their habbits and they think they know yours.
It is always a good idea to level with them.
Not after you made the decison to outsource, but of course let them get used to that idea.
At least, if they embrace that idea.
Else: NO WAY!