XP Practices

November 28, 2007 by Artem Marchenko

Values are the the roots of Extreme Programming stating what we like and not like. Principles guide applying the values to the realities of software development. Engineering and not so engineering practices compose the lowest and the most explicit layer of XP. These are known best ways of implementing the values and principles in the daily work. Primary practices are the ones that are useful on their own. Corollary practices are not so safe to start with and are best applied after most of the primary ones are implemented and there is a certain level of understanding the XP values and culture in the organization.

XP Primary Practices

Sit Together, Whole Team, Informative Workspace, Energized Work, Pair Programming, Stories, Weekly Cycle, Quarterly Cycle, Slack, Ten-Minute Build, Continuous Integration, Test-First Programming, Incremental Design

XP Corollary Practices

Real Customer Involvement, Incremental Deployment, Team Continuity, Shrinking Teams, Root Cause Analysis, Shared Code, Code and Tests, Single Code Base, Daily Deployment, Negotiated Scope Contract, Pay-per-use

Further Links

• Extreme Programming Core Practices on c2 wiki - some practice pages include a lot of discussion, some - only a brief definition
• The Rules and Practices of Extreme Programming - not that much about the practices, but a good reading otherwise
• What is Extreme Programming by Ron Jeffries' - a good and rather condensed article by one of known XP practitioners

This page is a part of the Extreme Programming overview

Permalink