#lean, #agile and the fundamental principals of Small Batches seem to be at odds with programs like carrier development and defence contracts in general. It's very unlikely that the lessons from IT fields will ever make their way into projects like this.
Re:How not to build a ship: the USS Ford
by mysterydip on Thursday June 08, 2017 @12:11AM
(#14511866)
I can understand the perspective, too, though. Stuff has to work. You're not emailing a new build to them mid-cruise. This means there should be a large paper trail and signoff on any project, which makes any team hesitant to anything but incremental changes.
I'm not sure what the ultimate solution would be that keeps the reliability aspect but allows for more risky/rapid development.
Anyone who has been in IT should have seen the story play out at least once in their career: some legacy system that's been hobbled together to keep running for so long because it worked... but now that a decade or more has passed there's finally some catalyst that says you _must_ upgrade. The problem being that now the upgrade is rip-and-replace rather than micro updates over time. That's what's happening here, on many systems at once.