Extreme Programming — Summary of Practices

Hover or tap a practice to read what it means.

PracticesPracticesPracticesPRIMARYPRIMARYPRIMARYIntegrationIntegrationIntegrationTen-Minute BuildTen-Minute BuildTen-Minute BuildContinuous IntegrationContinuous IntegrationContinuous IntegrationWhole TeamWhole TeamWhole TeamProgrammingProgrammingProgrammingTest-First ProgrammingTest-First ProgrammingTest-First ProgrammingIncremental DesignIncremental DesignIncremental DesignPlanningPlanningPlanningWeekly CycleWeekly CycleWeekly CycleMonthly CycleMonthly CycleMonthly CycleStoriesStoriesStoriesSlackSlackSlackEnergized WorkEnergized WorkEnergized WorkCOROLLARYCOROLLARYCOROLLARYProgrammingProgrammingProgrammingShared CodeShared CodeShared CodeSingle Code BaseSingle Code BaseSingle Code BaseCode & TestsCode & TestsCode & TestsBusinessBusinessBusinessNegotiated Scope ContractNegotiated Scope ContractNegotiated Scope ContractPay-Per-UsePay-Per-UsePay-Per-UseDaily DeploymentDaily DeploymentDaily DeploymentIncremental DeploymentIncremental DeploymentIncremental DeploymentRoot Cause AnalysisRoot Cause AnalysisRoot Cause AnalysisTeamTeamTeamTeam ContinuityTeam ContinuityTeam ContinuityShrinking TeamsShrinking TeamsShrinking TeamsReal Customer InvolvementReal Customer InvolvementReal Customer Involvement

Point at any practice in the map above — say Incremental Design or Slack — and its explanation appears here, with its branch back to the centre highlighted.

After Kent Beck, Extreme Programming Explained: Embrace Change (2nd ed.).