The Product Backlog

1. The single source of requirements for the product.
2. Prioritized list of requirements arranged as value-creating user stories ordered by business value.
3. The user-stories nearer the top are clear and detailed than those below.
4. User-stories taken into sprint backlog are fine-grained enough to be done in a Sprint.
5. User-stories at the bottom are usually vague in scope. They are called Epics (fairly vague ideas) or Themes (extremely vague ideas).
6. This document exists and evolves all through the product’s lifetime.
7. Editable by anyone but owned and prioritized by Product Owner.

"The product backlog 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."

At its core, the product backlog is an ordered list of items that is managed by a person with the ability to understand the business’ needs.

The product backlog is used to:

capture requests for modifying a product.  This can include add new features, replacing old features, removing features and fixing issues; and ensure the delivery team is given work which maximizes the business benefit to the owner of the product

Artifacts in the Scrum Framework

List of Artifacts in the Scrum  Framework

1. The Product Backlog
2. The Sprint Backlog
3. The Increment

Product Backlog :

The product backlog is a prioritized features list, containing short descriptions of all functionality desired in the product. When using Scrum, it is not necessary to start a project with a lengthy, upfront effort to document all requirements. Typically, a Scrum team and its product owner begin by writing down everything they can think of easily. This agile backlog is almost always more than enough for a first sprint. The Scrum product backlog is then allowed to grow and change as more is learned about the product and its customers.

Sprint Backlog :

The Sprint Backlog consists of the necessary tasks to realize the final accepted a version of the Selected Product Backlog. The team uses it to synchronize its activities. The tasks turn the Selected Product Backlog into working product functionality.

Increment:

Increment = [all backlog items done in this sprint ] + [increments done in all previous sprints]

An increment must always be in “done” and usable condition.