Category

2.     On-site customer

3.     Testing

4.     small releases

Category

2.     coding standards

3.     pair programming

4.     small releases Collective ownership

5.     continuous integration

Category

2.     Simple design

3.     Testing

4.     Refactoring

In XP, programmers practice developing a simple design with the help of programming languages and other modeling languages.

Testing Practice in XP

In XP, programmers practice testing the code(e.g; white box testing)

Refactoring Practice in XP

In XP, programmers practice improving the code without changing the functionality of the code.

coding standards Practice in XP

In XP, programmers practice following the coding standards as followed by the software developer’s community.

In XP, the team practice to encourage everyone to contribute new ideas to improve and to complete the project. For example, Any developer can change any line of code for better improvements in the project.

Continuous integration Practice in XP

In XP, the team practice to integrate the code and other material into a shared repository. This sharing is not limited and can be performed as much as needed.

Metaphor Practice in XP

In XP, the team practice to replace the standard project architecture used in traditional software development methodologies.

Coding standards Practice in XP

In XP, not only programmers but all other team members practice ensuring that all coding standards are following by programmers and by all the team.

 40-hour week Practice in XP

In XP, the team practice to work for quality and not for quantity. The team supposed to work only for 40 hours collectively in a week. This is just a practice and can be varied according to the expertise and mood of your team.

Pair programming Practice in XP

In XP, two of the developers from the teamwork together and work on one computer to achieve a task.

Small releases Practice in XP

In XP, the team practice to deliver the system modules in parts.

In XP, the team practice to communicate with the customer, online, or preferably face to face. The customers help to validate that the system’s desired functionality is covered by use cases or stories. Similarly, customers validate all the processes according to the functional requirements.

Testing Practice in XP

In XP, the tester practice to play both the customer and programmer roles and test the system.

Small releases Practice in XP

In XP, the team practice to deliver the small releases to show the accuracy of the overall process and work done by the team.

Planning Game Practice in XP

In XP, the team practice to arrange a planning meeting that occurs once per iteration, typically once a week.

(Principle)

2.     The Planning Game

3.     On-site Customer

4.     Pair Programming

2.     Refactoring

3.     Small Releases

2.     System Metaphor

3.     Collective Code Ownership

4.     Coding Standards