Scrum co-creators Ken Schwaber and Jeff Sutherland are making new updates to The Scrum Guide to promote flexibility and clarity within the Scrum framework. The updated guide will now clear up common Scrum miscommunications about the framework, and provide a better understanding of Scrum inspection and adaptation.
“As new technologies and practices have evolved over time, a misconception that Scrum is rigid has arisen and these changes will resolve that,” said Schwaber. “Scrum is truly an empirical process that is not prescriptive and is adaptable by the teams using it. You’ll no longer find the words ‘there are no exceptions’ in this guide and with that comes the clarity that many releases can occur during a Sprint. We look forward to how the community will embrace this update.”
The Scrum Guide is Schwaber and Sutherland’s definitive description of the Scrum methodology. According to the guide, Scrum is a framework used to “address complex adaptive problems, while productively and creatively delivering products of the highest possible value,” according to the guide. The guide has not been updated since July 2016, when Schwaber and Sutherland added five values of Scrum to the guide: courage, focus, commitment, respect and openness.
The guide includes a new “Uses of Scrum” section that explains what Scrum has, and can be, used for. Scrum was initially focused on software complexity, yet the co-creators have found it works in a majority of business and technology areas such as integrated, embedded and advanced technologies.
In addition, the guide clarifies that “a ‘Done’ increment is required at the Sprint Review,” and “An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal. The increment must be in useable condition regardless of whether the Product Owner decides to release it.” It further details what a daily Scrum is, and updates the meaning of an increment.
The changes were based on community feedback, and made at the discretion of Schwaber and Sutherland.
“First and foremost, we want to thank our extended team of Scrum practitioners, who offer valuable insight into the day-to-day implementation of The Scrum Guide,” said Sutherland. “Without their input, The Scrum Guide would not be the living document that it is. Scrum continues to evolve in its use in delivering value to any industry.”