Some developers are a cancer too of course - want to do things they way they choose, taking the time they choose. A lot don't want to lose their specialisation or ownership of some portion of the code.
You get the senior devs who have been a law unto themselves for years and they certainly don't like anything that distributes power across the team. It might mean they have to do work they don't like sometimes.
From the start they're out to sink the whole scheme and even one of those in a team makes it very difficult to achieve any change.
That's just ontop of the fact that middle management don't like a method that removes their ability to interfere with the details or put pressure on individuals.
And of course in the end there are those developers who expect to do nothing but write beautiful lines of code all day long and consider every other part of delivering software to be beneath them - reviewing other people's code, writing tests, working on requirements, maintaining old code.
You get the senior devs who have been a law unto themselves for years and they certainly don't like anything that distributes power across the team. It might mean they have to do work they don't like sometimes.
From the start they're out to sink the whole scheme and even one of those in a team makes it very difficult to achieve any change.
That's just ontop of the fact that middle management don't like a method that removes their ability to interfere with the details or put pressure on individuals.
And of course in the end there are those developers who expect to do nothing but write beautiful lines of code all day long and consider every other part of delivering software to be beneath them - reviewing other people's code, writing tests, working on requirements, maintaining old code.