What Has Changed with the Scrum Guide 2020? – PART I
The Scrum Guide, the previous version of which was published in 2017, which contains the definition of Scrum and says that the definition of Scrum includes roles, events, artifacts and the rules that hold them together, was renewed on November 18, 2020.
The Scrum Guide, the previous version of which was published in 2017, contains the definition of Scrum and says that the definition of Scrum includes roles, events, artifacts, and the rules that hold them together, was renewed on November 18, 2020.
In the Scrum Guide 2020, which defines Scrum, which has been developing with the contributions of its users for 25 years, not only in the world of software development but in all areas with complex work, the emphasis on roles, activities, works, and rules is no longer included when describing the Purpose of the Scrum Guide.
For many years, Scrum has been used outside of IT for value generation with adaptive solutions for complex problems. This de facto situation is pointed out by the Scrum Guide 2020, which eliminates complex expressions and no longer includes words that focus on software development.
A language that is much simpler and appealing to a wider audience beyond the software development world is used; the new guide, which is much more comprehensive and yet simple, is stated that each element that makes up the framework serves a specific purpose necessary for the value and results achieved with Scrum.
Furthermore, we see that the focus is on the purpose of being more inclusive than the sentences of “At Scrum, we use the word “Developers” to address a particular role, not to exclude others, but to simplify and make it more inclusive. If you derive value from Scrum, you can consider yourself in Developers.”, included in the Purpose of the Scrum Guide.
Scrum, which was described as “simple, easy to understand, difficult to manage” in its 2017 version, is defined as a loop where “the Product Owner lists the work in the Product Backlog, the Scrum Team turns the selected work into a valuable piece of product, the team and partners review the results and correct for the next Sprint and these are repeated.” The necessity of a Scrum Master to keep this environment alive is also emphasized.
In the Scrum Guide 2020, we see that the Use of Scrum title is no longer available. The absence of this title once again made us feel that the new Scrum Guide is less restrictive, more inclusive and simpler.
When we came to the title of Scrum Theory, the first thing that caught our attention was the use of the concept of Lean, which was not included in the Scrum Guide 2017. Lean is described as follows in the Scrum Guide 2020: “Lean thinking reduces waste and focuses on what matters” . With this addition, we see the importance given to simplification.
Transparency: Scrum Guide 2017 talked about making important parts of the process visible to those responsible for the output and value produced. In the new version, it is stated that the process and the work must be visible to those who do the work and those who benefit from the work done. We have experienced the importance of this expression by encountering the need that team members and those who benefit from the work of team members have the same understanding of the process and everything about the work. What is expressed in the Scrum Guide 2020 and the subjects included in these statements once again underline the importance we must attach to building common understanding and to this end, maintaining radical transparency.
Observation: Whereas Scrum Guide 2017 previously talked about the observation of Scrum artifacts and progress towards the Sprint Goal, in the new version, the observation of progress towards the agreed goals (Product Goal, Sprint Goal, Done Definition) together with the Scrum artifacts is emphasized.Adaptation: The Scrum Guide 2020 highlights the importance of empowering those involved and being able to manage themselves (previously, self-organization was emphasized) for ease of adaptation.
Transparency, the link between observation and adaptation, and the need for each other are also emphasized when describing the carrier columns of experimentation in the new version. “Observation without transparency is misleading and wasteful. […] Observation without adaptation is considered meaningless. […] A Scrum Team is expected to adapt as soon as it learns something new through observation.”While Scrum Guide 2017 defines the roles of Product Owner, Scrum Master and Development Team, roles are not mentioned in the new version and PO, SM and Developers are defined with their responsibilities.
The Development Team as a role is no longer included under the Scrum Team title. It is described as a single team, consisting of the Product Owner, Scrum Master and Developers. The Product Target that came into our lives with the Scrum Guide 2020 is also emphasized here. It defines the Scrum Team as professionals who focus on one product goal at a time.
One of the most important qualifications stated for the Scrum Team that draws attention is the self-management of the team (a Product Owner, a Scrum Master and Developers). What is meant by the team’s self-management is explained as “the team decides who will do what, when and how”.It is said that the Scrum Team will typically consist of 10 people or less, as the concept of the Development Team is no longer in our lives.
While Scrum Guide 2017 describes the roles, Product Owner, Development Team and Scrum Master progress in order, Scrum Guide 2020 defines the responsibilities of Developers, Product Owner and Scrum Master, in that order.
Developers: The definition of the Development Team, which was self-organized and took responsibility as a team, is disappearing from our lives. Instead, Developers, defined as one of the special responsibilities within the self-managed Scrum Team, who hold each other accountable as professionals, come into our lives.
Product Owner: We see that the Product Owner’s responsibilities include establishing the Product Target and communicating this target.Scrum Master: The Servant Leader description for the Scrum Team is not included in the Scrum Guide 2020. Whereas the concepts of “self-management”, “Product Goal” that came into our lives and the Scrum Artifacts with a stronger emphasis are being defined, the areas of responsibility of the Scrum Master are also developing to include them, together with the "Definition of Done", which is referred to as Commitment to Increment. The Scrum Master’s services include coaching the Scrum Team in self-management, helping the Scrum Team focus on creating value to meet the Definition of Done, helping the Product Owner define the Product Goal.
Comment(s)