Earlier quoted context omitted.
4. The requirements are often flat out wrong. The Phoenix payroll system comes to mind, the Canadian government tried to shift the blame to IBM, but have their hands tied since IBM delivered exactly what was in the contract. It's just that what the government decided to put in the contract has little to do with how they really do payroll.
> 4. The requirements are often flat out wrong. Isn't this basically a given? I find it hard to imagine that any organization could come up with good, complete requirements before they've had any software written.
Governments by their nature tend to approach everything from a legal perspective.
This then means the requirements of these big IT project end up being a mass of legal documents which try to describe what is being delivered by whom.
Then when the whole thing falls apart it ends up in the courts and the court then decides who promised what based on those original contract documents.