• Skip to main content

d.c.m.e.

The Dutch Company that Makes Everything

  • Customer Portfolio
  • Speaker Profile
  • About Me
  • Contact
  • Blog

Scrum Guide v. 2020 – Release Notes

posted on November 18, 2020

www.scrumguides.org

On November 18 2020, a new version of the Scrum Guide has been released. This article aims to inform people in less than 2 minutes what has changed.

The 2020 Scrum Guide revision:

  • Does not change Scrum. You do not need to change the way you work.
  • Changes and omissions are a shift in nuance and result from making the guide more simple and concise.
  • Better reflects the reality of Scrum implementations.
  • Offers more freedom for contextual implementation variances by being less prescriptive. 
  • Uses simpler language for a wider audience without referencing to IT work.
  • Brings Scrum back to being a minimally sufficient framework.
  • Included the possible uses of Scrum in the guide’s introduction.
  • Makes one Scrum Team focus on the same objective.
  • Refers to accountabilities rather than roles in the Scrum Team.
  • Removed the Development Team in favour of Developers.
  • Abandoned the concept of “servant leadership” for Scrum Masters.
  • Introduces the Product Goal to focus the Scrum Team on a larger objective.
  • Provides Commitments as an identity for the Sprint Goal and Definition of Done.
  • Promotes self-management over self-organization.
  • Removed the 10% capacity claim for refinement activities. 
  • Adds a third Sprint Planning topic “Why”, referring to the Sprint Goal.
  • Removed all references to estimates and requirements.
  • No longer describes monitoring progress towards goals in a separate section.
  • No longer prescribes using the three questions in the Daily Scrum. 
  • No longer details the elements of the Sprint Review.
  • Moves the decision to release the Increment to the whole Scrum Team rather than the Product Owner.
  • No longer describes detailed outcomes as the purpose of the Sprint Retrospective. 
  • Dropped the obligation to have improvements from the Retrospective implemented in the next Sprint.
  • Puts less emphasis on cancelling a Sprint by removing the separate section for it.

Read the full guide here: https://www.scrumguides.org/

Scrum is still Scrum.
Scrum on!

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Home
  • Contact
  • Terms and Conditions
  • Koos Coach
  • Scrum Cards

© 2025 Roland Flemm
made with by Studio nulelfzeven