It is sometimes referred to as a to-do list,[1] and is considered an 'artifact' (a form of documentation) within the scrum software development framework.
In scrum, coherence is defined as a measure of the relationships between backlog items which make them worthy of consideration as a whole.
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] 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.
A typical scrum backlog comprises the following different types of items:[clarification needed]