Extreme programming practices

From: Agile Software Development: Principles, models, and practices: Robert C. Martin, translated by Deng Hui]

Extreme programming practices:
1. Complete team:
All participants of the XP Project (developers, business analysts, testers, etc.) work together in an open place where they are members of the same team. The walls of the place are displayed with large, notable charts and other things that show their progress.

2. Plan the game:
The plan is continuous and gradual. Every two weeks, developers estimate the cost of candidate features for the next two weeks, while customers choose the features to be implemented based on the cost and business value.

3. Customer test:
As part of selecting each desired feature, the customer defines an automatic acceptance test to indicate that the feature can work.

4. Simple Design:
The Team maintains that the design exactly matches the current system function items. It passes all tests and does not contain any duplicates. It expresses everything the author wants to express and contains as few as possibleCode.

5. Pair programming:
All product software is composed of twoProgramMembers, sitting side by side on the same machine.

6. Test-driven development:
Programmers work in a very short cycle. They first add a failed test and then make it pass.

7. Improved Design:
Improve bad code at any time. Keep the code as clean and expressive as possible.

8. Continuous integration:
The team is always integrated with the system.

9. collective code ownership:
Any paired programmer can improve any code at any time.

10. encoding standards:
All the code in the system looks like it is written by a single person who is very competent.

11. metaphor:
The team proposed a public picture of how the program works.

12. Sustainable speed:
Only a long-lasting team can win the game. They work hard at a rate that can be maintained for a long time. They save their energy and think of the project as a marathon, not a full-speed sprint.