A product backlog is an agile artifact that represents the work that will go into building a product. It can contain enhancement requests, features, maintenance work, learning needs, and bug fixes. Product backlogs are prioritized by the product owner in Scrum projects.
I have experience working with backlogs with various levels of detail. We often track work item metadata, such as the requester, owner, request date, high-level details, priority notes, size estimate, and scope notes or assumptions. Most of these data points are not officially required by the Scrum process, but many teams find this information helpful when managing large backlogs or backlogs that serve multiple stakeholders.
