A Problem with Scrum (agile)
In one word: Management
So many projects these days talk about being agile, but in reality they are not. The biggest problem is that to become agile means a fundamental shift in the way people think about projects from the project management/senior management viewpoint. As an example, historically projects were planned to the nth degree using Microsoft Project or similar, giving senior management the feeling that the project would hit the delivery dates and that all dependencies where understood. Unfortunately as we all know this was a complete farce. Today most projects think that using iteration and stories mean a project is agile. Unfortunately these same projects probably have a project plan which is as adaptive as a waterfall project. For each change that the business request, n man days of project management kick in to attempt to correct the overly complex n year project plan 
There still appears to be the need for a very large training initiative for corporations to understand the concept of backlog and iteration development, and to truely see the advantages of lean agile development. Where the old world (waterfall) meets the new world (agile) is still a very painful experience.
Agree. But I also think that it is easier for the PMs’ management to believe that all is rosy in the world project – thats certaily what they will be told. You could argue that the function is actually redundant and that perhaps what we now need is someone to act as product owner.