loading...
AntiPractices: AntiPatterns for XP Practices
Salt Lake City, Utah, USA June 22-June 26
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ADEVC.2004.7Agile Development Conference (ADC'04)
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Yoshihito Kuranuki, TIS, Inc., Eiwa System Management, Inc.
Kenji Hiranabe, TIS, Inc., Eiwa System Management, Inc.
When you introduce Extreme Programming (XP) to your project, the team gets fresh energy and high efficiency. However, sustaining the good condition becomes difficult when you are attacked by its side effects. We call these XP side effects "AntiPractices", just as AntiPatterns come from Patterns. "Turning all the knobs up to 10" is the XP way, but AntiPractices show bad symptoms of the overdrive. (There is a proverb "more than enough is too much" in Japan.)
In this experience report, we identify AntiPractices discovered from our projects. We add prescriptions so that XPers can share the countermeasures.
Citation:
Yoshihito Kuranuki, Kenji Hiranabe, "AntiPractices: AntiPatterns for XP Practices," adc, pp.83-86, Agile Development Conference (ADC'04), 2004
Usage of this product signifies your acceptance of the Terms of Use.


Suggestions