Roadmaps

Introduction

Roadmaps are typically associated with Product Development and as such "Product Roadmaps" are the most common type of roadmap.  However, the concept can be applied to any area where strategic planning, agility and transparency are important.  VFS use Technology Roadmaps to help convey the key messages and to aid with the execution of a Technology Strategy.

Below, we refer to Product Roadmaps, but the points are relevant to any roadmap.

Where to start?

Creating and sharing product roadmaps can often feel daunting.  How can we possibly know what we need to do in 6 months time?  If we share this we will be held to it!  We shouldn’t be listing a set of features out, we need to research and test what the users need.  These are all normal questions and concerns, and normally arise when there isn’t a correct and common understanding of what Product Roadmaps are across the business.

What is a Roadmap?

They are NOT a Product Backlog.  They do NOT capture or convey what functionality will be developed and released until this functionality is known to be the preferred way of meeting our users needs and that it is likely to provide our business with the desired benefits (value / impact).

Roadmaps and Information Radiators

• Increase alignment with succinct visuals:

  • Why are these items on our roadmap? and Where is our destination?

  • Who will play an important role in helping us get to our destination?

  • How will these people need to behave to ensure we get there?

  • What ideas we currently have for nudging and influencing people to change their behaviours?

• Include Business Goals and Hypotheses that need testing

• Convey the need to support adaptability and agility

It is likely that a Roadmap will contain MVFs and MVPs, as well as MMFs and MMPs.

Minimum Viable Features and Products; Minimum Marketable Features and Products

Roadmaps and Forecasting Business Impact