Commonly confused
Backlog vs Roadmap
A backlog is the ordered list of work that hasn't started yet — the near-term 'what's next.' A roadmap is the higher-level plan of direction and outcomes over time — the 'where we're going and roughly when.' The roadmap sets priorities; the backlog sequences the specific work that delivers them.
Backlog vs Roadmap, in short
- A backlog is the ordered list of work that hasn't started yet — the near-term 'what's next.' A roadmap is the higher-level plan of direction and outcomes over time — the 'where we're going and roughly when.' The roadmap sets priorities; the backlog sequences the specific work that delivers them.
- When to use backlog: Use the backlog to decide and order the next concrete units of work a team will pull.
- When to use roadmap: Use the roadmap to communicate direction, themes, and rough timing to stakeholders.
| Aspect | Backlog | Roadmap |
|---|---|---|
| Definition | 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. | A 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. |
| When to use it | Use the backlog to decide and order the next concrete units of work a team will pull. | Use the roadmap to communicate direction, themes, and rough timing to stakeholders. |
| Full definition | Backlog | Roadmap |