Here is one of the XP2006 workshop antipatterns the group worked on.
Manager prioritizes stories, tells how to do them, developers don’t have a say (because of manager’s authority)
Managers want to stay in control
Manager knows product and thinks he knows what users want
Organization doesn’t trust developers
Customer doesn’t get what he wants/needs
Team is disempowered/alienated
Creates dependency situation
Product owner manages the whole team. He discourages the team to come up with better solutions so that they depend on him.
Separate product owner from other roles on the product
Train manager as coach (so that he has a role outside of owning product and can drop that role)
Very small company
Temporary replacement if product owner on planned/unplanned absence
Feedback awaiting moderation
This post has 382 feedbacks awaiting moderation...