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.

3. Software development Process Task (1) Task (2) Task (3) . . . Task (n) Goal HIGH QUALITY SOFTWARE Action

5. THE ROADMAP THAT YOU FOLLOW

6. Software development Process Models

7. Nature of Software Change

12. So, what is Agility? Drawing the customer into the team .

13. This yields to…

14. Rapid & incremental delivery of software.

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.

17. Planning

22. Testing TEST FIRST

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 .

26. Testing Fixing small problems every few hours takes less time than fixing huge problems just before the deadline. Fact:

27. Coding Pair Programming

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.

29. Coding ROI

30. Coding ROI

31. Release Project Velocity The number of stories that we performed in this release.

32. When to use XP? Dynamically changing requirements. Risky projects. Small development groups (up to 100). Non-fixed price contract.

35. We Must Ask Ourselves… Do we need Agile or any other Software Development Process models in our lab?

36. Questions?