Antipattern: Lack of effective acceptance testing
Here is one of the XP2006 workshop antipatterns the group worked on.
Poor solution:
Acceptance testing is either not done or done at the end
Forces:
Excessive belief in unit testing
No testers involved
Insufficient awareness of how to “agilize”… more »
Antipattern: Too nice a guy in charge of planning
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… more »
Antipattern: Manager is Customer/Owner
Here is one of the XP2006 workshop antipatterns the group worked on.
Poor solution:
Manager prioritizes stories, tells how to do them, developers don’t have a say (because of manager’s authority)
Forces:
Customer absent
Managers want to stay in… more »
Antipattern: Programmer Marriage (when 2 become 1)
Here is one of the XP2006 workshop antipatterns the group worked on.
Poor solution:
Not switching pairs
Forces:
High productivity of pair
Pair is happy
“never change a winning team”
Inability to pair with others
Consequences:
Pair does not… more »
Antipattern: Team does not refactor enough
Here is one of the XP2006 workshop antipatterns the group worked on.
Poor solution:
Individuals volunteer to refactor for the team
Forces:
Trying to take responsibility on behalf of the team
Some people do not refactor enough
Some people are af… more »


