eXtreme programming
Enlarge text Shrink text-
Topic
- Work cat.: 99036995: Beck, K. eXtreme programming, 1999:CIP galley (eXtreme programming (henceforth XP). XP is a lightweight methodology for small-to-medium sized teams developing software in the face of vague or rapidly changing requirements)
- eXtreme programming web site, July 2, 1999(EXtreme programming (XP) is the name that Kent Beck has given to the lightweight team process which he has been evolving over the years. In XP, we use a very lightweight combination of practices to create a team that can rapidly produce extremely reliable, efficient, well-factored software. Many of the XP practices were created and tested as part of the Chrysler C3 project, which is a very successful payroll system implemented in Smalltalk)
Extreme programming (XP) is a software development methodology intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which 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, not programming features until they are actually needed, a flat management structure, code simplicity and clarity, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers. The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels. As an example, code reviews are considered a beneficial practice; taken to the extreme, code can be reviewed continuously (i.e. the practice of pair programming).
Read more on Wikipedia >