So, we have started trying to work to Agile/scrum in our business to run the software dev team and it's not (in my eyes as a humble dev) working very well. Its getting to the point now where the team (devs/scrum master) are getting very pissed off due to it turning into more of a time and motion exercise than a 'get quality products out the door exercise'.The main issue is with our backlog, we have a product owner who is also the IT manager. Virtually all of the items on the backlog have really poorly defined stories, nothing has any priority and no one else in the business seems to be having any input into the backlog. It gets filled by the assumption of the IT manager most of the time, and other times based on who in the business shouts the loudest.We have suggested improvements in the retrospectives but they all seem to fall on deaf ears. As a team, has anyone encountered this before, I'd be interested to hear how they tackled the problem. As far as I'm concerned the business isn't invested so Agile is failing. 
When Agile becomes a bit slugish
agile;scrum
I dislike Scrum. It has been described as the least agile agile methodology ever. I think its the cause of much inefficiency and a lot of friction between management and development. Understand that all published agile methodologies are starting points for your own modification. Scrap the bits that do not work for your environment, add bits that you think would help. Never, ever follow the methodology as if it were holy scripture. It isn't. Often they are just practices that worked for some team and are now published in case they help you. Unfortunately a whole industry has grown around doing agile this way, and they like to tell you to follow the rules - that way you need to buy consultant time to find out how to do it right. Good for the training company, bad for you.So you have issues with the scrum way that are not going to be fixed unless you get the IT manager and business team on board. They have to understand and get with the programme for what you're doing to work. But, they are the programme and so it's you who has to change to accommodate them.You can change scrum to suit, but I think that's a huge task, so change agile method. One of the ones that is very popular and much more in keeping with how old IT managers expect work to progress is Kanban. Change your dev team to use this, do not be afraid to tweak it, and I think you will suddenly find Agile being a big success across the whole extended team. 