Skip to main content

Scrum Guide updates - What would you change?

Last post 03:10 pm October 2, 2020 by Arun C
2 replies
06:34 am September 30, 2020

Soon the updated Scrum will be released. It will be a little bit shorter, only 13 pages.

(https://kenschwaber.wordpress.com/2020/08/30/scrum-guide-2020/)

What would you change and why? What do you think will be changed?

Nils

 

 


08:24 am October 2, 2020
  1. The name of one of the roles, but there's a separate thread for that.
  2. Shorten the description of Sprint Planning. It's very prescriptive, and leaves less room than I'd like for Scrum Teams to find their own way.
  3. Remove the 3 questions altogether from the description of the Daily Scrum. Why should this practice have more prominence than walking the board, or any other technique a self-organizing Development Team may choose?
  4. Replace references to negotiating between the Product Owner and Development Team with a greater emphasis on inspect & adapt. Negotiation can be interpreted to be non-collaborative.
  5. Remove the requirement for "at least one high priority process improvement" to appear on the Sprint Backlog. In my view it was a mistake to add this in 2017. It's overly prescriptive, and an abuse of the Sprint Backlog. Even though it would be a good idea to do this on many occasions, I see no reason why we should constrain the outcome of a Sprint Retrospective to something that has to be visualized and processed in this way. It enforces delegation to the Development Team of something that was agreed by the Scrum Team.

09:35 am October 2, 2020

+1 to Simon's response on renaming the role. A Developer is not referred to as a "Code Master" or "Development Master" either.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.