Loading content
Extreme Programming (XP) is an agile software development method that emphasizes short iterations, continuous feedback, and strong engineering practices such as TDD and pair programming. It improves code quality and responsiveness to change through frequent releases and close customer collaboration. XP requires discipline and a supportive organizational envi…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Extreme Programming (XP) is an agile development method that protects software quality and adaptability through short cycles, close customer feedback, and disciplined engineering practices.
Extreme Programming emerged in the 1990s from work on the Chrysler Comprehensive Compensation System (C3). Kent Beck reshaped the development practice there, with influence from and collaboration with Ward Cunningham and Ron Jeffries. The method responded to rapidly changing requirements, short product cycles, and the limits of traditional processes; Beck later collected the experience in Extreme Programming Explained in 1999.
XP works like a tight control loop for software development. The team plans small increments, builds them immediately, checks them with automated tests, and gets early feedback from the customer side. Pair programming, reviews, and simple designs reduce wrong assumptions, while short releases expose what needs to change next. Change is treated as a normal part of the work, not an exception.
XP belongs to agile approaches that deliver iteratively and adapt continuously to new information.
Work is broken into small development cycles that can be checked quickly.
Tests are written before, or very early after, the code so behavior is checked precisely.
Two people work on one task together and catch mistakes and ambiguities earlier.
Domain feedback enters frequently so requirements can be refined continuously.
Solutions should be no more complex than the current problem requires.
XP is useful when requirements are uncertain, quality must surface early, and the team can work closely with domain experts or product ownership. It is especially valuable in iterative product development under strong change pressure. The trade-off is discipline: XP depends on automation, pairing, communication, and an environment that genuinely supports refactorable design.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.