Let’s briefly review the popular roadmaps types:
A timeline-based roadmap answers the question, ‘How long are you going to focus on a specific task—and when you plan to complete it?’
The basic reason to add timelines is to give your stakeholders a high-picture view of when and in what order you'll be making progress. Sometimes, companies don't set the exact dates as they don’t want to tie up to specific deadlines. They keep the time-frames high-level—a few months, a quarter, a year.
2. Roadmaps With No Dates
When you're writing a product roadmap for customers or your sales & marketing teams, often the best decision is to focus on themes and strategies, not dates or deadlines.
That's how you earn people’s interest in the forthcoming product while not setting expectations about the day when it comes out.
Same for the marketing & sales teams: you probably don't want to risk reputation telling customers the release date. Or it may lead to the same risk of disappointment in case of a delay.
3. Kanban Roadmaps
Timeline-based and no-dates roadmaps usually present the plan for a great deal of time, like months or even years. On the contrary, a Kanban roadmap focuses on what needs to be done right now.
Kanban is more of a high-level project management view, mostly for internal audiences—developers, product teams, and others responsible for building your product.
You can use statuses for a Kanban roadmap:
- Ready for estimation
- In progress
That’ll inform your stakeholders of the status and priorities of each development stage.