The Product Roadmap


Stakeholder Engagement
The Product Vision

The course is part of this learning path

Start course

This module outlines some of the key areas that stakeholders are involved in during the Scrum process. It starts by defining what a Product Vision is before giving you guidance on how it can be effectively communicated to stakeholders. Then it describes the role of the stakeholder in the Product Roadmap and Sprint Goal.

Learning Objectives 

The objectives of this course are to provide you with and understanding of: 

  • The product vision and why it is required. 
  • The key components of a product vision including setting SMART goals. 
  • Methods to communicate the vision to your stakeholders.
  • The key features of a Product Roadmap and how it is created.
  • The Sprint Goal and its related outputs.
  • The importance of the Product Vision, Product Roadmap and Sprint Goal in supporting effective stakeholder management.

Intended Audience 

This course is aimed at Scrum Masters who want to improve their individual knowledge of stakeholder engagement practices in service to their Scrum team and their wider organization 


There are no specific prerequisites to study this course.


We welcome all feedback and suggestions - please contact us at to let us know what you think. 


A product roadmap is a powerful tool to support stakeholder engagement and works alongside the Product Vision. 


It’s a high-level visual summary that maps out the vision and direction of the product offering over time. It’s a projection that helps to communicate the why and what behind the product being developed and helps secure budget for it.  

A Product Roadmap is designed to: 

  • Describe the vision and strategy; 

  • Achieve internal stakeholder alignment; 

  • Facilitate discussions of options and scenario planning; and 

  • Help communication with external stakeholders. 


Types of Product Roadmap 

Product Roadmaps come in different formats: 


This is a ‘goal orientated roadmap’ which focuses on goals, objectives, and outcomes; like acquiring customers or increasing engagement. Product features are derived from the goals and there should generally be no more than 3-5 features per goal. 


This type of roadmap is more of a map. It lays the key processes, milestones and stages on a broad timeline with accompanying descriptors for each element. 


Remember, the roadmap is to help communication within the project team and with other internal stakeholders. It doesn’t matter what type you use as long as it does the job you need it to.  


There’s more information about creating a Roadmap in the ’10 tips for Creating an Agile Product Roadmap’ guide. You’ll find the link in the Stakeholder Engagement Resources. 

About the Author
Learning Paths

Tony has over 20 years’ experience in Business Development, Business Change, Consulting, and Project/Program Management working with public, private, and third sector organizations.

He has helped organizations to design and create processes and procedures to align ways of working with corporate strategy. A highly motivated and detailed solution provider, utilizing a wide range of methods and frameworks to provide structure whilst promoting creativity and innovation.

As a confident and self-motivated professional with excellent communication skills, Tony is able to bring people together and get them working as a team quickly.

Tony is an Agile and Scrum trainer with a vast knowledge spanning IT Systems, Business Change, Program and Project Management. With excellent presentation skills and a solid background, he ensures that all clients gain maximum benefit from his training. He has successfully guided those new to the industry through their initial training, helped experienced staff as they progress in their careers, and worked at the director level advising on best use and practice, as well as tailoring courses to fulfil the exact needs of clients.