The Product Backlog answers the question: “What capabilities are needs for financial success?”
Product Backlog a prioritized list of Stories that are waiting to be worked on. It is the requirements for a system, expressed as a prioritized list of Product Backlog Items. These included both functional and non-functional customer requirements, as well as technical team-generated requirements. While there are multiple inputs to the Product Backlog, it is the sole responsibility of the Product Owner to prioritize the Product Backlog. During a Sprint Planning meeting, Backlog Items are moved from the Product Backlog into a Sprint, based on the Product Owner's Priorities.
The Product Backlog is the set of all un-implemented Product Backlog Items (requirements, in the form of Stories and Defects that have not been assigned to the current Sprint. Unlike the Sprint Backlog, there is no requirement that all PBIs be assigned a rank.
A Product Backlog should only consist of the Product Backlog Items for the approximately next three Sprints.
The Product Backlog should fullfill the DEEP criteria.