You are on page 1of 2

XP concepts of refactoring:

Before describing the XP concepts of refactoring we will find a proper


definition for it
Refactoring is a practice of software development that allows you to improve the code
without changing or breaking its functionality. It is aimed at simplification. The code
should be as simple as possible to find all the bugs and to make it easy to change
something in the process of project’s performance. Refactoring is especially necessary
in Extreme Programming and other Agile projects because they require strong customer
involvement into the working process. If the client wants to change something in the
final product, the team should make these changes as fast as it is possible. XP code
refactoring allows you to achieve this goal.
 
XP concepts of refactoring and Pair Programming
Refactoring works very well in all XP projects, including those that are based on Pair
Programming principles. Two persons can refactor the initial code even more efficiently
than just one employee.

Pair programming:
Pair programming is an Agile technique originating from Extreme programming
(XP) in which two developers team together and work on one computer. The two
people work together to design, code and test user stories. Ideally, the two
people would be equally skilled and would each have equal time at the keyboard.

Pair programming uses the four eyes principal, ensuring that two sets of eyes
review the code that is being produced even when there is a division of labor.
While one person writes test cases using test-driven development techniques, for
example, the other person may write code to get the tests to pass. Typically, the
two developers will turns coding or reviewing, checking each other's work as they
go. 

You might also like