Slide d
eck
Roman Pichler’s
Agile Product
Roadmap Tutorial
About Roman
• Agile
product
management
and
Scrum
consultant,
trainer
and
author
with
over
10
years
experience
in
– Teaching
and
coaching
product
managers,
product
owners,
business
analysts,
and
project
managers
– Helping
companies
apply
agile
prac?ces
to
achieve
business
success
• Business
owner
and
product
manager
– I
walk
my
own
talk
One of my books!
© 2006-2014 Pichler Consulting Ltd 2
Introduction
What is a Product Roadmap?
• A
product
roadmap
is
a
high-‐level
plan
that
shows
how
a
product
is
likely
to
evolve.
• It
typically
covers
several
major
releases
or
product
versions.
© 2006-2014 Pichler Consulting Ltd 4
The Benefits of a Product Roadmap
Stakeholder
Continuity
alignment and Prioritisation
of purpose
collaboration
Helps with Umbrella for
portfolio the product
management backlog
© 2006-2014 Pichler Consulting Ltd 5
Common Roadmap Mistakes
• View
it
as
a
hard-‐and-‐fast
plan
or
a
commitment.
• Focus
too
much
on
features.
– Makes
it
hard
to
achieve
agreement
and
the
roadmap
more
vola?le.
• List
largely
unrelated
features
to
please
individuals.
• Create
a
roadmap
when
you
cannot
look
beyond
the
next
major
release.
© 2006-2014 Pichler Consulting Ltd 6
Agile Roadmap Challenges
• Crea?ng
a
realis?c
roadmap
when
markets
and
technologies
change
frequently
and
unexpectedly.
• Building
a
longer-‐term
plan
when
agile
teams
commit
to
no
more
than
four
weeks.
• Unclear
how
the
product
roadmap
and
the
product
relate.
– Do
they
compete
with
or
complement
each
other?
© 2006-2014 Pichler Consulting Ltd 7
Creating an
Agile Product Roadmap
Let’s Look at an Example
© 2006-2014 Pichler Consulting Ltd 9
How do We Get to the Roadmap?
Idea
?
?
Product Roadmap
© 2006-2014 Pichler Consulting Ltd 10
First Create and Validate a Product Strategy
Product Product
Strategy Roadmap
Idea
Validated! A plan with!
Value prop & ! goals, dates !
biz goals! and metrics!
© 2006-2014 Pichler Consulting Ltd 11
The GO Product Roadmap
When will !
Date
The launch date or timeframe
the release !
be available?!
Name What is!
The name of the new product
version or major release
it called?!
Goal Why should!
The reason for creating the
new version
it be developed?!
Features What are its!
The high-level features
necessary to meet the goal
key features?!
Metrics How do we
The metrics/KPIs to determine know the goal!
if the goal has been met has been met?!
© 2006-2014 Pichler Consulting Ltd 12
A Sample GO Roadmap
3rd quarter! 4th quarter! 1st quarter! 2nd quarter!
Version 1! Version 2! Version 3! Version 4!
Acquisition: Free Revenue: in-app Retention! Acquisition: New
app! purchases! segment!
• Basic game • Purchase dance • New characters • Street dance
functionality! moves! and floors! elements!
• Multiplayer! • Create new dances! • Enhanced visual • Dance competition!
• FB integration! design!
Downloads: top 10 At least 10% of users Daily active Downloads!
dance app! make one in-app players, session
purchase! length!
© 2006-2014 Pichler Consulting Ltd 13
The GO Roadmap Template
Download at
romanpichler.
com/
tools/product-
ro a d ma p
© 2006-2014 Pichler Consulting Ltd 14
Tips for Creating the GO Roadmap
Tell a convincing Have the courage Keep your roadmap
and realistic story. to say no. simple and easy to
understand.
Create buy-in by Choose a realistic Determine the right
involving key timeframe. innovation cadence.
stakeholders.
Prioritise Derive features
Use helpful metrics.
date vs. goal. from goals.
© 2006-2014 Pichler Consulting Ltd 15
The Roadmap Creation Workshop
Validated!
Vision Board
!
op &
Value pr
biz model!
Product Owner Dev Team Members
Involve key! Marketer Sales Rep Mgmt
Sponsor
stakeholders!
2-4 hours! GO Roadmap
© 2006-2014 Pichler Consulting Ltd 16
The Roadmap and the Backlog
GO Product Roadmap
Goals!
Strategic! for several!
major releases!
Details !
Tactical! for the next !
major release!
Product
Backlog
© 2006-2014 Pichler Consulting Ltd 17
Managing
the Roadmap
Roadmap Review and Update
• Your
roadmap
is
not
a
fixed
plan;
it
will
change.
– New
ideas
come
up,
progress
is
not
as
an?cipated,
the
market
and
the
compe??ve
landscape
change.
– The
changes
may
be
small
or
big.
• Regularly
review
and
update
your
roadmap.
– The
more
change
and
uncertainty
there
is,
the
more
frequently
you
should
you
check
your
roadmap.
– Tip:
Start
with
monthly
reviews
and
adapt.
– Involve
development
team
members
and
key
stakeholders
to
leverage
their
knowledge
and
to
create
buy-‐in.
© 2006-2014 Pichler Consulting Ltd 19
Incremental Changes
• Incremental
changes
help
you
implement
your
exis?ng
product
strategy.
This
assumes
that
your
strategy
is
valid.
• Examples
are
revising
a
goal,
changing
a
date
or
a
feature,
and
adjus?ng
the
metrics.
GO Roadmap
Adjust!
© 2006-2014 Pichler Consulting Ltd 20
Big Changes
• Big
changes
are
needed
when
the
strategy
that
was
used
to
create
the
roadmap
is
no
longer
valid.
– You
want
to
address
a
new
market
segment
and
new
needs,
for
instance,
or
you
experience
a
pivot.
• Your
exis?ng
roadmap
is
no
longer
valid.
Bigger Update
or Pivot New or ! New or!
changed! reworked!
strategy! roadmap!
© 2006-2014 Pichler Consulting Ltd 21
Roadmap Ownership
GO Roadmap
Owns and! Contribute!
manages!
Product Stakeholders
Owner
Contribute!
Development
Team Members
© 2006-2014 Pichler Consulting Ltd 22
More Info
Attend my Training Course
Available!
for onsite!
delivery!
Register at http://www.romanpichler.com/training-courses/
© 2006-2014 Pichler Consulting Ltd 24
You can find more info on agile roadmaps at:!
romanpichler.com/tools/product-roadmap!
I look forward to your feedback and questions:!
info@romanpichler.com!
@romanpichler!