Yesterday (November 7) Ken Schwaber and Jeff Sutherland presented the Scrum Guide revision.
They started with a brief history of Scrum and explained the essence of Scrum followed by the main part of this webinar. The Scrum Guide 2017 is updated on responses to input from Scrum users.
The following topics were discussed:
- Uses of Scrum (beyond IT)
- Refined the role of the Scrum Master (promoting and supporting Scrum by helping everyone understand Scrum theory, practices, rules, and values, within the culture of the organization)
- Daily Scrum is for inspection and adaption to ensure progress towards the sprint goal (how can we move the backlog to done?)
- Time-boxes cary a maximum length (the words “at most” are added)
- Sprint Backlog includes feedback from the sprint retrospective. To ensure continuous improvement, the sprint backlog must contain at least one high priority process improvement identified in the previous retrospective meeting).
In the last part of the session some common misconceptions were addressed:
- Is Scrum only relevant to software delivery? No
- Can I release before the end of the sprint? Yes
- What about DevOps? Already after the first sprints you have to prove the product is viable and will produce value. This asks for an operational environment.
To download the new Scrum guide: www.scrumguides.org
To watch the video of the Scrum Guide Revision Webinar: video of the Scrum Guide Revision Webinar, where you can download the used presentation too.
Sent from my iPad