According to my knowledge there are four main differences between Scrum and XP:

  1. Scrum teams typically work in iterations  also called sprints that last from two weeks to one month long. XP teams typically work in iterations that are one or two weeks long.
  2. Scrum teams do not allow changes in their sprints. Once the sprint planning meeting is completed and a commitment made to delivering a set of product backlog items, that set of items remains unchanged through the end of the sprint. XP teams are much more amenable to change within their iterations. As long as the team hasn’t started work on a particular feature, a new feature of equivalent size can be swapped into the XP team’s iteration in exchange for the unstarted feature.
  3. Extreme Programming teams work in a strict priority order. Features to be developed are prioritized by the customer  also called Scrum’s Product Ownner and the team is required to work on them in that order. By contrast, the Scrum product owner prioritizes the product backlog but the team determines the sequence in which they will develop the backlog items. I’ve never seen a Scrum team not choose to work on the highest-priority item. And a Scrum team will very likely choose to work on the second most important. However, at some point one of the high priority items may not be a good fit for the sprint being planned—maybe a key person who should work on it will be swamped by work on higher priority items. Or maybe it makes sense to work on a slightly lower priority item (let’s say #10 on the product backlog instead of #6) because the team will be working in the code where #10 would be implemented.
  4. Scrum doesn’t prescribe any engineering practices; XP does. I love the XP engineering practices, particularly things like test-driven development, the focus on automated testing, pair programming, simple design, refactoring, and so on. However, I think it’s a mistake to say to the team “you’re self-organizing, we trust you, but you must do these specific engineering practices….” This sends a mixed message to the team that causes confusion. I love the XP practices but don’t like mandating them. I want teams to discover the value on their own.
  5. The above mentioned differences are only to my knowledge on agile methodologies.
You would..
Share
Related Documents
  1. [Free] XPCGI : Agile CGI application testing tool (1441)
  2. Agile guide and article from extremeplanner (866)
  3. [Ebook] Kanban and Scrum : Making the most of both (5216)
  4. [Free] Agilo : Agile testing & scrum management tool (2577)
  5. [Ebook] Scrum and XP from the Trenches (3634)
  6. devagile : Agile Software Testing & Development Web site (925)
  7. [Video] Agile Testing Environment (923)
  8. Scrum Process (Agile Testing) (1799)
  9. Agile Testing vs XP (Extreme Programing) vs SCRUM? (2226)
  10. 2010-08-09, Agile2010 @ USA (954)
  11. Agile software testing articles : Object Mentor (1163)
  12. Patterns of agile development : AgileInjection.com (865)
  13. 2010-11-14, Agile Development Practices East @ USA (1585)
  14. [Intro] Agile Testing by Lisa Crispin and Janet Gregory (4463)
  15. [Webinar] The Agile PMO: Real Time Governance The Agile PMO: Real Time Governance (930)
  16. [Ebook] Agile Estimating and Planning (4929)
  17. Agile Estimating and Planning (2260)
  18. [Webinar] Principles of Agility (944)
  19. [Video] Agile Testing (1133)
  20. [Free] ScrumWorks : Scrum Project Management Tool (2062)