Scrum Agile Project Management

Scrum Guide Updated on the 25th Anniversary of the Scrum Framework

Scrum.org and Scrum Inc. have announced that the co-creators of Scrum, Ken Schwaber and Jeff Sutherland, have released the latest iteration of the Scrum Guide, the definitive guide to the Scrum Framework, as we celebrate Scrum’s 25th anniversary. These changes were made with input from the community of Scrum users around the globe.

Scrum is inspired by the work of Hirotaka Takeuchi and Ikujiro Nonaka in “The New New Product Development Game” from 1986 and was later adapted 25 years ago via a presentation at the OOPSLA ‘95 conference. A paper written by Schwaber and Sutherland titled “The Scrum Development Process” was then released based on this presentation. Scrum has been updated over the years starting with the first Scrum Guide release in 2009, but its foundation on empirical process and Lean principles has remained the same.

“Over the years, the Scrum Guide started getting a bit more prescriptive, yet our goal has always been to retain it as a framework and not a methodology. The 2020 version aims to bring Scrum back to its roots, being a minimally sufficient framework,” said Schwaber. “We have also placed an emphasis on eliminating redundant and complex language and focusing on the Team which is required to build trust and uphold the Scrum Values.” “While this version has significant changes, it’s important to remember that Scrum is still Scrum and there is only one Scrum,” said Sutherland. “It is exciting to have witnessed the evolution of how Scrum has been used over the past 25 years. Although the usage of Scrum has grown well beyond software, the key pillars of Transparency, Inspection and Adaptation remain.”

The 2020 version brings together everyone as one team – the Scrum Team. This change eliminates the concept of a separate team within a team. Previous versions had the Development Team within the Scrum Team. The Scrum Team is focused on the same objective, with three different sets of accountabilities: Product Owner, Scrum Master and Developers. “Previous Scrum Guide versions referred to Development Teams as self-organizing, choosing who and how to do work,” said JJ Sutherland, CEO, Scrum Inc. “With more of a focus on the Scrum Team as a whole, the 2020 version emphasizes a self-managing Scrum Team, choosing who, how, and what to work on sharing responsibilities across the entire Scrum Team.”

Other updates include the introduction of the concept of a Product Goal to provide focus for the Scrum Team toward a larger valuable objective. Each Sprint should bring the product closer to the overall Product Goal and likely will evolve as the Scrum Team(s) learn over time.

“The Scrum Team can continue their short-term focus with the Sprint Goal and now also maintain a vision on the overall end state with the Product Goal,” said Dave West, CEO Scrum.org. “Each of the artifacts now contain ‘commitments’ to them. For the Product Backlog, it is the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. They exist to bring transparency, alignment and focus.”

You can read the Scrum Guide for free on https://scrumguides.org/

Be the first to comment

Leave a Reply

Your email address will not be published.


*


This site uses Akismet to reduce spam. Learn how your comment data is processed.