Comments on: The GO Portfolio Roadmap

By: Roman Pichler

Roman Pichler — Fri, 04 Feb 2022 14:47:13 +0000

In reply to Chris. Hi Chris, Thanks for sharing your questions. To find the right answers to your questions, I recommend that you read the following articles: The GO Product Roadmap The Product Roadmap and the Product Backlog The Product Roadmap and the Release Plan Hope this helps.

By: Chris

Chris — Fri, 04 Feb 2022 10:43:47 +0000

Hi Roman, I am looking to implement the GO Portfolio Roadmap framework in a new digital platform and have a few questions:

What is the best digital platform for a GO Portfolio Roadmap?
Would the GO Portfolio format work with columns that relate to months or agile sprints instead of quarters?
What happens if it is not possible to complete a feature within one of the columns and then you need to adjust all future columns?
Is there a way to drill down into the features so that progress and product requirements can be viewed in more detail?
Is there a way for the actual metrics to be dynamically populated to complement the desired metrics?
How do product managers own a swimlane in the roadmap if all their initiatives relate to multiple products within the portfolio?
Do you use a delivery plan to complement the GO product/portfolio roadmap?

Best, Chris

By: Roman Pichler

Roman Pichler — Mon, 18 Jan 2021 08:50:36 +0000

In reply to Sophie Olyphant.

Thank you for you feedback and sharing the question Sophie. If you want to make the dependencies explicit, try the following: Create a new row called “Dependencies” to describe a depency the training app might have on beach body app, to stay with the example given in the article. Alternatively, visualise the dependencies with (annotated) arrows assuming that the tool you use supports this. Hope this helps!

By: Sophie Olyphant

Sophie Olyphant — Fri, 15 Jan 2021 22:19:31 +0000

This is really helpful, thank you.
How would you display/highlight any dependencies please?
Thanks

By: Roman Pichler

Roman Pichler — Fri, 18 Jan 2019 13:11:58 +0000

In reply to Lorna.

Hi Lorna,

Thanks for sharing your question. I suggest you simply add the new or changed features to the appropriate lines/products on your portfolio roadmap. Please bear in mind, though, that the features should serve a goal on a goal-oriented roadmap.

Does this help?

By: Lorna

Lorna — Fri, 18 Jan 2019 06:53:10 +0000

Hi Roman, I’m working to define a portfolio roadmap where there are multiple business initiatives with deadlines affecting multiple products at the same time. An example might be an initiative to implement a new business process with a deadline that ultimately involves changes or new features across a host of existing products and another initiative to implement a new business process that affects the same products but involves different features or changes to a shared data model. How would you show this?

By: Roman Pichler

Roman Pichler — Thu, 01 Jun 2017 07:47:22 +0000

In reply to Matt.

Hi Matt,

Thanks for your question. Generally, I recommend creating a separate vision and strategy for each product, unless you work for a startup. The company vision should guide the product visions, and the business strategy should direct the product strategies. I describe the relationships in more detail in my book Strategize.

Hope this helps!

By: Matt

Matt — Wed, 31 May 2017 21:24:39 +0000

Hi Roman!

If we have an overarching Company Vision/Strategy and 2 or more teams that each are responsible for individual products, do we create a vision/strategy for each team’s products in addition to an overarching product vision/strategy? I’m confused. 🙂

Best
Matt

By: Roman Pichler

Roman Pichler — Tue, 18 Apr 2017 14:30:41 +0000

In reply to Natalia. Hi Natalia, I recommend revisiting your notion of what a product is along the lines I discuss in my article "What is a Digital Product?". If you are dealing with one product, then this product should have one product strategy and one Product Vision Board. Does this help?

By: Natalia

Natalia — Thu, 06 Apr 2017 12:51:37 +0000

Hello Roman,
I find the idea with Portfolio board great. Though I think of applying it to different features of the big Product but not products. We have several feature POs. Each of them works with stakeholders and cares about requiements for the feature (feature Vision Board, prioritizing of backlog for feature, etc.). At the same time we have a POs meeting, where we are going to make a global prioritizing. We do not have PO of POs – we are altogether should do a final decision. Of course there is information about the company strategy and goals. This should serve for global prioritization. This is the idea. For this pupose Portfolio Board could be useful.
What do you think about this usecase?

It would be very interesting to hear your opinion about this.