A Quick Summary of the November 2020 Scrum Guide Update
On November 18th, 2020 a new version of the Scrum Guide was published. The updated version of the Scrum Guide is more succinct, flexible, and direct. To download a PDF version of the November 2020 Scrum Guide click here.
While I encourage everyone to read the updated November 2020 Scrum Guide, in this blog post I’ll be pointing out some of the key changes made in this most recent update and explaining what these changes mean, in my opinion, for the overall Scrum framework.
New Definition
2017 Scrum Definition: [Scrum is] a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
2020 Scrum Definition: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
The new Scrum definition puts an emphasis on outcome over output and no longer mentions the word product; these changes help to combat some of the common misconceptions about Scrum including that it’s meant to increase productivity and that the framework only applies to product development projects.
No Sub-Teams
While the developers within a Scrum team used to be referred to at the “Development Team” they are now simply referred to in the Scrum Guide as Developers. Eliminating the term Development Team from the Scrum Guide makes it so that no sub-teams exist within the Scrum framework, instead there is just one Scrum team.
“Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal.” — The Scrum Guide, November 2020
Emphasis On The Scrum Values
The updated version of the Scrum Guide emphasizes the need for people to embody the five Scrum values in order for Scrum to be successful.
“Successful use of Scrum depends on people becoming more proficient in living five values: Commitment, Focus, Openness, Respect, and Courage.” — The Scrum Guide, November 2020
Self-Managing Instead of Self-Organizing
In the November 2020 edition of the Scrum Guide, Scrum Teams are described as being self-managing rather than self-organizing.
2017: “Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all the competencies needed to accomplish the work without depending on others not part of the team.”
2020: “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.
Accountabilities
Instead of roles, the newest update to the Scrum Guide defines a Scrum team as being made up of three specific accountabilities: the Developers, the Product Owner, and the Scrum Master.
“Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.” — The Scrum Guide, November 2020
Click here for a detailed description of each of the three accountabilities.
Scrum Masters are Leaders Who Serve Rather Than Servant-Leaders
To better clarify the accountabilities of the Scrum Master, the newest version of the Scrum Guide refers to Scrum Masters as leaders who serve rather than servant-leaders. A servant-leader is often misunderstood as being someone who acts as a scribe, secretary, or other administrative role. The term leader who serves clarifies the fact that Scrum Masters lead by serving the Scrum Team, Product Owner, and organization rather than by being their servant.
“Scrum Masters are true leaders who serve the Scrum Team and the larger organization.” — The Scrum Guide, November 2020.
Elimination of the Three Daily Scrum Questions
While answering the famous three questions — What was accomplished yesterday? What do you hope to accomplish today? Do you have any impediments? — can still be useful for some teams, these three questions have been removed from the Scrum Guide. Why? The three questions stated in pervious versions of the Scrum Guide were always suggestions however, many teams became trapped by these three questions. Eliminating the three questions offers teams more flexibility with their Daily Scrums, further enabling them to choose their own format that best helps them plan for the day rather than feeling the need to follow a prescribed script that may not be as affective.
Three Clear Commitments
The November 2020 version of the Scrum Guide defines three Scrum artifacts each with a corresponding commitment.
Artifact — Commitment
Product Backlog — Product Goal
Sprint Backlog — Sprint Goal
Increment — Definition of Done
The Product Goal is a new term and is defined as “a future state of the product which can serve as a target for the Scrum Team to plan against.” For more information about the Product Goal, what it is, and what it means, click here.
While the Sprint Goal and Definition of Done were both part of the previous version of the Scrum Guide, the November 2020 update recognizes them, along with a Product Goal, as formal commitments made and adhered to by the Scrum team.
Please take some time to look at the new Scrum Guide. While some of the changes made may seem small and others quite large, each has it’s purpose. I’m interested to know what you think of the latest Scrum Guide update. Leave your thoughts in the comments below!
