XP is - as the name suggests - about programming.

Scrum • Definition (Rugby): A Scrum is a way to restart the game after an interruption, • The forwards of each side come together in a tight formation and struggle to gain possession of the ball when it is tossed in among them • Definition (Software Development): Scrum is an agile, lightweight process This focus on delivering working code in a short timeframe means that Scrum and XP teams don’t have time for theories. Scrum is a framework for product development, which is a container where you can add other practices. Extreme programming (XP) is an engineering methodology consisting of practices that ensure top-quality, focused code. The differences between scrum vs XP are quite subtle yet very significant and might have quite an effect on the project undertaken. Most Agile Teams use Scrum as their primary, team-based project management framework. As iterations in Scrum are quite fast, it's quite natural to pick up … XP. There are no reasons why a team should choose between Scrum and XP. They are as under : Development period; Scrum generally works in iterations or sprints which lasts from two to four weeks. XP is much more focussed on programming activities in particular, and prescribes ways in which traditional software engineering practices like TDD, Pair Programming, refactoring, etc. XP on the other hand comes with a set of core practices that could seem overwhelming to the Agile beginner. Scrum on the other hand is about managing projects first of all. They are more focused on the release date of the … Adding XP into Scrum could be a natural path for teams starting out with Scrum … In fact, if you walked in on a team doing one of these processes you might have hard time quickly deciding whether you had walked in on a Scrum team or an XP team. Scrum doesn't have any engineering practices, wrapping and using those at the organization where it is implemented. It combines the power of Scrum project management practices with Extreme Programming (XP) practices.. As described in the Scrum Guide, a Scrum Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. One of the standard questions asked related to Agile is how extreme programming compares with Scrum, as both of them are the most important methodologies of Agile. Since XP and Scrum have the same principles and values in their foundation, they have some common features. There are Scrum Events, which consist of Sprint Planning, the Daily Scrum (aka Daily Standup, in XP), Sprint Review, and Sprint Retrospective. It is hard to recognize if you walked into a team doing involved in this processes. Scrum methodology is mostly concerned about productivity. The differences are often quite subtle, but they are important. Key Differences Between Scrum and XP Development Cycles Here, Henrik Kniberg shares his actual war stories and shows us why Scrum is beneficial for the company and their clients. When these engineering practices are weak, overall productivity is lessened. XP in a Nutshell. XP rules and practices are not easy and the majority of XP rules are non-negotiable. the overhead to a minimum, a fact that benefits CSE development. XP vs Scrum. are taken to “extreme” levels to maximise their value. 不难发现，这四个区别显见的是： Scrum非常突出Self-Orgnization, XP注重强有力的工程实践约束 作者建议， 在管理模式上启用Scrum， 而在实践中，创造一个适合自己项目组的XP(“start with Scrum and then invent your own version of XP.”) 非常不错， 文武之道，有张有弛。