Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to build a roadmap ?

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →
Avatar for Guillaume Guillaume
December 10, 2019

How to build a roadmap ?

Key ideas on how to build a Product roadmap

This presentation explains how to define and communicate a product roadmap. This is explained through the mistakes and lessons I've learned in my various jobs.

Avatar for Guillaume

Guillaume

December 10, 2019

Other Decks in Technology

Transcript

  1. Current role D A D & P R O D

    U C T M A N A G E R Background C O M P U T E R S C I E N C E & M A N A G E M E N T Worked at J P M O R G A N / E D F F I S E R V / I N E X T E N S O D I G I T A L Where S W I T Z E R L A N D / U S A N E W Z E A L A N D / F R A N C E G U I L L A U M E P E R C H A I S
  2. • No start and end date • Not linear, more

    iterative • Cycle, not milestones Product management vs. Project management
  3. The product vision or at least the company vision. Examples:

    Fiserv : Mobiliti Product “Make mobile banking easier than online banking” Gitlab https:/ /about.gitlab.com/company/strategy/#vision Share the vision
  4. Share the objectives This is the value you are bringing.

    Examples: Fiserv : Mobiliti Product “Quick access to balance” “Cash out with mobile” In Extenso Digital Dashboard “Combine data sources” “Share dashboard”
  5. Objective = Where Avoid describing how or what will be

    implemented, only share your intent. The way you get there could change.
  6. Share the timeframe This is not a date, this is

    a priority. Stakeholders need to understand your priorities.
  7. Timing to share No good time, just think about your

    audience Fiserv Forum June +6.000 attendees User group Jan 15 attendees User group Apr 15 attendees User group Jul 15 attendees User group Oct 15 attendees
  8. The unexpected @ Sept. 2013: Apple launches Touch ID with

    iOS7 Expected in a banking app, but.. • 1 month estimated effort • No device to test
  9. “Force majeure” Some items arrive unplanned and must be done:

    - Legal requirements, New regulation, .. (Prices, ..) - New devices/upgrades (iOS, Notch, ..) - 3rd party dependencies (Google Maps pricing, ..) … They could be large and therefore will impact your roadmap. Estimate exposure & allocate bandwidth
  10. The usual @ In 2017, the teams with own backlog

    of bugs Not able to juggle between short term and long term. Critical bugs / client demos were consuming the bandwidth.
  11. Some small changes are urgent and unplanned. They distract the

    team and bring a short term focus. Use a dedicated bandwidth (specific day vs. specific people) Urgent changes Read more about our transition : https:/ /medium.com/inexdigital-fr/how-to-keep- delivering-features-while-doing-production-support-cab2c0430838
  12. Ressources • Listen: French PM podcast www.lafrenchtouch.fm LPCx talks &

    videos https:/ /laproductconf.com/lpcx/ • Talk: Large (EN speaking) PM community mindtheproduct.slack.com • Meet: Meetups @ Aix / Marseille LPCx, Flupa www.meetup.com • Job: PM, Devs roles available www.inextenso.digital/careers [email protected]