Devops for Growth

In a nutshell, the changes are: 

• Less prescriptive
• One team focused on one product
• Introduction of the Product Goal 
• Artifact commitments, 
• Change from self-organized to self-managed
• Three Sprint Planning topics
• A general simplification of language 

Role replaced by accountabilities

Many people mistakenly thought that the Scrum roles were job titles. With the 2020 release of the Scrum Guide, the focus on “accountabilities” rather than job descriptions has been emphasized by removing the word “role.” However, it is a direct replacement and there are still many places where the use of the word “role” will still make sense when describing these accountabilities. 

For a more detailed description of this change please read the blog

“Self Organized” replaced with “Self Managed”

For many people these terms are synonyms. The change was inspired by the idea that the Scrum Team should take ownership of the management tasks necessary to deliver a useful, valuable increment. The use of the word “management” highlighted this focus. However, there remains a significant amount of valuable content that uses the term “self-organized. 

For a more detailed description of this change please read the blog. 

Servant Leadership  

The 2017 guide used the term “Servant Leadership” to describe the style of leadership that serves Scrum Teams well. This idea is still valid, however, the 2020 Scrum Guide places more emphasis on leadership, removing the potential misinterpretation that Scrum Masters are servants first and leaders second. Understanding the idea of servant leadership is still valuable when using Scrum. 

Development Team vs. Developer

This change has the biggest impact on the content associated with Scrum. Development Team was a key role within the Scrum Framework which was replaced by the term Developer. This meant that the team (or shared accountabilities) went to the Scrum Team and individual accountabilities are held by the Developer. 

Main removed elements:

• The prescriptive elements of the Sprint Review.
• The detailed outcomes defined in the purpose of the Sprint Retrospective. 
• The improvements that will be implemented in the next Sprint from the Retrospective.
• Refinement usually consumes no more than 10% of the capacity of the team. 
• How to monitor progress towards the goal in Product Backlog.
• The use of an organization’s “Definition of Done”.  
• The three questions for the Daily Scrum. 
• Meeting after the Daily Scrum for detailed discussions, replanning, etc.