| Teamwork Iterations | 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. |
| Flexibility in Timelines | Scrum models do not allow changes in their timeline or their guidelines. | Extreme Programming allows changes in their set timelines. |
| Emphasis | Scrum emphasizes self-organization. | Extreme Programming emphasizes strong engineering practices |
| Development Sequence | 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. |
| Framework Adaptation | 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. |
| Software Engineering Practices | 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. |
| Engineering Methods | 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. |
| Feature Prioritization | 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. |
| Task Prioritization | 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. |
| Flexibility in Task Prioritization | 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. |
| Core Values | Values-
| Values-
- Communication
- Simplicity
- Feedback
|
| Customer Involvement | Customer involvement is less in the project. | Customer involvement is more in the project. |