The requirements backlog is a tool where customers can record and prioritize their business requirements for each iteration, and where the project teams can record the progress of their work during each iteration against these requirements.
The Product Backlog lists requirements. It is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. It contains broad descriptions of all required features, functions, enhancements, wish-list items, etc. The Product Backlog defines the “What” that will be built.
The Product Backlog items are initially established and calculated during Release Planning. Afterwards they are updated in Sprint Planning or Backlog Groomings. The top priority items are selected for development during Sprint Planning developed in the Sprint and reviewed in the Sprint Review.
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. These items are normally termed as User Stories. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
