Extreme Programming (XP)
Extreme Programming (XP) is an agile software development framework that emphasizes technical excellence and engineering practices such as pair programming, test-driven development, continuous integration, and frequent releases.
Explanation
XP was created by Kent Beck in the late 1990s and is built around five values: communication, simplicity, feedback, courage, and respect. XP takes proven software engineering practices to extreme levels. For example, if code review is good, XP takes it to the extreme with pair programming. If testing is good, XP takes it to the extreme with test-driven development.
Key XP practices include pair programming, TDD, continuous integration, refactoring, simple design, collective code ownership, coding standards, sustainable pace, and small releases. These practices reinforce each other and create a disciplined approach to software development that produces high-quality code with minimal defects.
XP teams work in short iterations (typically one to two weeks) and deliver working software at the end of each iteration. XP places a strong emphasis on customer involvement, with an on-site customer providing rapid feedback and clarification. For the exam, understand XP as the most engineering-practice-focused agile framework.
Key Points
- •Five values: communication, simplicity, feedback, courage, and respect
- •Emphasizes engineering practices like pair programming, TDD, and CI
- •Short iterations of one to two weeks with frequent releases
- •Strong emphasis on technical excellence and customer involvement
Exam Tip
XP is the agile framework most focused on engineering practices. If a question asks about technical practices like TDD or pair programming, they originate from XP.
Frequently Asked Questions
Related Topics
Pair Programming
Pair Programming is an XP practice where two developers work together at one workstation, with one writing code (the driver) and the other reviewing each line in real time (the navigator).
Test-Driven Development (TDD)
Test-Driven Development (TDD) is a software development practice where developers write a failing test before writing the production code that makes it pass, following a red-green-refactor cycle.
Continuous Integration
Continuous Integration (CI) is the practice of frequently merging code changes into a shared repository, where automated builds and tests verify each integration to detect problems early.
Refactoring
Refactoring is the practice of restructuring existing code without changing its external behavior to improve its readability, reduce complexity, and make it easier to maintain.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Part of
Agile & Hybrid
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.