I will disagree. You are building a product and you need to know if you are building the right thing. So you build it using a set of MVPs. Another way to call it is Objectives
MVP focuses on developing a product with just enough features to satisfy early users and provide feedback for future iterations. This means that the full vision of the product is sacrificed in favor of speed and minimalism. Key word: sacrificed. You don't sacrifice in a system humans are reliant on to live.
You can find this described on Wikipedia in a similar manner [0].
Compare this to a Waterfall approach - an approach that has been used in developing rigor in critical systems for decades. Waterfall emphasizes a complete and well-documented design upfront, ensuring that the final product aligns with the original vision and objectives. The end result is a fully-featured product, even if (and it will) take longer to develop.
Again... Wikipedia [1].
So, no. You don't build a mission critical system by stacking MVPs like Lego block on top of each other and then calling them "objectives". It's clear you've never built or been involved with building systems that are classified as "Safety of Life Critical System". Feel free to go review some relevant standards (e.g., ISO 26262, IEC 61508, DO-178C) and then feel free to re-justify how MVPs could be used for space vehicles that transport humans.
“ It's clear you've never built or been involved with building systems that are classified as "Safety of Life Critical System".”
That couldn’t be farther from the truth. I have worked on safety critical aircraft systems for the past 10 years. We incrementally have built MVPs and have been very successful. I won’t say which but it’s one of the most successful aircraft projects in development today.
