Transform: Scrum Vs. Extreme Programming (XP)
Scrum Vs. Extreme Programming (XP)

Transform: Scrum Vs. Extreme Programming (XP)

Scrum Vs. Extreme Programming (XP)

The aim of this series is to present a comparison between Scrum and XP, as sometimes teams mistakenly think that they are using Scrum, when they are actually using XP. The comparison is to show how close they are (whether we are in the IT and software development fields, or working on product development).


Scrum:

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.


Extreme Programming (XP):

Extreme programming is a software development methodology, the goal of which is to satisfy the customer by delivering high-quality, valuable software at small intervals.

Extreme programming is a software development methodology, the goal of which is to satisfy the customer by delivering high-quality, valuable software at small intervals.


VALUES

The Scrum Values:

The Scrum Values
  • Focus

Everyone focuses on the work of the sprint and the goals of the Scrum team

  • Openness

The Scrum team and its stakeholders agree to be open about all the work and the challenges with performing the work

  • Commitment

People personally commit to achieving the goals of the Scrum team

  • Respect

Scrum team members respect each other to be capable, independent people

  • Courage

Scrum Team members have courage to do the right thing and work on tough problems


The Extreme Programming Values:

The Extreme Programming Values
  • Communication

Everyone is part of the team, and we communicate face to face daily. We will work together on everything from requirements to code. We will create the best solution to our problem that we can together.

  • Simplicity

We will do what is needed and asked for, but no more. This will maximize the value created for the investment made to date. We will take small simple steps to our goal and mitigate failures as they happen. We will create something we are proud of and maintain it long term for reasonable costs.

  • Feedback

We will take every iteration commitment seriously by delivering working software. We demonstrate our software early and often then listen carefully and make any changes needed. We will talk about the project and adapt our process to it, not the other way around.

  • Respect

Everyone gives and feels the respect they deserve as a valued team member. Everyone contributes value even if it's simply enthusiasm. Developers respect the expertise of the customers and vice versa. Management respects our right to accept responsibility and receive authority over our own work.

  • Courage

We will tell the truth about progress and estimates. We don't document excuses for failure because we plan to succeed. We don't fear anything because no one ever works alone. We will adapt to changes when ever they happen.

Comparison Between Both Values:

Focus 	Everyone focuses on the work of the sprint and the goals of the Scrum team Openness 	The Scrum team and its stakeholders agree to be open about all the work and the challenges with performing the work Commitment 	People personally commit to achieving the goals of the Scrum team Respect 	Scrum team members respect each other to be capable, independent people Courage 	Scrum Team members have courage to do the right thing and work on tough problems Communication 	Everyone is part of the team, and we communicate face to face daily. We will work together on everything from requirements to code. We will create the best solution to our problem that we can together. Simplicity 	We will do what is needed and asked for, but no more. This will maximize the value created for the investment made to date. We will take small simple steps to our goal and mitigate failures as they happen. We will create something we are proud of and maintain it long term for reasonable costs. Feedback 	We will take every iteration commitment seriously by delivering working software. We demonstrate our software early and often then listen carefully and make any changes needed. We will talk about the project and adapt our process to it, not the other way around. Respect 	Everyone gives and feels the respect they deserve as a valued team member. Everyone contributes value even if it's simply enthusiasm. Developers respect the expertise of the customers and vice versa. Management respects our right to accept responsibility and receive authority over our own work. Courage 	We will tell the truth about progress and estimates. We don't document excuses for failure because we plan to succeed. We don't fear anything because no one ever works alone. We will adapt to changes when ever they happen.

Comparing the two at this stage proves how close they are in value and more will follow.

To Be Continued...

Eslam Farid

Techno Commercial Consultant

2 年

Felt like the same workflow with different definitions of done.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了