RUP UP! What Part Of Software Development is Outsourcable?

Here's a rough (very) diagram of the four phases of the RUP: Inception, Elaboration, Construction, and Transition. I'm not writing a treatise on software development, so we'll just cover each phase and ask a couple questions at the end. If you phrase the phases in terms of questions, here's a Cliff's Notes on what they're all about:
Inception: What are we doing? Can we afford it? Does it affect our architecture/business model? Do we have agreement on what it is and how to fix it?
Elaboration Can we do the risky parts?
Construction Are we building this correctly?
Transition Is it what we wanted? Are we delivering this to the customer?
As you can see, the questions (or risks) that are managed during each phase have critical impact on the success of the project. Just guessing, most American companies are trying to "move to the left" of the process: covering Inception and maybe part of Elaboration and farming out the rest.
But this is a simplified diagram. In reality, each phase affects the earlier ones. Issues found in Elaboration can change deliverables from Inception. Likewise, risks discovered during Construction may require a major re-look at the issues addressed in Elaboration.
The danger is that this process is seen as it is drawn above: a simple set of blocks with "gates" between each step. The idea that somehow we can "pull this box out" and give it to some other team. That's not the way software development works. It certainly may be the way it is thought about in the board room, but the difference between the way it looks at fifty-thousand feet and the way it looks in the trenches is going to mean life or death for some of these outsourcing efforts. I'm not saying it's impossible, I'm saying it's poorly understood.