---
title: extreme programming
slug: extreme-programming
qid: Q209711
snapshot: extreme-programming-024762-73cb4b22a3cd8d42
content_hash: 73cb4b22a3cd8d42ce3e7bc53bd6e519c4744f6458fad0cb4076a53b35ba1c72
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1376079099
tags: [129826521, 22176491, 22911899, 22923484, 22930698, 22958409, 23015547, 23118434, 23603337, 24043274, 24623845, 24745122, 26839250, 28269686, 36406786, 62672627, 68319748]
---

# extreme programming

> [!note] Provenance
> Snapshot `extreme-programming-024762-73cb4b22a3cd8d42` · content root `73cb4b22a3cd8d42…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1376079099> · Licensed CC BY-SA 4.0

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).

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).
