Extreme Programming

Extreme Programming

Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,"Informatics85">
"Human Centred Technology Workshop 2005",
2005, PDF webpage:
.
UPenn49/>USFCA601/>
it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.

Other elements of Extreme Programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customers requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers."UPenn49">
"Design Patterns and Refactoring",
University of Pennsylvania, 2003, webpage:
.
"USFCA601">
"Extreme Programming" (lecture paper),
USFCA.edu, webpage:
.
"MASD">
"Manifesto for Agile Software Development",
Agile Alliance, 2001, webpage:

The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels, on the theory that if some is good, more is better. It is unrelated to "cowboy coding", which is more free-form and unplanned. It does not advocate "death march" work schedules, but instead working at a sustainable pace."tr"/>

Critics have noted several potential drawbacks,Cworld92/> including problems with unstable requirements, no documented compromises of user conflicts, and lack of an overall design spec or document.

History
Extreme Programming was created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project.Cworld92/> read more at » http://en.wikipedia.org/wiki/Extreme+Programming

http://en.wikipedia.org/wiki/Extreme+Programming