Product Vision, Strategy & Roadmap
Mar 21 st , 2020
Sharad Agrawal
Introduction
Working as Sr Principal Product Manager in Oracle
Based out of NCR (Noida)
B.Tech + MBA
8+ Years in Product Management (Overall 20 years)
Previously worked in Deloitte, Cisco, Dell & Ford
Have more than 14+ years of US experience
Focus on SaaS Applications (CRM, ERP etc.)
LinkedIn: https://www.linkedin.com/in/sharad22
Agenda
Agile Product Plan
Key Factors
How to Build Product Strategy
How to Build Product Roadmap
Epic/Story
Tools Used
Q &A
Agile Product Plan
Vision
Strategy
Roadmap
Key Factors Vision
• Its about the future and hopefully Better Word
• Should be revised atleast once a year
• Should be easy to understand and everyone in company
Strategy should know about it
Strategy
• Defines the direction that will take it your vision
• Serve as a guide, how to turn vision into a reality
• Its not the tactical work, but lays out the goals and key
Vision Roadmap initiatives to be successful
Roadmap
• Visualization of the strategy
• Captures the activities need to be done within a given
time frame
• Helps in prioritization, resource allocation & tracking
dependency
• Its not static and should be updated as needed
Vision, strategy, and roadmaps build upon one another — All three are
needed to create winning plans and goal realization.
Product Strategy
Customer Interview
• Should address the needs of your customers above all else
• Ask for question to understand the need and look for pattern what they
say
• Always refer back to what customer
Futuristic Cross Functional Collaboration
Cross Functional • Strategy does not exist in isolation
Collaboration
• Needs discussion with marketing, sales, support, and engineering to
understand their goals
• By hearing different perspectives, a common ground can be found that is
Clarity of Thoughts aligned with the organization goal
Interview
Customer
Futuristic
• Should not ignore the long term perspective
• Strategy needs to serve the customers now as well as in the future
Steps to Clarity of Thoughts
Define • Define clear assumptions and layout the customer benefits
Product • Acknowledge any potential disadvantage and constraints
Strategy • Be respectful and listen to others perspective but don’t afraid to keep
your points
Product Roadmap
External roadmap for Customers & Partners:
• Should focus on the product’s benefits
• Don’t include the release or launch dates in external-facing roadmaps
Internal roadmap for Sales Team:
• Should focus on customer benefits
• Group similar features so that sales reps can discuss with prospects
• Avoid committing internal target date to sales rep
Internal roadmap for Engineers:
• Granular in scope and shorter in duration than executive-facing roadmap
• Have details - Epics, Story, Release, Sprint etc.
• Should focus on Milestones & dependency etc.
Internal roadmap for executives:
• Focus on driving growth, new market penetration, customer satisfaction etc
• Helps to Get Buy-in from executives
M (Must Have) – Non Negotiable
S (Should Have) – Important Initiative
MoSCoW Co (Could Have) – Nice to Have
Prioritization W (Will not Have) – Not a priority for this Release
Epic/Story
Initiative
Epic Epic Epic
Story Story Story
Story Story
Story
Tools Used
Confluence (Wiki) Page
Jira
Microsoft Office
Questions & Answers