Product backlog#Coherence
{{Short description|List in product management}}
Within agile project management, product backlog refers to a prioritized list of functionality which a product should contain. It is sometimes referred to as a to-do list,{{Cite web|last=Atlassian|title=The product backlog: your ultimate to-do list|url=https://www.atlassian.com/agile/scrum/backlogs|access-date=2021-12-19|website=Atlassian|language=en}} and is considered an 'artifact' (a form of documentation) within the scrum software development framework.{{Cite web|title=What is a Product Backlog?|url=https://www.scrum.org/resources/what-is-a-product-backlog|access-date=2021-12-19|website=Scrum.org|language=en}} The product backlog is referred to with different names in different project management frameworks, such as product backlog in scrum,{{Cite web|title=What is a Product Backlog?|url=https://www.scrum.org/resources/what-is-a-product-backlog|access-date=2021-12-19|website=Scrum.org|language=en}}{{Cite web|title=Agile Core Practice: Prioritized Requirements|url=http://agilemodeling.com/essays/prioritizedRequirements.htm|access-date=2021-12-19|website=agilemodeling.com}} work item list in disciplined agile,{{Cite web|title=Agile Core Practice: Prioritized Requirements|url=http://agilemodeling.com/essays/prioritizedRequirements.htm|access-date=2021-12-19|website=agilemodeling.com}}{{Cite web|title=Artifact: Work Items List|url=https://www.utm.mx/~caff/doc/OpenUPWeb/openup/workproducts/work_items_list_39D03CC8.html|access-date=2021-12-19|website=www.utm.mx}} and option pool in lean.{{Cite web|title=Agile Core Practice: Prioritized Requirements|url=http://agilemodeling.com/essays/prioritizedRequirements.htm|access-date=2021-12-19|website=agilemodeling.com}} In the scrum framework, creation and continuous maintenance of the product backlog is part of the responsibility of the product owner.{{Cite web|title=Produkteier {{!}} Digitaliseringsdirektoratet|url=https://www.prosjektveiviseren.no/roller/produkteier|archive-url=https://web.archive.org/web/20200810211854/https://www.prosjektveiviseren.no/roller/produkteier|url-status=usurped|archive-date=August 10, 2020|access-date=2021-11-15}}
A sprint backlog{{Cite web|title=Sprintkø {{!}} Digitaliseringsdirektoratet|url=https://www.prosjektveiviseren.no/begreper/sprintko|archive-url=https://web.archive.org/web/20200812212100/https://www.prosjektveiviseren.no/begreper/sprintko|url-status=usurped|archive-date=August 12, 2020|access-date=2021-11-15}} consists of selected elements from the product backlog which are planned to be developed within that particular sprint.
In scrum, coherence is defined as a measure of the relationships between backlog items which make them worthy of consideration as a whole.[https://www.scrum.org/resources/scrum-glossary Scrum Glossary | Scrum.org]
Outline
The agile product backlog in scrum is a prioritized features list, containing short descriptions of all functionality desired in the product. When applying the scrum or other agile development methodology, it is not necessary to start a project with a lengthy, upfront effort to document all requirements as is more common with traditional project management methods following the waterfall model.{{citation needed|date=December 2021}} Instead, a scrum team and its product owner will typically begin by writing down every relevant feature they can think of for the project's agile backlog prioritization, and the initial agile product backlog is almost always more than enough for a first sprint. The scrum product backlog is then allowed to grow further throughout the project life cycle and change as more is learned about the product and its customers.
A typical scrum backlog comprises features, bugs, technical work and knowledge acquisition.{{clarify|date=December 2021}}