The document provides an overview of Extreme Programming (XP), the most widely used agile development process originally proposed by Kent Beck. It discusses the key practices of XP including planning with user stories, small iterative releases, simple design practices like CRC cards, test-driven development, pair programming, continuous integration, and collective code ownership. The document notes that XP works well for projects with dynamically changing requirements, risky projects, or small development groups of up to 100 people.
16. Extreme Programming (XP) Planning Design Test Coding Release The XP Process The most widely used Agile process, and it is originally proposed by Kent Benck.
23. Testing Unit tests are written before the code. Tests are run to ensure that our software fails . A good test case is one that ensures that the software fails. Test is rerun until it passes .
24.
25.
26. Testing Fixing small problems every few hours takes less time than fixing huge problems just before the deadline. Fact:
28. Coding Two people work together at one computer to create code for a story. This provides a mechanism for real-time problem solving and real-time quality assurance . Keeps the developers focused on the problem at hand. As pair programmers complete their work, the code they develop is integrated with the work of others.
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](https://image.slidesharecdn.com/agile-development-ultimate-slides-1198295615697276-4/85/Agile-Development-Ultimate-Slides-1-320.jpg)
![Just before we begin… ,[object Object],[object Object],.](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)