If you’ve not had a chance to view this webinar which explains changes to the 2017 Scrum Guide, I offer this brief review.
The Scrum Guide by Ken Schwaber and Dr. Jeff Sutherland was first formally presented in 1995 at an OOPSLA Conference in Texas. The first version of the Scrum Guide was released in 2010 as the official “Body of Knowledge of Scrum.” This was posted in a neutral open space for anyone to access, and the authors received tons of feedback.
The 2017 Scrum Guide, according to Schwaber, provides a minimal approach to Scrum to enable people to use it, but not be restrained by it. He adds that this 2017 version was motivated by people’s feedback and input.
So what’s new?
The uses of Scrum – Scrum has expanded far beyond IT
Refined role of the Scrum Master – SM is responsible for promoting and supporting Scrum as defined in the Scrum Guide, by helping everyone understand Scrum theory, practice, rules and values; and, as much as is possible, within the culture of the organization, and according to the SM’s organizational and political skills, and patience. “It’s a very tough job.” (Schwaber)
Clarifying the purpose of the Daily Scrum – The daily scrum has been a problem area; it’s more than reporting your action; it’s about replanning and refocusing, and moving the backlog to “done.”
Time boxes – only require a maximum length; clarity has been added around time boxes using the words “at most” to remove questions that events have to be a certain length.
Sprint Backlog – includes feedback from the sprint Retrospective; it’s about continuous improvement; the sprint backlog makes visible all the work that the development team identifies to meet the sprint goal; it includes at least one high priority process improvement identified in the previous Retrospective meeting. (The authors struggled with this, worried it would be too prescriptive.)
Schwaber and Sutherland also address common misconceptions in the webinar. One topic they emphasize is that Scrum is not only relevant to software delivery, but can be used in many different domains, from products to services.
They also address the idea that releases may be delivered at any time, not just at the end of the sprint. Sutherland calls this “continuous deployment.”
Another misconception the authors discuss is whether or not Scrum and DevOps are competitive.
Jeff Sutherland states:
“The biggest problem in attempting Scrum is not using every part of it.” The parts are interlocking, and all need to be synchronized. In other words, use all of Scrum!
Scrum may be needed more than ever. The rate of change in the world has accelerated beyond being linear. The authors outline three universal dimensions of change:
People – including markets, population, distribution, social and religious organizations
Technology – !
Mother Earth – including climate, desertification, oceans, etc.
Changes in these three areas cause great cultural instability. The sweet spot of Scrum is vision with a team of people who can create something new and needed!
The webinar contains valuable nuggets of information, plus it’s fascinating to watch these two innovators. Enjoy!
If you find this useful, please consider contributing with our
“Value for Value” model.