A great article on how the DOD applies now to the Scrum Guide and the Scrum Team. The emphasis that the entire Scrum Team creates the DOD prevents from misunderstandings in the future, as I’ve personally witnessed in the past.

https://www.scrum.org/resources/blog/2020-scrum-guide-definition-done-created-scrum-team

How do Product Goal and Release Goal relate? Is the Product Goal the product vision and Release Goal is helping us to define relevant Sprint Goals to achieve the Release Goal?

Good reads about the Product Goal: https://www.scrum.org/resources/blog/scrum-guide-2020-update-introducing-product-goal

https://www.scrum.org/resources/blog/product-goal

Several articles on Scrum.org describe and discuss the 2020 changes: https://www.scrum.org/scrum-guide-2020

Things that have been removed:

• The prescriptive elements of the Sprint Review.
• The detailed outcomes defined in the purpose of the Sprint Retrospective.
• The improvements that will be implemented in the next Sprint from the Retrospective.
• Refinement usually consumes no more than 10% of the capacity of the team.
• How to monitor progress towards the goal in Product Backlog.
• The use of an organization’s “Definition of Done”.
• The three questions for the Daily Scrum.
• Meeting after the Daily Scrum for detailed discussions, replanning, etc

Source: https://www.scrum.org/resources/blog/scrum-guide-2020-update-what-has-been-removed

While the SM worked closely with the Dev team to support them creating the DOD, with this new emphasis on entire Scrum Team the potentially odd moments of ownership and contribution from the SM/PO to the DOD are less likely to happen.

This is where the new Scrum Guide 2020 generates some leverage for Coached and the Testing Engineers (as part of DEV). Testing/Quality is everyone’s job on the Scrum Team. Including all DEV, PO and SM.