The Product Backlog is an emergent, ordered list ๐ of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
Product Backlog items that can be "Done" โ by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. Product Backlog refinement is the act of breaking ๐จ down and further defining Product Backlog items into smaller more precise items ๐. This is an ongoing activity to add โ details, such as a description, order, and size. Attributes often vary with the domain of work.
The Developers๐ฉ๐ป๐จ๐ป who will be doing the work are responsible for the sizing ๐๏ธ. The Product Owner๐ฉ๐ผ may influence the Developers by helping them understand ๐ง and select trade-offs ๐ค.
Commitment: Product Goal
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 โญ๏ธ.