In order to simplify the Guide further and make it reflect the framework as lightweight, Ken Schwaber and Jeff Sutherland have removed some unnecessary content, as follows: This made it available for a much wider audience since, thanks to those simplifications, it has now less than 13 pages.Ĭontact Us → What was removed from the Guide? The new Scrum Guide eliminated complex statements, redundancy and removed any inference to the IT (eg. The main goal was to eliminate the concept of separation within the team and avoid the, sometimes difficult, cooperation between the PO and development team. It now describes sets of accountabilities for the Product Owner, Scrum Master as well as Developers, instead of focusing on the particular roles. In the 2020 version, the Guide puts a great emphasis on the one common goal the team should be focused on. It was achieved by, for example, the deletion of the three Daily Scrum Questions, softening the language around the retrospective items in the Sprint Backlog or shortening the Sprint Cancellation section. The latest version aims to bring it back to being a rather minimalistic framework. Over the years, the Scrum Guide started getting more prescriptive as lots of new elements were added and described. So what exactly has changed? How is the 2020 Guide different from its predecessor? Let’s dive deeper. Want to learn more about Key Changes of Scrum Guide 2020? However, Scrum is still Scrum and this is what is most important. The structure of the Guide has changed and the prescriptive language and practices have been removed in order to create a more lightweight and easy to comprehend framework. If you are familiar with the 2017 version you may be surprised how different the recent version is. The Scrum Guide has been translated to over 30 languages and can be read and downloaded from the official website. Thanks to the contributions from the community, specialists and founding fathers many updates have been introduced to make the Guide even more clear and transparent. It contains a clear definition of the methodology, descriptions of the roles, events and artifacts as well as the rules that bind them together. The Scrum Guide is developed and maintained by the founders of Scrum themselves, since the day it was first published 25 years ago - Ken Schwaber and Jeff Sutherland. In this brief article, I would like to share with you the key changes in the 2020 Scrum Guide and make them easier to understand for a future reference. I was very excited about that because every new version makes it more clear what this methodology is really about and how it can help you achieve your project and business goals.
#Scrum guide 2020 update
On November 18 2020, Ken Schwaber and Jeff Sutherland published an update of the Scrum Guide. Knowing the updated guidelines can help you become an even better leader with the most effective team of people. If you wish to dive deeper into the topic, make sure to visit the post Why Do You Need A Scrum Master? A Report from the Battlefield.Īs a business owner, it is crucial to stay up-to-date with the operating rules and notions within the methodology even if you are not currently employing a Scrum Master. His/her role is to serve as a coach to your team to lead them through the development process smoothly and without unnecessary distractions. Scrum Master is someone your projects need.
0 kommentar(er)
