Yes, but if your company were actually presented with such reliable software, the answer would be “well obviously we meant software that otherwise does what we want. This stuff doesn’t have half the features we need, and it’s almost completely unusable. We can’t deploy this, or we’ll be getting five calls about usability issues for every call we used to get about crashes and compatibility problems.”
Bottom line: what you trade away with the NASA approach isn’t only money. It’s also development speed. Okay if the application remains unchanged for three decades and the users spend a few years of their lives doing nothing but training, not so good otherwise.
Yes, but if your company were actually presented with such reliable software, the answer would be “well obviously we meant software that otherwise does what we want. This stuff doesn’t have half the features we need, and it’s almost completely unusable. We can’t deploy this, or we’ll be getting five calls about usability issues for every call we used to get about crashes and compatibility problems.”
Bottom line: what you trade away with the NASA approach isn’t only money. It’s also development speed. Okay if the application remains unchanged for three decades and the users spend a few years of their lives doing nothing but training, not so good otherwise.