Here is one of the XP2006 workshop antipatterns the group worked on.

Poor solution:
Unable to take responsibility
Cannot say no to developers/stakeholders

Forces:
Authority problems
Inappropriate personality in key role
Unclear roles/decision rights

Consequences:
“bedazzlement” – confusion – “rabbit in headlights”
Time wasted
Poor prioritization

Example:
Developers talk excessively at daily meetings
Multiple customers cause constant re-prioritization

Better solution:
Certain roles need certain personalities

Exceptions:
Better than having a “nasty” guy in charge.