Agile Thinking

Scrum Guide Changes to Expect in the Latest Version

Ken Schwaber and Jeff Sutherland regularly make Scrum Guide changes every few years. They came up with some more in the latest version that came out in 2020. The purpose of their effort was to simplify the guide so that people could access and embrace it more. In this article at Mountain Goat Software, Brian Milner shares the Scrum Guide changes you can see in the 2020 version.

2020 Scrum Guide Changes

The latest Scrum Guide changes are not significant enough to uproot your team’s current working style. You might need to use different terminology or respond differently to activities. Some key elements have been removed, so the guide seems thinner. If you had followed the 2017 version of the manual, it will be easier for you to drop the obsolete principles. However, if you start with the 2020 version, keep the 2017 edition handy to better understand the latest Scrum Guide changes. Now, let’s discuss the adjustments:

Ownership Over Roles

Most people considered the term ‘role’ as a job position. The term is now replaced by ‘accountability’ to clarify that. For instance, you do not have to hire a candidate with a ‘Scrum Master’ title in the resume. You can appoint the project manager of your existing team as a Scrum master.

Scrum Team Over Dev Team

Having a development team in a scrum team felt like having a ‘team within a team’. So, the authors have removed the concept of the development team and replaced it with developers. So, there are three accountabilities—‘scrum master, product owner, and developers’.

True Leader Over Servant Leader

One of the Scrum Guide changes is removing servant leadership requirements from scrum master roles. You instead should call them true leaders. The reason for dropping ‘servant’ or ‘master’ from the titles might be to remove the sense of being deemed lower to someone.

More Goals

You will have product goals for product backlogs, sprint goals for sprint backlogs, and a definition of done for increment. These ‘commitments’ might not make much difference except that you will think more about product goals than product vision.

Added Sprint Planning Questions

You used to have to answer two questions for sprint planning—what and how. For instance, ‘WHAT are we going to do and HOW are we going to accomplish it?’ Now, you will have to answer three questions—why, what, and how, including ‘Why is this Sprint valuable?’

To view the original article in full, visit the following link:

Related Articles

Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.