← Glossary
Org & delivery

Backlog

Also known as: product backlog, task backlog

A backlog is a prioritised list of work still to be done, from which a team pulls the next most important items to deliver.

Key takeaways
  • A backlog is one prioritised, ordered queue of work still to be done.
  • The value is in the prioritisation, not the list; an unordered pile is a to-do list, not a backlog.
  • Kept well, it is the single place priorities live, so the loudest voice does not set the agenda.

A backlog turns a scattered pile of requests, ideas and tasks into one ordered queue, so the team always knows what matters most next. The discipline is in the prioritisation: a backlog that is just a growing list of everything anyone has ever asked for is a to-do list, not a plan.

Kept well, it is the single place priorities live, which is what stops the loudest voice, rather than the most important work, setting the agenda.

Commonly confused with

Roadmap

A roadmap is the higher-level plan of what is coming and roughly when. The backlog is the detailed, ordered list of the work itself.

Frequently asked

What is the difference between a backlog and a to-do list?
A to-do list is an unordered collection of tasks. A backlog is deliberately prioritised, so the team always pulls the next most important item rather than whatever is nearest the top.
Who owns the backlog?
Usually one person, a product owner, delivery lead, or fractional PM, owns prioritisation with input from the team. Single ownership is what keeps it coherent.
How often should a backlog be reviewed?
Regularly, often weekly, so it reflects current priorities. A backlog nobody grooms quickly becomes a graveyard of stale requests.
Related terms
Fractional PMCapacity PlanningDelivery Model

Something in your operations is costing you. Let's fix it.

A 30-minute call, no pitch. Tell me what's breaking and I'll tell you straight whether I can help.

Book a callcontact@dhruvit.me