How to Define a Product Summary

A question that frequently comes up in my Scrum Training courses is how to define a product.
Scrum was created to help small teams solve complex problems and deliver products of the highest possible value. Scrum is used well beyond software because many teams and organizations recognize their work is complex, and they need to be nimble, creative, and value-focused. Yet defining your product can be challenging in both a software and non-software context.
How to Define a Product
What if you have a large complex system with multiple pieces that work together to deliver value to customers? What if your team provides processes or services such as marketing, sales, or innovation research? And what if those services you provide are a wide variety of work types that are not “integrated” in the same way software is?
Like most things in the complex world, there isn’t one right answer, and you may need to explore and adapt. In this blog post, I share how I coach people to think through defining their product. There are two essential things that help you define your product: “Done” and value.
Define a Product – “Done”
The Scrum Guide talks about a “Done” Increment being useable and potentially releasable. The concept of releasable sometimes causes confusion when the product is a service or perhaps R