What is a Backlog?

A backlog is the ordered list of everything the team might build next.

How does a backlog work?

The product owner keeps it ordered, so the top is always the most valuable next thing. Refinement breaks big items into smaller, clearer ones and adds enough detail to estimate. The team pulls from the top into a sprint. Anything below the fold stays deliberately rough.

Why does a backlog matter?

It is the single place where competing requests get compared. Without one, priority is decided by whoever asked most recently or most loudly. It also makes tradeoffs visible: saying yes to a new item means something else moves down, in public.

Where did the backlog come from?

The term is central to Scrum. The Scrum Guide, written by Ken Schwaber and Jeff Sutherland, defines the Product Backlog as the single source of work for the team and makes the Product Owner accountable for its order.

How do you keep a backlog well?

Order it, do not just group it, because a list without a top is not a decision. Refine only the next couple of sprints, since detail on distant items decays. Delete aggressively, because a backlog nobody reads is a graveyard with a project manager. Keep the Sprint Backlog separate, since that one is a commitment. And remember the ordering argument is the real work, which is why agile teams spend so much time on it.

Bottom line: A backlog is only useful if it is ordered, because an unordered list just moves the argument to standup.

For more startup terminology, visit startupdefinitions.com.