Discussion on: Was Cascade that bad 🤔?

I think it rather depends on the project itself. I doubt they build space rockets using a trial and error agile methodology. On the other end of the spectrum, when you don't exactly know what your audience exactly wants, quick iterations, prototypes and feedback are great. Such "not clearly outlined" projects are fairly typical in IT. However, if something rather big, involving several teams is built, the sudden changes and short cycles typical to agile methodology become drawbacks. All the devs will just cringe their teeth and shout "What, the other teams APIs/components/modules changed again?! Duh, we have to change everything too! This lack of proper planning makes so much work go down the drain!". Agile is also a vague term. Many people interpret it differently. Although I agree to it's original principles in the manifesto, it kind of evolved on it's own. Sometimes, it's more like navigating on sight vs planning the path beforehand. Also, it's rarely purely agile or purely cascade, but often somewhere in between.