I just want to highlight this entire article. It's not to say that Agile doesn't have advantages and benefits, but I think it's a lot like dynamic and functional languages, where it's an effective tool for 10x developers, but in the hands of an average or mediocre developer, it becomes quite the hazard. And, much like driving skills, people have a bad habit of overestimating their ability to use these things safely. The amount of guardrails you need to put into place to use Agile safely for the average team takes away so much of its flexibility and speed that I don't think it ends up being too different from Waterfall anyways.

I think another issue is that Agile proponents have badly sold it as being right for any and all projects, when for me it has some use cases where it shines - like delivering SaaS products that need to constantly evolve and grow their feature set, or extremely loosely coupled code like Netflix's "death star" of microservices - and a lot of use cases where it falls flat (like most professional services engagements with a defined timeline and budget and set of goals).

J.Ja