Time needed: 1 hour.
This process walks you through the steps to create your own roadmap slide for a presentation or to share.
- Choose your “Workstreams” (or “swim lanes”)
“Workstreams” are the ongoing, most important delivery areas of your Product / Project.
You will arrange key activities within these areas.
There may be just one, and there may be many.
Our advice is to choose 3-5 workstreams.
These are also known as “Project Swim Lanes”.
- Set the Timeframe
Think: “What timeframe do you need to cover?”
Be careful – the further in the future you go, the more uncertain. Read up on “the cone of uncertainty”
- Establish the important activities in each stream
Within each Workstream, what are the key areas of activity?
The could be “Projects” or “Tasks” etc, depending on your kind of product / programme / project.
Bear in mind that you want the whole roadmap readable within 5 mins, so you do not want lots & lots.
- Communicate risk levels
Use colour coding of the activity boxes in each work stream to indicate levels of risk or certainty.
Explain your colour coding in a “Legend” at the top.
You can use “Red Amber Green” or just highlight the Medium and High risks with amber and red.
- Set some Milestones
You should include a few key dates on the timeline.
These can be represented as “Milestones”.
e.g. Launches, handovers, closures, migrations, etc.
- Add any other important points
Bear in mind: your Roadmap tells your story.
It needs to do that within 5 mins.
Still,.. are there any other important points you need to highlight?
If so, then put them in as call-out “comments”!
Some more help for Creating Your Roadmap
Communicating your project plans and strategy in one document is not a simple process.
Project, programme and portfolio managers are increasingly using Roadmap Template formats to establish a clear, shared understanding of project plans, especially at the board and executive level.
Example Project Roadmap Layout
This is our popular Visio Roadmap Template from 2005.
Characteristics of a Project Roadmap
- Communicates project plans at a glance
- Highlights important milestones
- Tells your stakeholders what to expect, and when
- Demonstrates the use of the capacity you have available
- Demonstrates where your resources and budget are being allocated
- Gives a sense of proportional allocation
- Draws attention to important issues
- Keeps them few
- Makes them clear
- Gives you a tool to “manage upwards”
- Highlights what you need from stakeholders
- Manages expectations
Create your Roadmap
Before committing this to an electronic format, sketch it out on a large piece of paper, using pencil and eraser
- If you want to save time – you can see some Powerpoint Roadmap examples here.
- Set out your timeline
- How far do you want to show?
- Make sure this is going to be a relevant period of time – i.e. don’t go too far into the future
- Establish your workstreams
- Where are the areas of resource or budget focus?
- Work these into discrete “workstreams” of activity
- This helps you communicate to your stakeholders and their colleagues where the business is focussing
- Work out the high-level activities within each workstream
- Keep the level of detail down
- e.g. if your entire timeline is 12 months long, don’t include any activities below 1 month long
- Keep this realistic – i.e. don’t overload any of the workstreams
- If there are areas of high risk – add labels
- Resource issues/constraint/risks
- Financial issues/constraint/risks
- External issues/constraint/risks
- Put in your key milestones
- In a timeline along the top of your Roadmap, add markers for important dates
- Keep these dates realistic
- leave plenty of contingency
- If a date/milestone is tentative – clearly mark it so
- Clearly demark the status of your document
- If it is “draft”, clearly label it with “DRAFT” at the top of the document
- Give it a version number
- If it has been signed off by a key stakeholder, mark this prominently
With all parts of this Roadmap process, try and keep your roadmap document uncluttered.
Then create your electronic version – see the list of templates below if you need a good starting point.
Testing your Roadmap
- Use a friend or colleage as a guinea pig to test your Roadmap.
- They should be able to understand your roadmap and your project timelines within 1 minute of looking at it.
- This is what separates it from a standard “Project Plan”.
Keep your Roadmap up to date
Once created, you must be sure to keep your roadmap up to date.
If you are running an agile process (i.e. regular iterations and regular product releases), keep your Roadmap updated at regular intervals in time with your iterations.
Short on time?
Use these templates to help with business best practice:
Related Business Best Practices
Here’s a step by step guide to create one quickly – 5 minutes for a 1 side Roadmap.
A Project Roadmap is the best format to communicate project plans to executive boards and stakeholders. Here’s how to create one.
I have a presentation to do, which requires a Roadmap Slide – how do I do it in Powerpoint?
If you have a presentation to do, and are using Keynote on a Mac, here’s the process to help you.
Notes, templates, tips and tricks for how to create an agile project release plan.
If you need to show KPIs on your Product Roadmap, have a look at these approaches and examples.
All Business Best Practice
See all Business Best Practice here.