The Cult Of Agile with its Holy Practices that Must Be Done without actual logical and well thought about reasons (instead, the reason are things like "It's What It Says In This Agile Holy Book" and/or "That's What I Saw Other Agile People Do"), is not at all the same as the class of Software Development Processes called Agile.

Then again, Software Development Processes are the kind of thing you tackle at the level of Technical Architect, and since there aren't really that many genuine Technical Architects (with the actual chops, rather than merelly 5-10 years experience in a single kind of development environment and a title obtained from a company that gives fancy titles as "promotion" instead of a proper salary raise) around, Agile is mostly just blindly followed without true understanding of what it does, what it doesn't do, how that is does it or why it cannot do it, and thus were and how it actually adds value and were it doesn't.