backlog

/ˈbæk.lɒɡ/noun

A backlog is an ordered, evolving list of work for a product or project. Its order helps a team decide what to investigate or implement first.

After the customer research, the team moved a new reporting feature near the top of the backlog.

A backlog is a collection of work waiting to be considered or carried out. In software development, it might include new features, bugs, technical improvements and research questions. It is not a fixed schedule: adding an item to the backlog is not a promise that the team will implement it.

How does a team keep the backlog useful?

The team orders items by factors such as user value, urgency, risk and dependencies. Work likely to be tackled soon is described in more detail, including its purpose, intended outcome and Glossary · In briefacceptance criteriaAcceptance criteria are agreed, testable conditions that a product, feature or change must meet to be accepted.Read more. A rough estimate can help the team make decisions.

During Glossary · In briefrefinementRefinement is the ongoing clarification, breakdown and estimation of backlog work so the team understands what each item involves.Read more, the team discusses the most important items and breaks larger topics into smaller pieces when necessary. New insights may cause items to move, change or disappear altogether. This keeps the backlog aligned with the product's current needs.

Product backlog and sprint backlog

In Scrum, the product backlog contains work that may be needed to improve the product. The Glossary · In briefproduct ownerIn Scrum, the product owner is accountable for maximizing product value and managing the product backlog. They order the work and communicate the product goal.Read more is responsible for a clear ordering and makes sure the list is visible and understandable.

During sprint planning, the Scrum team selects items from the product backlog for the next Glossary · In briefsprintA sprint is a short, fixed period in which a team develops an agreed part of the software. Afterwards, you review the result and decide on the next priorities.Read more. Together with the sprint goal and the delivery plan, this selection forms the sprint backlog. The product backlog can change continuously; the sprint backlog describes the goal and work of the current sprint.