← Back to blog

Complete Guide to Extreme Programming (XP)

xp agile engineering-practices

Extreme Programming (XP) is the agile framework most focused on technical development practices. While Scrum organizes the process, XP solves how to write quality code.

XP Values

  • Communication — code is communication between developers
  • Simplicity — do the simplest thing that works
  • Feedback — short, constant, and honest
  • Courage — refactor, throw away bad code, tell the truth
  • Respect — among team members and for the code

The 12 XP Practices

1. Planning Game

Scope is divided into short iterations with small and frequent releases.

2. Pair Programming

Two developers, one computer. Real-time code review.

3. Test-Driven Development (TDD)

Tests before code. Red → Green → Refactor.

4. Continuous Integration

Integrate code multiple times a day. The build must always pass.

5. Refactoring

Improve the code structure without changing its behavior.

6. Simple Design

The simplest design that works. No over-engineering.

7. Collective Code Ownership

Any team member can change any part of the codebase.

8. Coding Standards

Consistent coding standards across the entire team.

9. Sustainable Pace

No chronic overtime. Maintain a sustainable rhythm.

10. On-site Customer

A customer or representative available within the team.

11. Metaphor

A shared metaphor for the system aids communication.

12. System Metaphor

A common name and concept for the system.

XP + Scrum = ScrumBan? No, Scrum + XP

Many teams use Scrum for process + XP for technical practice:

  • Sprint Planning and Scrum ceremonies
  • TDD, Pair Programming, and CI/CD from XP
  • Result: structure + technical quality

When It’s Worth It

  • Teams with many bugs in production
  • Teams that want less technical debt
  • Projects with critical code (financial, medical)
  • Teams that want continuous technical improvement

When It Might Be Overkill

  • MVPs for quick validation
  • Projects with extremely tight deadlines
  • Teams without experience in agile practices
  • Throwaway prototypes

Conclusion

XP is not radical — it is disciplined. XP practices solve real technical quality problems that Scrum alone does not cover. Combine the two for structure and quality.