Frog Driven Development by spif
24waystostart.com
24waystostart.com
I don't have a lot of experience contracting or being a contractor, but if it's clear that a project is going over budget, what contractor in their right mind would agree to a fixed fee contract? It sounds like that would be a situation with no upside for the contractor. Am I wrong about this?
Apart from that, I like the analogy.
If you can stomach frog torture then here's some more background: http://en.wikipedia.org/wiki/Boiling_frog
I believe the basic error is not recognizing the project as an integration task. There are many systems that fit nicely into some existing mature framework. There are others that require an additional effort to make two pieces of software work together, two pieces of software that weren't meant to play together in the first place.
A programmer that's able to do this kind of work needs a very wide knowledge, specific experience and being very stubborn. Outsourcing this work is, now you know, risky. But it's not just that. If you're working now with people in-house, I assume you're seeing that little quirks take more time than functionality development.