Difference between Scrum and XP

There are two main models of Agile framework namely: Scrum, and Extreme Programming (XP). Scrum Framework: Scrum is the type of Agile framework. It is a framework within which people can address complex adaptive problem while productivity and creativity of delivering product is at highest possible values. Scrum uses Iterative process. Life Cycle of Scrum: 

Extreme Programming (XP): Extreme Programming is one of the most important models of Agile framework. This model emphasizes team-work and customer satisfaction as well. The five basic component of Extreme Programming are:

1. Communication
2. Simplicity
3. Feedback
4. Respect
5. Courage

Life Cycle of Extreme Programming (XP): 

S. No.	Scrum	Extreme Programming (XP)
1.	In the Scrum framework, teamwork in iterations is called Sprint which is 2 weeks to 1 month long.	In Extreme Programming(XP), teamwork for 1-2 weeks only.
2.	Scrum models do not allow changes in their timeline or their guidelines.	Extreme Programming allows changes in their set timelines.
3.	Scrum emphasizes self-organization.	Extreme Programming emphasizes strong engineering practices
4.	In the Scrum framework, the team determines the sequence in which the product will be developed.	In Extreme Programming, the team has to follow a strict priority order or pre-determined priority order.
5.	The Scrum framework is not fully described. If you want to adopt it then you need to fill the framework with your frameworks methods like XP, DSDM, or Kanban.	Extreme Programming(XP) can be directly applied to a team. Extreme Programming is also known for its Ready-to-apply features.
6.	Scrum does not put emphasis on software engineering practices that developers should use.	Extreme Programming (XP) emphasizes programming techniques that developers should use to ensure a better outcome.
7.	It requires developers to be conscious of adopting engineering methods to ensure better progress or quality.	It is very strict in adopting engineering methods such as pair programming, simple design, restructuring to ensure better progress or quality.
8.	In the preference of features, demand and priority do not have to be in line with one another.	In the preference of features, the demand corresponds to the priority.
9.	In scrum, the scrum master asks the owner of the product to prioritize the tasks according to their requirements.	In XP, customer decides the job priorities being the owner of the product and then analyses the releases.
10.	The tasks are prioritized by the owner of the product but with the flexibility that the priorities can be changed later on by the development team if required.	The tasks are prioritized by the customer and the task priorities cannot be changed by the development team.
11.	Values- Openness Focus Commitment	Values- Communication Simplicity Feedback
12.	Customer involvement is less in the project.	Customer involvement is more in the project.