Try building any high-stakes engineering project (say, a bridge, or a production operating system) like that… With Agile, at best, you will build an amateur tr

Try building any high-stakes engineering project (say, a bridge, or a production operating system) like that… With Agile, at best, you will build an amateur treehouse. Sure, prototypes that test the viability of certain parts and aspects of the system are very useful. But having those prototypes and toy models then be “free-styled” (without a clear design document to be referenced - what exactly is the system supposed to do?) into a repurposed role to deliver the whole system’s functionality and reliability is the recipe to disaster. Or in other words: technical debt. - Where’s the Systems / Systems Integration perspective? - Where’s *Repeatability*? (middle management does like Agile to justify their many times useless positions) PS: I believe “Agile” explains a lot of the 737 MAX owes…