According to the Scrum Guide, 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.”
Each entry in the list is called a Product Backlog Item (“PBI”). Since User Stories are such a common practice, Backlog Items are often just called “Stories” even though User Stories are not part of Scrum and backlog items are not necessarily in User Story format. (I use story and backlog item interchangeably).
A list is just a list, so there is nothing binding about the Product Backlog. It is a list of ideas – things that you think belong in the product, but this list is subject to change at any time.
Each backlog item has the following attributes:
Description – a statement of the goal or purpose of the story.Sequence number – its place in the queue – determined by the Product OwnerValue - a statement of the business value of the story – determined by the Product OwnerEstimate – th…
Each entry in the list is called a Product Backlog Item (“PBI”). Since User Stories are such a common practice, Backlog Items are often just called “Stories” even though User Stories are not part of Scrum and backlog items are not necessarily in User Story format. (I use story and backlog item interchangeably).
A list is just a list, so there is nothing binding about the Product Backlog. It is a list of ideas – things that you think belong in the product, but this list is subject to change at any time.
Each backlog item has the following attributes:
Description – a statement of the goal or purpose of the story.Sequence number – its place in the queue – determined by the Product OwnerValue - a statement of the business value of the story – determined by the Product OwnerEstimate – th…