Skip to main content

Scrum Guide 2020 and 2017: A Side-by-Side Comparison

November 18, 2020
This is part #34 of 59 in the series Scrum Guide 2020 Updates

On November 18, 2020 Ken Schwaber and Jeff Sutherland published an update of the Scrum Guide. According to the co-creators, the Scrum Guide 2020 aims at “bringing Scrum back to being a minimally sufficient framework by removing or softening prescriptive language”[1].

To help you see and understand these changes, we created this side-by-side comparison of the Scrum Guide 2020 and the Scrum Guide 2017.

This information was compiled by Johannes Geske who is a Professional Scrum Trainer (PST) at Scrum.org and an agile coach based in Duesseldorf, Germany. His journey in Scrum began in 2005. Johannes is a Scrum Trainer at Amazing Outcomes where he teaches and coaches Scrum to help teams and organizations to deliver greater value to their customers.

  

Summary

Before you dive into a detailed side-by-side comparison, have a look at this summary of what has changed and – equally important – was hasn’t changed.

 

What hasn’t changed:

In a nutshell, Scrum is still Scrum. Scrum is still a lightweight framework to solve complex problems and deliver value. Scrum is still about a cross-functional team of people collaborating closely with one another and their stakeholders. As a team, they create and deliver valuable and useful Increments every Sprint.

 

What has changed[2]:

  • Less prescriptive, simpler language and removal of software-specific terminology.
  • Changes to some definitions, e.g., Scrum definition, empiricism, Product Backlog, Sprint Goal, Sprint Backlog, Increment, Definition of Done.
  • Removed (e.g., "Scrum Uses") or reorganized content (e.g., "Measuring Progress toward Goals").
  • Elements added and their relationships clarified, e.g., the "Commitments" Product Goal (new), Sprint Goal and Definition of Done.
  • The concept of a Development Team within a Scrum Team was removed to reduce the potential for dysfunctions between the Product Owner and the Development Team (“us vs. them”) and focus the entire Scrum Team on the same objective[1].
  • A Scrum Team now consists of the Product Owner, Developers, and the Scrum Master. The people doing the work of creating a usable Increment are called Developers.
  • The “entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.” The Developers are accountable for all aspects of creating the usable Increment.
  • The terms "accountable" and "responsible" are used more consistently, and "roles" is replaced by "accountabilities".
  • The Scrum Guide now uses the terms “self-managing” and “self-management” to emphasize that Scrum Teams choose “who, how and what to work on” whereas the Scrum Guide 2017 used the terms “self-organizing” and “self-organization” to describe that Development Teams chose “who and how to do work”.
  • The term servant-leader was removed, and Scrum Masters are now described as “true leaders who serve the Scrum Team and the larger organization”.
  • Sprint Planning now has three topics: “Why is this Sprint valuable?”, is the new first topic.
  • The purpose of events is clarified and the description how to conduct them is less prescriptive.
  • A “Product Goal” is introduced, serving as a target and describing a future state of the product.
  • It is clarified that multiple Increments can be delivered within a Sprint, even prior to the end of a Sprint. Sprint Review is not a gate to releasing value.

 

Side-by-Side Comparison

You can access and read the side-by-side comparison here.
 

Scrum Guide Side-by-Side Comparison

 

License:

This information was compiled by Johannes Geske who is a Professional Scrum Trainer (PST) at Scrum.org and an agile coach based in Duesseldorf, Germany. It is offered under the same license as the Scrum Guide, the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and in summary form at http://creativecommons.org/licenses/by-sa/4.0/. By utilizing this side-by-side comparison, you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution Share-Alike license of Creative Commons.

 

Source:

[1] Scrum Guide Revision History (accessed: 18‑Nov‑2020)
[2] The Scrum Guide 2020 (accessed: 18‑Nov‑2020)

 


What did you think about this post?

Comments (39)


Amir Syafrudin
03:44 am November 19, 2020

This is excellent, but why is the comparison contains "July 2020"? Shouldn't it be November 2020?


Johannes Geske
07:07 am November 19, 2020

November is correct. We fixed it. Thanks for bringing it up.


nick b
09:51 am November 19, 2020

Hi, Thanks for the update. While the PDF copy of the 2020 update is correct, the web copy (https://www.scrumguides.org... appears to be pointing at the 2017 version still.


Johannes Geske
10:18 am November 19, 2020

I had the same experienced. What helped was deleting the browser cache. Afterwards it showed the 2020 Scrum Guide.


nick b
11:05 am November 19, 2020

Thanks, Johannes - that worked!


Mighty Sashiman
12:16 pm November 19, 2020

Hi, I am about to begin my journey learning scrum and getting PSPO1 certification. So might as well learn from the 2020 revision. Will I have to wait until 2021 to pass 2020 version of the PSPO1 certification or is the new version of the certification test (and practice test files) already available? Thanks in advance


Johannes Geske
12:57 pm November 19, 2020

All Assessments and Classes will be based on the previous version (2017) through January 9th 2021.


Siva Rama Krishna Bhuma
03:04 pm November 20, 2020

There is one change regarding the service of Scrum Master regarding removal impediments.
Scrum Guide now mentions “Causing the removal of impediments to Scrum team’s progress” whereas the Scrum Guide 2017 mentions “Removing impediments to the Development Team’s progress”


Emanuel Dumitru
05:46 pm November 22, 2020

How to renew the current certification PSM I? Should I pay and take new exam to get certified again for current scrum version?


Johannes Geske
07:03 pm November 22, 2020

I recommend to take this question to the forum (https://www.scrum.org/forum... where Scrum.org staff can help you figure out the best course of action depending on your personal goals. But know that Scrum.org certificates do not expire and hence do not require renewal.


adaobimedia
06:26 pm December 1, 2020

Yeah. Why not just go ahead and do PSM II? You'll be trained using the updated Scrum Guide, as long as you take a course after 9th January 2021. You'll also be progressing in terms of your expertise.


Pradeep Soni
03:27 pm December 4, 2020

As per Scrum.org update, even though new version of Scrum guide has released on 18th Nov'20 but still 2017 based edition is valid till 9th Jan'2021. I am planning to appear for PSM-1 exam in Jan'2021 so need your experts advice whether to attempt for 2017 based guide or study based on 2020 new guide ? Please please help to resolve my query.


Henning Möller
11:43 am December 10, 2020

I'm curious. What's the "why" behind removing the term "servant-leader"?


Johannes Geske
08:16 pm December 10, 2020

My humble opinion: The term was replaced by the less prescriptive description "... true leaders who SERVE...". That still includes the idea of servant leadership while at the same time it is more open for alternative concepts and for leaders who serve without seeing themselves as servants.


TARUN MALIK
09:40 am January 9, 2021

Also "Product Definition" is now clearly articulated/defined in 2020 Guide Version - under Scrum Artifacts Section Page 12 - This was not specified in the 2017 Guide Version --------------------

"Product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers.
A product could be a service, a physical product, or something more abstract"


Kate Arms
11:16 am January 11, 2021

My thought: The term servant-leader arose in a historical context in which too many leaders didn't consider the needs of their followers. Over time, it has lead to a vision of leadership in which too many leaders don't provide enough vision and direction. The new language captures the need for both.


Johannes Geske
03:22 pm January 11, 2021

That's an interesting thought, Kate. Thank you for sharing.


Gunes Sayin
09:55 pm January 17, 2021

Thanks for the blog entry and opening this conversation.

After the changes in 2020, who is accountable or has the last say for the following in your point of view?:
1. Release management (my understanding is now the scrum team is accountable)
2. Progress and budget reporting towards Product Goal (my understanding is still the PO is accountable based open assessment I took)
3. Adding new members to the team (my understanding is now the scrum team is accountable but not sure)
4. Key stakeholder satisfaction (my understanding is still PO is accountable but anyone in team can collaborate)
5. Creation or change of Product Goal (my understanding is still PO is accountable)
6. Abondonment of Product Goal (my understanding is now the scrum team is accountable "The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.")

I would love to hear your comments.


Johannes Geske
07:29 pm January 19, 2021

Hi Gunes,

Thank you for asking these great questions. Here's my perspective:

1. If by "release management" you mean the decision whether or not to release, I'd say it's still the Product Owner. My reasoning is that the Product Owner is accountable for maximizing the value of the product. To create value, the product has to be made available to users/customers. If a product requires a release in order to be made available to users/customers, the final say on that decision is part of the Product Owner's accountability to maximize value.

2. I agree with your point of view as the Product Owner is likely the person with the most knowledge about the product value and progress towards the Product Goal.

3. I agree it's the entire Scrum Team that's accountable as adding a new member to the Scrum Team is part of "anything else that might be required [of all product-related activities]", according to Scrum Guide section "Scrum Team", 4th paragraph.

4. I agree, nothing has really changed here.

5. ditto.

6. The Product Goal is IN the Product Backlog, hence the Product Owner is accountable for defining and abandoning it. The entire Scrum Team commits to working towards and fulfilling that goal except it is abandoned.

Take care!

Johannes


Gunes Sayin
03:52 am January 25, 2021

Thank you Johannes. That really helped.
Wish the best for you!
Güneş


Mukul vij
04:31 pm January 26, 2021

I am planning to give psm1 by Jan 31st or in Feb, please suggest that the exam will be based on which version of scrum guide as I found today that many significant changes have been made from the previous version 2017 to that in 2020.


Johannes Geske
04:49 pm January 26, 2021

It will be based on the 2020 Scrum Guide. Good luck.


Mukul vij
05:33 pm January 26, 2021

Thanks for the confirmation


Mukul vij
02:36 am February 4, 2021

I was preparing for psm1 and have certain doubts here 1) who creates increment? Scrum team (2020),development team(2017) 2) who creates dod? Scrum team(2020),development team(2017) 3)events where key stakeholders participate are? Sprint planning, sprint retrospective (2020), spri t retrospective (2017).

Can anyone clarify my doubts??


Johannes Geske
07:38 am February 4, 2021

You'll find the answers to your questions in the Scrum Guide. Some tips:
- regarding your question #1: Distinguish between who's accountable and who's doing the work. Who's accountable for creating a valuable, useful Increment and who's doing the work of creating a usable Increment?
- regarding your question #3: What does the Scrum Guide (2017 or 2020) really say about stakeholders attending Sprint Planning or Sprint Retrospective?


Mukul vij
12:55 pm February 7, 2021

Thanks Joannes.I got the answer. Now I have a doubt that who decides if and when to release the product increment?scrum 2017 says its PO but scrum 2020 doesn't say anything about it


Johannes Geske
12:59 pm February 7, 2021

The Scrum Guide doesn't define who's accountable for that decision. You could argue, however, that the decision whether or not to release the Increment is part of the Product Owner's accountability to maximize the value of the product as the time and frequency with which releases happen impacts product value.


Mukul vij
03:32 pm February 7, 2021

Thank you for clarification


Johannes Geske
03:43 pm February 7, 2021

You're welcome. If you got value from this article and discussion, please consider rating this article on a 5-star scale (above).


Mukul vij
06:15 am February 12, 2021

Hi Johannes, this article was of great help,I have secured PSM1 today with 96.3 %. Thank you.


Johannes Geske
06:36 am February 12, 2021

Congratulations. I'm glad we could help you along the way.


Lily Nguyen
06:55 am February 19, 2021

Congratulations.!!!


Ntang Elad
05:27 pm December 6, 2021

The term servant leader was misleading some teams to see the Scrum Master as someone who serves the team more than lead and this led to some anti-patterns where some teams were using the Scrum master more in a secretarial role, the term was changed to better reflect the fact that Scrum Masters lead teams towards progress from within thus the new term "leader who serves" to emphasize the leadership portion.


Falcon Ener Kise

Johannes Geske
11:26 am October 31, 2024

We've cleaned up our website and the content no longer exists.


Falcon Ener Kise
11:34 am October 31, 2024

Would love to have it back, it was a wonderful clear and visually readable presentation of the differences.

Maybe the page can be given to Scrum.org, which has the reference link published?


Johannes Geske
11:45 am October 31, 2024

Thanks for your feedback. I'll put it on our Product Backlog to bring it back online. It might take a while though. Is there anything specific you'd like to look up?


Johannes Geske
11:49 am October 31, 2024

I almost forgot: You can still access the comparison through our legacy website:
https://legacy.amazing-outcomes.de/en/what-we-offer/agile-resources/comparison-scrum-guide-2020-and-scrum-guide-2017

Hope this helps in the meantime.


Falcon Ener Kise
12:41 pm October 31, 2024

Thanks, I will love that!

I have manually done a search to find what I looket for. But I love to use your page, and especially important for my fellow agile coach-collegueges and me to se the various differences when it comes to change of terms.