e-SEM
 Life cycle    | Phase-neutral themes    | Initiation    | Definition    | Design/Implementation    | Operations    | Termination
 eXtreme
 Programming (XP)
Testing
On-site-customer
Planning game
Short releases
Continuous
integration
Refactoring
Pair
programming
Metaphor
Coding
standards
Collective
ownership
40 hour week
Simple design

 


XP practices for agile software development

 
The 12 XP practices
XP is based on 12 practices that supplement and support each other. This gives rise to a network of methods, some of which are already very well known and are being implemented successfully. It is above all this combination of practices that the XP community is selling as unique and "extreme".
 

www.extremeprogramming.org
www.xprogramming.com/index.htm
2 important links on the Internet

XP at PSE
In some PSE projects, XP is being applied successfully. For more information and an exchange of experience, refer to the XP Interest Net. Whether or not the practices of XP can be applied in your project depends above all on the client-contractor relationship and on the concrete terms of commissioning (contract).

In a "classic" client-contractor relationship, XP is not suited as an overall model (little documentation, strong client involvement, no clearly defined scope of delivery at the start of the project), however, it is always possible to successfully apply single practices (such as for instance pair programming), which is not in contradiction to the principles of SEM.

The other pages of this section will give you a description of the individual XP practices and how they relate to e-SEM.

PSE Interest Net Extreme Programming
Exchange of experience and support within PSE

Click on this overview graph to see how the individual practices interrelate: