What is a backlog?

Backlog, explained#

Every team has more ideas than time. The backlog is where those ideas go so they are not lost and not mistaken for commitments. Separating "we might do this" from "we are doing this" is the whole point: the active plan stays focused, and the backlog stays honest about what is waiting.

In Scrum, the product backlog is formally the ordered list of everything needed to improve the product, owned by the product owner, and the sprint backlog is the subset chosen for one sprint. Outside Scrum, most tools simply give work a backlog status before it is planned. Either way the activities are the same: add items as they come up, refine the promising ones with enough detail to estimate, order them by value and urgency, and pull from the top when capacity frees up.

Backlogs rot when nothing ever leaves them. Hundreds of old items make the list unreadable, so the useful ones get lost. Regular pruning helps: close what no longer matters, merge duplicates, and accept that an idea not touched in six months is probably not going to be.

Backlogs are also a good landing place for machine-generated work. When an AI agent or an automation proposes tasks, putting them in the backlog keeps a person in charge of what actually starts.

For example, after customer interviews, a product lead adds twelve items to the backlog. In the weekly planning meeting the team refines the top four, moves two into this week's plan with owners and dates, leaves two for later, and closes three that duplicated existing work.