Product Backlog: definition and use

The Product Backlog is an artifact of Scrum in the form of a dynamic and incomplete list of items that reflect what is presently believed will be implemented for the product in order to realize the Product Goal (see chapter Commitment: Product Goal). This list is ordered, which means that at the top of the list are the items considered most important for the realization of the Product Goal and from it the next items are always selected and taken for implementation. The Product Goal is also part of the Product Backlog.

The Product Backlog is a living artifact and is thus constantly evolving. As the product is developed, released, and used, the more is known and understood about the emerging needs of its users and the product will thus evolve accordingly. The Product Backlog is then modified by adding, subtracting, reordering, and refining its items, which will have a granularity and level of detail based on how close they are to being implemented. In this way, the items at the top of the Product Backlog have a finer granularity, represent more detail, and can have a more accurate estimate of the effort required for their implementation. At the other end, the items at the bottom of the Product Backlog are coarser in granularity, represent less detail and have more general estimates.

The Product Backlog is the only source of work for the Developers, who likewise are the only ones to utilize their items in order to develop the product. No one can force them to work from another source.