Some thoughts...
There are some things to like in Agile. And some things which make no sense at all.
But that's not really what I'd like to focus on. I've had some thoughts percolating in my mind for a while, and would like to dump them here.
We shouldn't need Agile. It's a sticking plaster. Agile is often brought in because of previous failures to deliver IT projects. When Agile fails it's often not because of anything Agile was doing - any project management system/methodology would have failed in those conditions.
It's an unfortunate truth that people in IT are often bad at explaining the necessities and requirements that their platforms/technologies/infrastructures have.
It's an unfortunate truth that people in Management are often bad at making time to understand their IT requirements and capabilities.
It's an unfortunate truth that people in IT are often bad at making time to understand their organisation's requirements and capabilities.
It's an unfortunate truth that people in Management are often bad at explaining the necessities and requirements that their organisation has.
It's an unfortunate truth that many people are eager to please others, so will give slightly optimistic estimates. (We've all regretted it, right?)
It's an unfortunate truth that some people in Management are grubby little climbers, happy to shave estimates down to make themselves look better.
All of this combines to create significant issues with communication and trust. In many organisations both sides might say they trust and respect each other, but their behaviour says otherwise.
I feel that Agile was created simply as a framework to try and deal with these unfortunate truths. Something we could wheel out and say "Let's start over with this, which will fix it!"
The sad fact is that in doing so, it fails to address the actual problems. It's like putting a splint on a broken arm and then saying "Right, that'll do it. Back to climbing up the north face of the Eiger then..."
Strangely, that's not very likely to end well.
I find it fascinating that our relatively immature industry thinks it needs its own methods of working. Generations of tallest buildings, fastest aircraft, largest ships, longest bridges, and much more were done with fairly traditional project management methods and systems. And yet somehow we can't use those? It's an interesting narcissism - "the problem isn't our industry, the problem is we're using bad tools". Well we all know a phrase related to that attitude...
I don't hate Agile. I don't love traditional project management. I'd just like to see us being honest about the root causes that often drive people to change their management methods. Because surely if more than one method system has failed, then the problem is likely to be somewhere else?
Anyway, sorry if I've offended anyone who's inexplicably wedded to the cause. Hopefully an alternative point of view is useful to you...