The document provides an overview of eXtreme Programming (XP), an agile software development framework. It discusses the core values, principles and practices of XP, which include simple design, frequent iteration and reflection, communication, courage and respect. The primary XP practices are described as sitting together, having an informative workspace, pair programming, working in small iterations called stories, and continuous integration testing. The goal of XP is to improve software quality, reduce costs and defects through a collaborative team approach.

1. Agile NCR Workshop Method Overview eXtreme Programming V I K A S H A Z R A T I June 28' 2008

2. Know your presenter Practising XP and Scrum for last 3 years Board member of Agile Software Community of India Agile Community editor on InfoQ Published articles on The Server Side, Agile Journal Personal blog site http://vikashazrati.wordpress.com

3. What is XP? XP is a mindset change! XP is a philosophy of software development based on well laid out values, principles and practices. Goal of XP is outstanding software development at lower cost, with fewer defects, high productivity and much higher return on investment.

4. Why XP? Another methodology but why? Social Change- Giving up defences Based on Excellent programming techniques, clear communication and teamwork Lightweight – only do whatever adds value to the customer Addresses constraints in software development Can work with teams of any size Adapts to rapidly changing requirements

5. Core Components Values Practices Principles

6. The Five Core Values of XP Communication Simplicity Feedback Courage Respect

7. XP Principles Humanity Economics Mutual Benefit Improvement Opportunities Reflection Diversity Flow Accepted Responsibility Baby Steps Failure Quality

8. Practices Primary Corollary

9. Primary Practices Sit Together Whole Team Informative workspace Energized work Pair Programming Stories Weekly Cycle Quarterly Cycle Slack 10 minute build Continuous Integration Test First Programming Incremental Design

10. Sit Together / Whole Team

11. Sit Together / Whole Team

12. Informative Workspace

13. Informative Workspace

14. Energized work Work only as many hours as productive Ideally 40 hours a week Programming productivity is seen to be 4-5 hours a day

15. Pair Programming

16. Pair Programming

17. Stories Units of customer visible functionality. Should be on the story wall for everyone to look at.

18. A Story

19. Story Life Cycle

20. Weekly / Quarterly Cycles

21. More... Slack Ten Minute Build Continuous Integration Test First Programming Incremental Design Do the simplest thing that can possibly work Refactor

22. The Whole XP Team Emphasis on the “Whole Team” Collaboration and collocation

23. The Whole XP Team Testers Interaction Designers Project Manager Stakeholders Users Architects Product Manager Programmers

24. XP Project

25. XP Project Iteration

26. XP Project Development

27. XP Project Coding

28. Questions

29. Contact Me ... V i k a s H a z r a t i [email_address]