In Scrum, there is an artifact that consists of a prioritized list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver to achieve a specific outcome, such as the creation of a new product or modifications to an existing product. The name of this artifact is the Product Backlog, and it is the single authoritative source for things that a team works on. Inclusion of a Product Backlog Item (PBI) in a Product Backlog means that it is an option the team has for delivering a specific outcome; at any point a PBI could be removed from a Product Backlog or de-prioritized. The PBIs in a Product Backlog can vary considerably in size and also how well-articulated they are. Teams spend more time preparing the highest-priority work items, which are likely to be worked on sooner, while they spend little time preparing items that are lower in priority.
Product Backlog Video
Product Backlog Podcasts
Product Backlog Example
Authored by Philip Rogers
Photo by Jakob Owens on Unsplash
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Publishing as the source, who the author is, and the photo creator (if used).