Agile roadmap: the plan that sits above your backlog and sprints
Teams that work in sprints sometimes decide they don't need a roadmap. The sprint board says what's happening for the next two weeks, the backlog holds everything else, and anything longer feels like the kind of up-front plan agile was meant to replace. Then a customer asks "are you ever going to fix exports?" and nobody has an answer they can share.
An agile roadmap fills that gap. It says where the product is heading without fixing the route. This page covers how it fits with the backlog and sprints, how to keep it current, and how customer requests feed it. It's about one product team's roadmap, not organization-wide agile transformation programs.
Three layers, three questions
Agile development roadmap planning goes wrong when the three layers blur together. Each answers its own question for its own readers.
| Layer | Question it answers | Horizon | Who changes it | When it changes |
|---|---|---|---|---|
| Roadmap | Which customer problems are we taking on, in what order? | Months | The product owner, with the team | At sprint reviews, when priorities shift |
| Backlog | What could we build, broken into pieces? | Open-ended | The product owner | Continuously |
| Sprint | What are we finishing in these two weeks? | One sprint | The team | At sprint planning |
Information flows down. A roadmap card such as "Faster checkout for returning buyers" becomes several backlog items, and a few of those land in the next sprint. Progress flows back up: when the sprint work that serves a card is under way, the card moves to Now.
Outcomes and themes instead of dates
In an agile team, scope and timing are expected to move as you learn. A roadmap full of dated features fights that. Two changes fix it.
Write cards as outcomes. "Buyers can resend their own tickets" leaves the team free to find the best way to do it. "Build a resend button on the order page" has already decided, before anyone has tried it.
Group cards under themes. A theme is a lasting goal, such as "fewer support emails" or "sell out faster". Themes change slowly, perhaps once or twice a year, while the cards under them change at every review. That gives readers something stable to hold on to while the detail moves.
Broad time buckets, not sprint numbers
Resist putting sprint numbers or exact weeks on the roadmap. Use buckets that say how sure you are:
- Now: work under way in this sprint or the next.
- Next: decided, and likely to start within the next few sprints.
- Later: being weighed. It may change shape or disappear.
If leadership or larger customers need calendar language, quarters are the next step up. Keep the current quarter specific and the later ones broad, so a card's position still reads as intent rather than a delivery date.
Updating it at each sprint review
The sprint review is the natural moment to touch the roadmap, because the team has just seen what got done. Five questions, five minutes:
- Did any Now card finish? If so, announce it in the changelog and take it off the roadmap.
- Has work started on a Next card? Move it to Now.
- Did we learn something that changes a Later card's shape? Rewrite it.
- Has a card sat in Next for several reviews without starting? Either commit to it or move it back to Later and say why.
- Do the themes still describe what we're trying to achieve?
If the answer to every question is "no change", that's fine. It means the roadmap is still true.
How customer requests feed it
Requests usually arrive as solutions: "add a resend button", "let me pick seats". Put them on a public feedback board where others can vote and comment, and merge duplicates so the votes add up. The product owner reads the board before each review and decides which requests point at a problem worth a roadmap card.
From there the statuses do the bookkeeping. In Votelantern, a request marked Under review appears under Later, Planned under Next and In progress under Now, and you can rename those columns. The backlog and sprint work stay wherever your team keeps them. When the change ships, publish a changelog entry linked to the request. That moves it to Shipped and emails the voters who asked for updates.
An agile roadmap example
Pebblerun is a fictional ticketing tool for small theaters. Its roadmap has two themes. Here is what changed at one sprint review.
| Card | Theme | Before the review | After the review | Why |
|---|---|---|---|---|
| Buyers can resend their own tickets | Fewer support emails | Now | Shipped, off the roadmap | Finished this sprint; changelog entry published |
| Clear refund rules on every event page | Fewer support emails | Next | Now | First backlog items pulled into the new sprint |
| Choose your seat on a seating plan | Sell out faster | Next | Next | Still decided; waiting for the refund work |
| Waitlist for sold-out shows | Sell out faster | Later | Next | Many voters on the board, and the team agreed a plan |
| Group bookings for schools | Sell out faster | Later | Later, reworded | Sprint demo showed it needs a separate checkout |
No card has a date, yet a reader can see what's happening, what's coming and what's still open. Notice the seating plan card staying put. A roadmap doesn't have to change at every review; it has to stay true.
Roadmap agile template
The theme layout fits this way of working: each theme is a row running across Now, Next and Later, and cards move between columns as request statuses change. A filled-in version for Crumbcount, a fictional bakery app, is shown on the product roadmap template page.
It opens in a free Votelantern account with example cards you replace with your own. If you'd rather start without themes, the plain Now, Next, Later layout is on the roadmap template page.
Votelantern's prices are still drafts. The Free plan is $0 for one public board with its roadmap, changelog and widget, one admin and a "Powered by Votelantern" badge. Team (price not set yet) gives you up to three admins and up to five boards. Business (price not set yet) adds private boards, if your roadmap is for staff only.
FAQ
Isn't a roadmap the opposite of agile? Only if it's a fixed plan with dates. A roadmap of outcomes in broad buckets, revised at every sprint review, is a way of sharing your current best guess. That's in the spirit of responding to change.
Should sprint goals appear on the roadmap? No. A sprint goal serves a roadmap card; it isn't one. If you show both, readers outside the team lose the bigger picture in the detail.
Who updates the roadmap in a scrum team? The product owner, usually during or just after the sprint review, with the team in the room. One person making the edits keeps the wording consistent.
What if a stakeholder insists on a date? Give a range at the quarter level, and say what would make it slip. Keep the date off the public roadmap.