Definition
Backlog
A backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.
Key takeaways
- A backlog is the ordered, prioritized queue of all identified-but-not-started work — features, bugs, improvements, and ideas.
- Its discipline is ordering: the top should always be what's most worth doing next, so pulling the next item needs no debate.
- Backlogs need active grooming (refinement) — clarifying, splitting, dropping stale items — or they decay into an indistinguishable graveyard.
- A well-kept backlog feeds both models: cycle teams draw from it at planning; Kanban teams pull from it continuously.
A backlog is less a to-do list than a prioritized queue of intent. Anything the team might do lives there until it is either started or explicitly dropped. The discipline is ordering: the top of the backlog should always represent what the team believes is most worth doing next, so that pulling the next item requires no debate.
Backlogs need active maintenance, often called grooming or refinement: clarifying vague items, splitting large ones, dropping stale ones, and re-ordering as priorities shift. A backlog left untended becomes a graveyard where good ideas and dead ones are indistinguishable, which is why many teams cap its size and archive aggressively.
A well-kept backlog feeds both planning models. For cycle-based teams it is the source you draw from at planning. For Kanban teams it is the leftmost column you pull from continuously.
Planoda keeps the backlog filterable and rankable with fractional ordering, so reprioritizing never renumbers the whole list and triage can route new issues into it instantly.
Related terms
- TriageTriage is the process of reviewing newly reported issues and deciding what happens to each — accept and prioritize, request more detail, route to a team, or close. Borrowed from emergency medicine, it keeps the incoming flow of bugs and requests from overwhelming a team by quickly sorting signal from noise at the front door.
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
- KanbanKanban is a visual workflow method that maps work onto a board of columns representing stages — typically backlog, in progress, and done. Cards move left to right as work advances. It emphasizes continuous flow, making bottlenecks visible, and limiting work in progress rather than committing to fixed time-boxes.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.