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. .
SOFTWARE DEVELOPMENT ANALYSIS .
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. .
Risk analysis of the project is the next step, the project managers need to determine, based on the user requirements, the different risks that are involved in this particular project and have a plan of attack for any and all possible problems.