Backlog

A backlog is a prioritized list of everything a team plans to deliver for a product or project: new features, bug fixes, technical improvements and research tasks. The concept comes from Agile methodologies and sits at the heart of Scrum, where the product backlog serves as the single source of work for the development team. Items near the top are well understood, estimated and ready to be picked up; entries further down stay deliberately rough until they become relevant.

How a backlog works

The product backlog is owned by the Product Owner, who orders items by business value, risk, dependencies and cost of delay. It is never finished — customer feedback, new ideas and technical debt keep flowing in, while stale entries get pruned. During recurring refinement sessions the team breaks large epics into smaller user stories, adds acceptance criteria and estimates effort, typically in story points. At the start of every sprint, the team pulls the top items it can realistically complete into the sprint backlog, which becomes the working plan for the next one to four weeks. A common quality benchmark is that the top of the list should be detailed and small, while the bottom may remain coarse-grained.

Practical applications

Most teams manage backlogs in tools such as Jira, Trello, Azure DevOps or GitHub Projects, which support labeling, filtering and progress reporting. The pattern is not limited to software development: operations and DevOps teams keep backlogs of infrastructure work — OS patching, backup automation, monitoring rollouts — and marketing teams use them for content pipelines. Good backlog hygiene matters more than tooling: review the list regularly, delete items that no longer earn their place, and resist the temptation to treat the backlog as a wish-list archive. A backlog that nobody trusts stops being a planning tool and becomes noise.