The Scrum Guide got an update last November and one of the concepts introduced was the Product Goal. The Scrum Guide says:

“The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.

"A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users, or customers. A product could be a service, a physical product, or something more abstract.

"The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.”

For some, myself included, taking that basic definition, extending it, and creating clarity on how the Product Goal fits in with other ways we talk about the Product Backlog has been challenging. So, I reached out for some help...

In this episode of The Reluctant Agilist, I'm joined by Ryan Ripley. Ryan is the co-author of "Fixing Your Scrum", the co-host of the Agile for Humans podcast and he's also a Professional Scrum Trainer. During the conversation, Ryan and I dig into what exactly the Prout Goal is, how teams can use it to deliver value and how it fits in with some of the other aspects of the Product Backlog.

If you'd like to check out the podcast Ryan and I recorded on his book Fixing Your Scrum you can find it here: https://bit.ly/3vIWNJq

Links from the Podcast:
Agile for Humans Podcast https://ryanripley.com/agile-for-humans/
Fixing Your Scrum https://amzn.to/2PdBz5i
Web: https://ryanripley.com/
Email: ryan@agileforhumans.com
Twitter: https://twitter.com/ryanripley