XP Explained

2,505
-1

Published on

Vikas's presentation on "XP" at the at the Intro to Agile workshop on 28th June 2008

Published in: Economy & Finance, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,505
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
63
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

XP Explained

  1. 1. Agile NCR Workshop Method Overview eXtreme Programming V I K A S H A Z R A T I June 28' 2008
  2. 2. Know your presenter <ul><li>Practising XP and Scrum for last 3 years </li></ul><ul><li>Board member of Agile Software Community of India </li></ul><ul><li>Agile Community editor on InfoQ </li></ul><ul><li>Published articles on The Server Side, Agile Journal </li></ul><ul><li>Personal blog site http://vikashazrati.wordpress.com </li></ul>
  3. 3. What is XP? <ul><li>XP is a mindset change! </li></ul><ul><li>XP is a philosophy of software development based on well laid out values, principles and practices. </li></ul><ul><li>Goal of XP is outstanding software development at lower cost, with fewer defects, high productivity and much higher return on investment. </li></ul>
  4. 4. Why XP? <ul><li>Another methodology but why? </li></ul><ul><ul><ul><li>Social Change- Giving up defences </li></ul></ul></ul><ul><ul><ul><li>Based on Excellent programming techniques, clear communication and teamwork </li></ul></ul></ul><ul><ul><ul><li>Lightweight – only do whatever adds value to the customer </li></ul></ul></ul><ul><ul><ul><li>Addresses constraints in software development </li></ul></ul></ul><ul><ul><ul><li>Can work with teams of any size </li></ul></ul></ul><ul><ul><ul><li>Adapts to rapidly changing requirements </li></ul></ul></ul>
  5. 5. Core Components Values Practices Principles
  6. 6. The Five Core Values of XP Communication Simplicity Feedback Courage Respect
  7. 7. XP Principles Humanity Economics Mutual Benefit Improvement Opportunities Reflection Diversity Flow Accepted Responsibility Baby Steps Failure Quality
  8. 8. Practices Primary Corollary
  9. 9. Primary Practices <ul><li>Sit Together </li></ul><ul><li>Whole Team </li></ul><ul><li>Informative workspace </li></ul><ul><li>Energized work </li></ul><ul><li>Pair Programming </li></ul><ul><li>Stories </li></ul><ul><li>Weekly Cycle </li></ul><ul><li>Quarterly Cycle </li></ul><ul><li>Slack </li></ul><ul><li>10 minute build </li></ul><ul><li>Continuous Integration </li></ul><ul><li>Test First Programming </li></ul><ul><li>Incremental Design </li></ul>
  10. 10. Sit Together / Whole Team
  11. 11. Sit Together / Whole Team
  12. 12. Informative Workspace
  13. 13. Informative Workspace
  14. 14. Energized work <ul><li>Work only as many hours as productive </li></ul><ul><li>Ideally 40 hours a week </li></ul><ul><li>Programming productivity is seen to be 4-5 hours a day </li></ul>
  15. 15. Pair Programming
  16. 16. Pair Programming
  17. 17. Stories <ul><li>Units of customer visible functionality. </li></ul><ul><li>Should be on the story wall for everyone to look at. </li></ul>
  18. 18. A Story
  19. 19. Story Life Cycle
  20. 20. Weekly / Quarterly Cycles
  21. 21. More... <ul><li>Slack </li></ul><ul><li>Ten Minute Build </li></ul><ul><li>Continuous Integration </li></ul><ul><li>Test First Programming </li></ul><ul><li>Incremental Design </li></ul><ul><ul><ul><li>Do the simplest thing that </li></ul></ul></ul><ul><ul><ul><li>can possibly work </li></ul></ul></ul><ul><ul><ul><li>Refactor </li></ul></ul></ul>
  22. 22. The Whole XP Team <ul><li>Emphasis on the “Whole Team” </li></ul><ul><li>Collaboration and collocation </li></ul>
  23. 23. The Whole XP Team Testers Interaction Designers Project Manager Stakeholders Users Architects Product Manager Programmers
  24. 24. XP Project
  25. 25. XP Project Iteration
  26. 26. XP Project Development
  27. 27. XP Project Coding
  28. 28. Questions
  29. 29. Contact Me ... V i k a s H a z r a t i [email_address]

×