#7,915 in Business & money books
Use arrows to jump to the previous/next product

Reddit mentions of Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty

Sentiment score: 1
Reddit mentions: 1

We found 1 Reddit mentions of Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty. Here are the top ones.

Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty
Buying options
View on Amazon.com
or
Specs:
Height7.5 Inches
Length9.25 Inches
Number of items1
Weight1.46827866492 Pounds
Width0.5 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 1 comment on Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty:

u/whitew0lf ยท 2 pointsr/ProductManagement

ok so.. first of all, a product roadmap includes no dates or timelines. This is a release plan, which comes after you have prioritized and planned your strategy. Drop the dates now.

A product roadmap is meant to communicate strategy - what you're doing, why you're doing it, and how this relates back to your product vision.

To answer your specific questions:

What is the typical format of a roadmap - a huge graph with major features embedded?

No, no, and no. A typical roadmap communicates strategy, not execution. Execution comes AFTER, not before strategy. Your roadmap should focus on themes (what, why) not releases (how) and not be based on features you are releasing.

How do I come up with the release schedules (past teams I've worked on do weekly)?

Release scheduling is primarily a dev function, but on smaller teams something the product manager will be in charge of. You need to plan weekly sprints with your team, figure out their workload, and then work in releases. If you're agile, you can release up to twice a week (we do that.) Remember that releases will include both new and existing issues. (features and bugs.)

I've been asked to go up to 8 quarters (!) ahead of time. Is this even reasonable? I know priorities change often, so I'm not really sure how useful it is to go that far. I don't want to fall into the trap of constantly re-working my roadmap by stretching time so far away.

You are absolutely falling into a trap, because again, you shouldn't be planning your product roadmap in terms of releases. You're confusing release planning and product roadmapping, and even trying to attempt to plan your releases 8 quarters in advance is a nightmare.


Any useful resources out there for this (software, templates, articles)?

Yes:
Themes: A Small Change to Product Roadmaps With Large Effects by Jared Spool
Drop Feature-Based Roadmaps by Teresa Torres
How to build a product roadmap everyone understands by Andrea Saez
Product Roadmaps Relaunched by C. Todd Lombardo, Bruce McCarthy, Evan Ryan, Michael Connors - available on Amazon