3 ms·
They did; the anticipated needs in the environment when it was designed were not the actual needs when it waa delivered. This is a perennial big-project proble
by dragonwriter 4y ago
They did; the anticipated needs in the environment when it was designed were not the actual needs when it waa delivered.
This is a perennial big-project problem (one of the core things addressed, originally, by Agile in software), but you can’t easily quickly turn out an MVP of a warship and rapidly iterate on it.
A lot of time it doesn’t get noticed because needs move further toward the strengths of the project, or because there is a good opportunity for adaptation. But sometimes, you just get burned.
- iudqnolq 4y agoFunnily enough they did try to do agile design with these warships. They started building the first one before they figured out the whole design, with the idea they could update as they went. It was an absolute disaster. They had to redo a bunch of work to fit in changes they didn't anticipate. Now all the early ships are unique, making maintenance worse. Turns out Agile depends on a low cost to refactor. It's easy to make a function body bigger. It's very painful to make an engine room bigger.