The process of defining a roadmap is arguably one of the most difficult but important things a product manager has to do. Far too often roadmaps are built without the complete picture in mind, without the right timing, in silos, or are misdirected. How then can we ensure we’re doing it right? Is there really such a thing as an agile roadmap?
This talk will draw from lessons learnt building product to provide practical tips and techniques enabling you to understand roadmap inputs, plan with different perspectives in mind, optimise for learning, communicate and set roadmap goals as well as find agility when the landscape around you changes.
Products covered:
Confluence
13. FEEDBACK
CHANNELS
BUSINESS
MODEL
Building on the Shoulders of Giants:
the Story of Bitbucket Pipelines
James Bryant (Now!, Check it out on YouTube)
Company
goals
Product
vision
Lightning talk: Tips for painting a
vision
Sherif Mansour (1:50pm, tomorrow)
25. Be data informed, not data
driven…
Good product design comes
from striking the right balance
between data, empathy and
intuition.
“
Alastair Simpson, Atlassian
bit.ly/data-informed
28. Teams that fall in love with a
problem have more successful
outcomes than teams that fall in
love with particular solutions.
“ …knowing that a problem is worth
solving continues to be motivating
even when a team doesn’t come
across the right solution…
Julie Zhuo, Facebook
bit.ly/buildingproduct
63. The art of building a roadmap
INPUTS
ROADMAPPING
Your roadmap is a set of decisions
Goals, vision, business model and feedback channels
Goal driven (solutions, metrics, problems)
Persona driven (by persona, by role, personify features)
Vision driven (lay tent pegs, paint visions and boxes)
Thanks!
@sherifmansour