The Product Road Map is a plan that communicates how a product is likely to evolve over a period of time driven by the goals of the product.

1. THE PRODUCT ROAD
MAP
James Barnes
Product Owner | Agile Coach | Project Manager
www.jbagility.com

2. What is a Product Road Map?
■ A plan that communicates how a product is likely to evolve over a period of time driven by the goals
of the product.
■ Communicates major releases or versions of a given product.

3. Why is a Product Road Map a UsefulTool?
■ Provides continuous purpose.
■ Encourages collaboration.
■ Makes priorities visible and negotiable.
■ Gives clarity to the product backlog.
■ Helps derive a budget.
■ Manages dependencies between related products (when applicable).

4. Where doWe Start?
■ Decide if its an Internal or External roadmap makes the most sense for the product. (The less that’s
known about the product you are building, the more external exposure helps clarify what is
providing value.)
■ Prioritize product goals and benefits (the product reduces cost, generates revenue) - decide if goals
or dates or more important and focus the road map on that priority.
■ Decide on desired release dates and time frames.
■ Decide on metrics to determine if the goal has been met (Make goals SMART – Specific,
Measureable, Attainable, Realistic andTimely)
■ Focus attention to goals over features and capabilities needed to - focus on goals first!
■ Name the road map 

5. The Roadmap and the backlog
■ The product roadmap is broken down to create the product back log.
■ The Difference:
– The road map is strategic in that it describes how the product will evolve.
– The backlog is tactical and consists of the pieces (epics, user stories, etc.) needed to build the
product increments that satisfy the goals on the product roadmap.
■ KEEP IN MIND:The product road map and the backlog should stay in sync as a product adapts to
needed changes.

6. Product Strategy and the Road Map
■ The product strategy should drive the product road map.Validating a product strategy allows the
road map to be realistic, reliable and adjustable.
■ Ensure product strategy is validated and visible:
– Know the value the product creates for users and customers.
– Know the main problem the product solves.
– Know the main benefit the product provides.
– Evaluate who the users and customers are and are not.
– Know the business goals that influenced the strategy- Revenue generation? Reduce cost and
increase productivity?

7. Who Owns the Road Map?
■ Primary Owner: Product Owner
■ Secondary Owners: are driven by the product itself
■ COLLABORATION is key!
– Determine the key players of the product.
– Who has the highest influence and interest in the product?
– Who will we regularly involve in activities such as creation and adjustment of the road map?
■ Examples:The customers and end users, the development team, business stakeholders,
marketing and sales teams.

8. Use the Road Map to Estimate Costs
■ Using the roadmap as a guide, evaluate the people, skillsets, and tools you have or will need to
develop a rough estimate of cost.
■ Analyze Cost vs. Benefits
■ If the cost is too high or the resources aren't available, adjust the roadmap or pivot (adjust
strategy).
■ Use a release burn down to determine if the time line/cost is realistic.
■ Be roughly right vs. precisely wrong!

9. Reviewing and Adjusting the Road Map
■ How often the roadmap is reviewed and adjusted depends largely on the type and age of the
product and the type of market the product exists in.
– As a general guide:
■ Young product /dynamic market – Review Monthly
■ Mature Product / dynamic market - Review Quarterly
■ Young Product / stable market - Review Quarterly
■ Mature Product / Stable market – Review 3- 6 month