Ravi, like many project (1) , had studied the waterfall model of software development as the primary software life-cycle (2) . He has all set to use it for an upcoming project, his first assignment. However, Ravi found that the waterfall model could not be used because the customer wanted the software delivered in stages, something that implied that the system had to be delivered and built in (3) and not as (4) . The situation in many other projects is not very different. The real world rarely presents a problem in which a standard process, or the process used in a previous project, is the best choice. To be the most situation, an existing process must be (5) to the new problem. A development process, even after tailoring, generally cannot handle change requests. To accommodate change requests without losing control of the project, you must supplement the development process with a requirement change management process.

Extreme Programming (XP) is a discipline of sofiware development with (1) of simplicity,communication, feedback and cuurage. Successful software development is a team effort - not just the development team, but the larger team consisting of customer, management and developers. XP is a simple process that brings these people together and helps them to success together. XP is aimed primarily at object-oriented projects using teams of a dozen or fewer programmers in one location. The principles of XP apply to any (2) project that needs to deliver quality software rapidly and flexibly. An XP project needs a (3) customer to provide guidance. Customers, programmers, managers, are all working (4) to build the system that's needed, Customers - those who have software that needs to be developed - will learn simple, effective way to (5) what they need, to be sure that they are getting what they need, and to steer the project to success.