practical guide to product roadmapping
DESCRIPTION
Tired of reading textbooks on product management theory? In this session, Ram and Joe will discuss the practical real world issues, concerns, and best practices when developing and communicating roadmaps. We will debunk the preconceived notions of what a roadmap is as well as its recommended uses. Also bring along your biggest challenges you have with roadmapping and we'll take some time discuss them. Ram Sarabu -- VP Product Development, SAP Labs Joe Granda -- EVP Marketing, Wellspring WorldwideTRANSCRIPT
PDMA Chicago: Prac/cal Guide to Roadmapping Product Innova/on
Ram Sarabu, VP Product Development, SAP Joe Granda, EVP Marke<ng, Wellspring
A PLAN THAT MATCHES SHORT-‐TERM AND LONG-‐TERM GOALS WITH SPECIFIC SOLUTIONS TO HELP MEET THOSE GOALS.
Product Roadmap
Build consensus
Forecast tech requirements
Framework to coordinate development
11 Prac<cal Lessons Learned
1. Roadmapping is a boring exercise
2. Roadmap ≠ PowerPoint
3. Roadmaps without <melines are pointless
4. Roadmaps are not technical specs
5. Roadmaps are not demos
6. Roadmaps are not constant
7. Roadmap is about what & when
Feature/Product
Q1 Q2 Q3 Q4
A ddd eee fff ggg
B hhh iii jjj kkk
C mmm nnn ooo ppp
8. Roadmap is not for you, but for others
9. Roadmap is an outcome, roadmapping is the process behind it
GANTT CHARTPROJECT EE4 - SSV
Tijd
span
ne
Ver
wac
hte
wer
kduu
r
Act
uele
wer
kduu
r
Hen
drik
Koe
n
Tom
Wou
ter
Chr
isto
ph
Que
ntin
Werkopdrachten Taken Deeltaken Niveau 1 Deeltaken Niveau 2 Deeltaken Niveau 3 Verantwoordelijke Weken Uren Uren Uren Uren Uren Uren Uren Uren 1 2 3 4 5 6 7 8 9 10 11 12 13 141. Planning/oriëntatie 1.1 Gantt Chart 1.1.1 Voorlopige Gant Chart maken 1 3 0,5 0,5 0,5 0,5 0,5 0,5
1.1.2 Definitieve Gant Chart maken Quentin 1 0,5 0,51.1.3 Aanvullen Gantt Chart Quentin 1 2 1 1
1.2 WBS 1.2.1 Voorlopige WBS maken 1 3 0,5 0,5 0,5 0,5 0,5 0,51.2.2 Definitieve WBS maken Hendrik 1 0,5 0,5
1.3 Plan van aanpak 1.3.1 Voorlopig PVA maken 1 3 0,5 0,5 0,5 0,5 0,5 0,51.3.2 Definitief PVA maken Koen 1 1 1
1.4 Samenwerkingscontract 1.4.1 Voorlopig SWC maken 1 3 0,5 0,5 0,5 0,5 0,5 0,51.4.2 Definitief SWC maken Tom 1 1 1
2. Engineering aspect 2.1 Case SSV, Deel 1 2.1.1 Metingen en Berekeningen 2.1.1.1 Bepalen karakteristieken van het zonnepaneel Koen 1 4 0,5 1 1 0,5 0,5 0,52.1.1.2 Optimale ratio tussen motor en wielen Tom 1 12 4 82.1.1.3 Bisectiemethode Hendrik 1 4 2 22.1.1.4 Sankey Diagramma Wouter 1 2 1 1
2.1.2 Conceptuitwerking 2.1.2.1 Brainstorm 3 18 3 3 3 3 3 32.1.2.2 Evaluatie ideeën 2 6 1 1 1 1 1 12.1.2.3 Maken van concepttekeningen Hendrik 3 1 2
2.1.3 Ontwerp 2.1.3.1 Research 2 12 2 2 2 2 2 22.1.3.2 Materiaalkeuze 2.1.3.2a Optimale materiaal Christoph 2 3 1,5 1,5
2.1.3.2b Optimale vorm Quentin 2 5 2,5 2,52.1.3.2c Banden/wielen Wouter 2 4 2 2
2.1.4 Uitvoering 2.1.4.1 Fabricage onderdelen (Fablab) Koen 2 18 3 3 3 3 3 32.1.4.2 Bouwen van SSV Wouter 4 40 8 4 6 8 8 82.1.4.3 Testfase Tom 2 4 2 2 22.1.4.4 Optimalisatie (m.b.v. Matlab) Quentin 3 8 4 42.1.4.5 Esthetische opwaardering Hendrik 1 4 2 2
2.2 Case Simulink 2.2.1 Simulatie Christoph 3 8 82.2.2 Optimalisatie Quentin 3 8 4 4
2.3 Case SSV, Deel 2 2.3.1 Analyse 2.3.1.1 Vermogensverdeling Hendrik 3 13 3 5 52.3.1.2 Belasting aandrijflijn Koen 3 12 3 3 3 32.3.1.3 Belasting door impact Christoph 3 8 5 3
2.3.2 Technisch tekenen Wouter 3 40 10 4 4 8 10 42.4 Race 4 12 2 2 2 2 2 2
3. Enterprising aspect 3.1 Naam bedenken 1 3 0,5 0,5 0,5 0,5 0,5 0,53.2 Logo 3.2.1 Logo maken Hendrik 1 3 3
3.2.2 Logo Graveren in SSV Christoph 2 1 13.3 Online beheer 3.3.1 Blog Koen 11 6 6
3.3.2 Wiki Koen 11 12 123.4 Slogan bedenken Quentin 2 0,5 0,53.5 Kostenberekening maken Tom 3 8 8
4. Educating aspect 4.1 Vergaderingen 4.1.1 Vergaderen 12 24 4 4 4 4 4 44.1.2 Verslagen maken 12 6 1 1 1 1 1 1
4.2 Seminaries volgen 5 30 5 5 5 5 5 54.3 Testen 4.3.1 Studeren voor testen 4 24 4 4 4 4 4 4
4.3.2 Testen afleggen 4.3.2.1 Test 1 1 12 2 2 2 2 2 24.3.2.2 Test 2 1 12 2 2 2 2 2 2
4.4 Peer Assessment invullen 4.4.1 Peer Assessment 1 1 3 0,5 0,5 0,5 0,5 0,5 0,54.4.2 Peer Assessment 2 1 3 0,5 0,5 0,5 0,5 0,5 0,5
4.5 Verslagen 4.5.1 Technisch Verslag 4.5.1.1 Schrijven 6 66 11 11 11 11 11 114.5.1.2 Nalezen Tom 4 6 3 34.5.1.3 Evaluatie 1 6 1 1 1 1 1 14.5.1.4 Aanpassing 4 3 0,5 0,5 0,5 0,5 0,5 0,5
4.5.2 Procesverslag 4.5.2.1 Schrijven Koen 7 24 4 4 4 4 4 44.5.2.2 Nalezen Hendrik 5 4,5 1,5 1,5 1,54.5.2.3 Evaluatie 1 6 1 1 1 1 1 14.5.2.4 Aanpassing 5 3 0,5 0,5 0,5 0,5 0,5 0,5
4.6 Dossierbeheer Hendrik 12 6 6TOTAAL UREN 535 92,5 93 87,5 84 93 90
Wee
k
10. Roadmap is not a project plan or a schedule
11. Roadmap is an implied commitment
What is delivered * When in <melines * How much and how long is up to you and your team
Roadmap must contain What and When
Research tech, market, and compe<<on
Priori<ze deliverables
Collaborate