In late 1990 a number of software developers began looking for an alternative to traditional methods of software development and Extreme Programming, which are usually based on the waterfall model. In early 2001 a group of experts formulated the basic principles of soft technology, now known as agile software development. The main elements of the philosophy of Extreme Programming agile development are:

• Focus on staff involved in the project of Extreme Programming, including both buyers and sellers. Successful cooperation of experts selected is properly considered a promise of future success of a project.

• Change of formal specification for effective communication. Discussion and feedback to a basic line of communication between the team and the buyer, and team

• Iterative Extreme Programming development with up to short duration of each iteration, each resulting in the release of a fully functional version of the product.

• Extreme Programming Flexibility to change – in the first phase of the work of the project team does not establish a series of stringent requirements on a strict plan to follow. In agile development environment changes can be made on each project.

Extreme Programming Is methodology Software

Extreme Programming is one of the most widespread methods of agile software development. The fundamental principles are formulated in 1996 by Kent Beck as a failed project accounting system to restore one of the giants of the auto industry. It did not help the project, but the XP methodology has gained popularity and many of the software development teams have been chosen as a method of leadership.

Extreme Programming  From Chris Aronivich