![]() īelow are the descriptions of the practices as described in the second edition of Extreme Programming Explained Embrace Change. ![]() If you would like more information about how these practices were originally described, you can visit. ![]() The XP Practices have changed a bit since they were initially introduced.The original twelve practices are listed below. While it is possible to do these practices in isolation, many teams have found some practices reinforce the others and should be done in conjunction to fully eliminate the risks you often face in software development. The core of XP is the interconnected set of software development practices listed below. The members of your team need to respect each other in order to communicate with each other, provide and accept feedback that honors your relationship, and to work together to identify simple designs and solutions. You need courage to accept and act on feedback, even when it’s difficult to accept. ![]() You need courage to stop doing something that doesn’t work and try something else. You need courage to raise organizational issues that reduce your team’s effectiveness. This definition shows a preference for action based on other principles so that the results aren’t harmful to the team. Kent Beck defined courage as “effective action in the face of fear” (Extreme Programming Explained P. Your team builds something, gathers feedback on your design and implementation, and then adjust your product going forward. Through constant feedback about their previous efforts, teams can identify areas for improvement and revise their practices. Simplicity also means address only the requirements that you know about don’t try to predict the future. Simplicity means “what is the simplest thing that will work?” The purpose of this is to avoid waste and do only absolutely necessary things such as keep the design of the system as simple as possible so that it is easier to maintain, support, and revise. XP stresses the importance of the appropriate kind of communication – face to face discussion with the aid of a white board or other drawing mechanism. Software development is inherently a team sport that relies on communication to transfer knowledge from one team member to everyone else on the team. The five values of XP are communication, simplicity, feedback, courage, and respect and are described in more detail below. While you can’t use the entire XP framework in many situations, that shouldn’t stop you from using as many of the practices as possible given your context. The post When is XP Not Appropriate on the C2 Wiki is probably a good place to start to find examples where you may not want to use XP. The technology you are using allows for automated unit and functional testsĭue to XP’s specificity when it comes to it’s full set of software engineering practices, there are several situations where you may not want to fully practice XP.Small, co-located extended development team.Risks caused by fixed time projects using new technology.Dynamically changing software requirements.The general characteristics where XP is appropriate were described by Don Wells on Learn Agile principles and techniques for beginners XP is the most specific of the agile frameworks regarding appropriate engineering practices for software development. Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team.
0 Comments
Leave a Reply. |