The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists.
The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate, and value. Product Backlog items often include test descriptions that will prove its completeness when “Done”.
As a product is used and gains value, and the marketplace provides feedback, the Product Backlog becomes a larger and more exhaustive list. Requirements never stop changing, so a Product Backlog is a living artifact. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.
Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product. A Product Backlog attribute that groups items may then be employed.
The What is Scrum Blog Series are excerpts from the Scrum Guide by Ken Schwaber and Jeff Sutherland. Offered for license under the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/.
- Scrum Foundations Course Video Series
- An Introduction to Scrum
- What Are the 3 Pillars of Scrum?
- What are the 5 Scrum Values?
- What is a Scrum Team?
- What is a Scrum Product Owner?
- What is a Scrum Development Team?
- What is the Ideal Size of a Scrum Development Team?
- What is a Scrum Master?
- What are the Scrum Events?
- What is a Sprint?
- Who can cancel a Sprint?
- What is Sprint Planning?
- What is a Sprint Goal?
- What is a Daily Scrum?
- What is a Sprint Review?
- What is a Sprint Retrospective?
- What are the Scrum Artifacts?
- What is a Product Backlog?
- What is Product Backlog Refinement or Grooming?
- What is a Sprint Backlog?
- What is a Product Increment?
- What is a Definition of “Done”?
- Who is Monitoring Progress?
- The Importance of Artifact Transparency
- Scrum in an Nutshell