The article claims that it is their process, and although they are certainly extremely thorough, I don't buy it. At the very least, they cannot be compared to most developers apples to apples.
Why?
> NASA and the Lockheed Martin group agree in the most minute detail about everything the new code is supposed to do — and they commit that understanding to paper, with the kind of specificity and precision usually found in blueprints. Nothing in the specs is changed without agreement and understanding from both sides.
For most anyone working as a developer, could you even imagine what this would be like? Specs not changing or only changing in very small ways that are documented to the nth degree not only is impossible from a practical standpoint for most fields of software development, but such a different process that it's essentially a completely different field of work.
> Most people choose to spend their money at the wrong end of the process
> In the modern software environment, 80% of the cost of the software is spent after the software is written the first time
I would argue that this is largely the result of:
1. Incompetency as far as specifications go (suits don't know what they want, or what they are asking for)
2. Large changes in the specification (moving target)