About four years ago, many software developers in the industry were frustrated with the “heavy” methodologies that were being used. They were so complex and time consuming that many of the projects they were undertaking seemed almost unattainable. This is when the paradigm in thinking switched from “heavy” methodologies to the “lightweight” methodologies. (sdmagazine article)

XP is an example of a “lightweight” methodology. It simplifies the process and also involves the customer. Both of these elements help to ensure successful projects. The customer is involved throughout the process and the project is also broken down into smaller attainable steps or goals that will aide the developer in completing the project. Not only is this pl

The software development process basically breaks down into taking the customer’s project requirements and turning them into a valid, finished project. This seems easy in theory, but can become very complicated if all personnel involved on the project do not communicate and work well together. The developers must understand the customer’s requirements and in turn the customer needs to be able to accurately communicate their requirements and specifications. Only when managers are sure that this stage of the project is completed should they allow for the project to commence. When using the XP approach, this process is defined as the user stories. “User stories, written on cards, are the core of the XP planning process, and they belong to the people with the requirements.” (Jeffries). This is the stage of the project where the users is defining his requirements or telling you what the finished product should do. This is also the step where everyone involved needs to have excellent communication skills, both written and verbal.

Another important and distinguishing characteristic of the XP programming is the documentation. Documentation is developed in increments, simultaneously as the project is being developed and tested in increments. XP does not lend itself to the concept of writing the manual first and then designing the project to the manual’s specifications. XP allows for flexibility and this includes ever-evolving documentation of the project. “Don’t write and maintain implementation documentation-communication, in XP projects occurs face-to-face, or through efficient tests and carefully written code.” (Beck).

Not only is XP a more simplified approach, it is also flexible in more ways than one. Software developers can change to the entire XP approach or they can incorporate some of the methods in the XP approach into the method that they are familiar with. Many of the other methodologies do not have this type of flexibility. With them it is all or nothing. Another positive characteristic of the XP methodology is that it emphasizes teamwork. Everyone, including the programmers, managers, users, and customers become involved with the project from the very beginning and they work their way through the entire project, finishing with a quality product. XP helps to improve the project by building simplicity, communication, customer feedback and risk taking analysis into the methodology design. As stated earlier, it also allows for change throughout the entire design process. All of these positive characteristics are quickly making XP the preferred methodology of today.

Another positive effect that XP has on the industry is that it promotes testing. It involves testing throughout the develo

Some topics in this essay:
DEVELOPMENT ANALYSIS, Programming XP, XP XP-like, Changing XP, Jeffries Testing, INDUSTRY Extreme, FUTURE XP, Supporters XP, xp methodology, software development, development process, DEFINITION XP, software developers, Company UBS”, xp approach, allows change throughout, allows change, simplicity communication, throughout entire, change throughout, design process, improve project building, helps improve project, project building simplicity, xp helps improve,