volume_mute

XP Practices — Descriptions

publish date2026/06/04 05:56:8.575432 UTC

volume_mute

The diagram below shows the ten XP practices.

Key XP PracticesIncremental planningSmall releasesSimple designTest-first developmentRefactoringPair programmingCollective ownershipContinuous integrationSustainable paceOn-site customer


Match each practice to its correct description.

To complete the line match

  1. Click on an item in the first group
  2. Click on the match in the second group

To delete a match, double click on a line

Practice

Simple design
Collective ownership
Continuous integration
Sustainable pace

Description

Enough design is carried out to meet the current requirements and no more
Developer pairs work on all areas of the system so no islands of expertise develop — anyone can change anything
As soon as work on a task is complete it is integrated into the whole system; all unit tests must then pass
Large amounts of overtime are not acceptable as the net effect is often to reduce code quality and medium-term productivity

Correct Answer

(1) Simple design,Enough design is carried out to meet the current requirements and no more
(2) Collective ownership,Developer pairs work on all areas of the system so no islands of expertise develop — anyone can change anything
(3) Continuous integration,As soon as work on a task is complete it is integrated into the whole system; all unit tests must then pass
(4) Sustainable pace,Large amounts of overtime are not acceptable as the net effect is often to reduce code quality and medium-term productivity

Explanation

Simple design: just enough design for current requirements. Collective ownership: all developers take responsibility for all code — anyone can change anything. Continuous integration: completed tasks integrated immediately, all unit tests must pass. Sustainable pace: overtime reduces code quality and productivity.

Reference

Software Engineering, Ian Sommerville, 9th edition


Quizzes you can take where this question appears