Scrum Guide Revisions 2017

The Scrum Guide revisions November 2017

• Highlighting that the framework can be applied beyond software is a nice addition.
• The additional information and rewording for the Scrum Master role will be helpful to some.
• Daily Scrum changes are a great step in a positive direction. Promoting a conversation over the three question format (3QF) or walking the board has been a challenging sell to many.
• The need to further reiterate the definition of a time-box highlights one of many symptoms exemplifying that Scrum, for many, is not "Simple to understand" as advertised. :-)
• The requirement to have "at least one high priority process improvement identified in the previous Retrospective meeting" on the Sprint Backlog creates some issues as it does not align with the definition of the Sprint Backlog.
• It is not a Product Backlog Item (PBI).
• It is not a part of the plan for delivering the Increment and realizing the Sprint Goal.
• It is not a forecast of functionality.
• The Sprint Backlog belongs solely to the Development Team therefore so does this process improvement item.
• Changes are inspected and adapted during the Daily Scrum (for Development Team only).
• Development Team works through the plan.
• Only the Development Team can change its Sprint Backlog during a Sprint.
• It is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint.