XP - eXtreme Programming

L'XP est une méthode disciplinée de développement mettant la priorité sur la satisfaction du client. Les tests unitaires en sont une pierre angulaire.

Extreme Programming (XP) is actually a deliberate and disciplined approach to software development. About six years old, it has already been proven at cost conscious companies like Bayerische Landesbank, Credit Swiss Life, DaimlerChrysler, First Union National Bank, Ford Motor Company and UBS.
XP is successful because it stresses customer satisfaction. The methodology is designed to deliver the software your customer needs when it is needed. XP empowers your developers to confidently respond to changing customer requirements, even late in the life cycle.
This methodology also emphasizes team work. Managers, customers, and developers are all part of a team dedicated to delivering quality software. XP implements a simple, yet effective way to enable groupware style development.
XP improves a software project in four essential ways : communication, simplicity, feedback, and courage. XP programmers communicate with their customers and fellow programmers. They keep their design simple and clean. They get feedback by testing their software starting on day one. They deliver the system to the customers as early as possible and implement changes as suggested. With this foundation XP programmers are able to courageously respond to changing requirements and technology.
XP is different. It is a lot like a jig saw puzzle. There are many small pieces. Individually the pieces make no sense, but when combined together a complete picture can be seen. This is a significant departure from traditional software development methods and ushers in a change in the way we program.

Extreme programming (XP) is a set of software development practices, originated by Kent Beck. XP developers work continuously with the customer, anticipate frequent changes to the software spec, and develop tests to evaluate when a coding goal is achieved. XP is often boiled down to 12 core practices, which include:

• Planning with customers
• Functional testing and unit testing
• Refactoring
• Simple design
• Simple code metaphors
• Collective code ownership
• Coding standards
• Continuous integration of changes
• Customer on site
• Open workspace
• 40-hour week
• Pair programming