Community Blog

In this vlog, Joshua Partogi shares insight on how to create the Product Goal.

November 2020 was the launch of the Scrum Guide update. It seems like only yesterday but was over 3 months ago...

Here are some simple examples of Product Goals, Sprint Goals and the relationship between them.

Le Product Backlog est une liste ordonnée et évolutive de tous les travaux jugés nécessaires par le Product Owner pour créer, publier, maintenir et entretenir un produit.

L’apport le plus notable de la version 2020 du Guide Scrum est l’ajout d’un Product Goal au Product Backlog. Cette nouvelle caractéristique du Product Backlog vient accroître la transparence de cet artéfact Scrum.

In the 2020 Scrum Guide Ken and Jeff introduces the idea of the Product Goal. The Product Goal is a commitment to ensure transparency and focus against progress.

Four PST's (Andy Hiles, Steve Trapps, Sjoerd Kranendonk and Jasper Alblas) discuss the changes in the 2020 version of the Scrum Guide. You can watch the video above.

The following are the changes that struck me the most in the 2020 Scrum Guide...

In the 2020 Version of the Scrum Guide, the commitments were introduced for each artifact. These then became an element of Scrum; in that they need to be used to gain the maximum value that the Scrum Framework offers. They were always part of a Professional Scrum approach, now there is a clear connection of these commitments to the artifacts. They increase transparency, and the focussed delivery of Value. Each of the commitments now clearly support and sustain an artifact.

With the 2020 update to the Scrum Guide, three commitments were added to the artifacts. The idea of a commitment is to provide additional quality to the artifact to improve transparency. In the case of Product Backlog, the commitment is to the Product Goal. 

This blog post talks about the addition of Commitments to each Artifact in the updated Scrum Guide.