Comments on: 10 Tips for Creating an Agile Product Roadmap

By: Roman Pichler

Roman Pichler — Fri, 18 Nov 2022 14:17:43 +0000

In reply to Yazan AlTamimi.

Thank you Yazan! I’m glad that you like it.

By: Yazan AlTamimi

Yazan AlTamimi — Fri, 18 Nov 2022 13:50:29 +0000

What a great article!

By: Roman Pichler

Roman Pichler — Thu, 04 Feb 2021 08:42:43 +0000

In reply to Sara.

Hi Sara,

Thank you for sharing your question. There are two things I would suggest: First, try to agree on outcome-based goals with your stakeholders and development teams rather than focussing on features and pieces of functionality. When someone comes to you with a feature request explore its benefits after having attentively listened to the individual. Would it, for example, reduce cost or increase productivity? Secondly, try to bring the key stakeholders and dev team representative together, be it in an online or onsite meeting. Jointly discuss the roadmap to leverage people’s expertise, ensure that there is a shared understanding, and maximise the chances that people support the product roadmap. Hope this helps!

By: Sara

Sara — Wed, 03 Feb 2021 15:15:54 +0000

I work for a state agency. We have been using agile approach to our system enhancements or fixes. I just read this article to learn what a product roadmap is. I am the product owner for one of our key mission critical systems. It is difficult for me to consider some of the elements of this roadmap as we have constraints to our system that a private business wouldn’t have. As you can imagine it is top down driven, support staffing and budget limited and the customers we support are most often internal. How could we write a product roadmap with these constraints, any ideas would be helpful. Thanks.

By: Roman Pichler

Roman Pichler — Mon, 30 Nov 2020 11:42:42 +0000

In reply to Logan Torres.

Thank you for your kind feedback Logan. I am glad that you found the article helpful.

By: Logan Torres

Logan Torres — Mon, 30 Nov 2020 09:13:26 +0000

Your article has given me lots of ideas. Such great information shared through this article. Its really helpful for me. Thanks for sharing keep up the good work.

By: Shreya Shinde

Shreya Shinde — Wed, 27 Nov 2019 12:29:02 +0000

Your blogs are always helpful and who are managing the agile projects, they can get useful tips after reading this article. Thanks for sharing this useful info.

By: Roman Pichler

Roman Pichler — Thu, 23 May 2019 09:51:21 +0000

In reply to Wei Zhu.

Hi Wei,

Thank you for your feedback and question. If your product’s business goals are tied to the user needs/goals, which I would recommend, then you can choose either option. I’ve used business goals in past and expressed the user benefit indirectly by deriving the appropriate features. But you may want to try working with dual goals, for example, “Make it easier for users to do and increase retention by “, in order to clearly express the benefits for the users and business. I’ve written more about the relationship of product strategy and roadmap goals in my article “Leading through Shared Goals“.

Hope this helps!

By: Wei Zhu

Wei Zhu — Wed, 22 May 2019 01:37:36 +0000

Hi Roman,
Thank you for sharing your knowledge of Agile product management! I learned a lot from your books (Strategize) and your blogs.

Regarding setting the release goals on product roadmap, I have one question:

Should we set goal from perspectives of company’s benefits (business goals) or from user’s perspectives? Example of company business perspective goal might be “increase retention rate by 2%”. Example of user perspective goal might be “Optimize the user experiences” .

Thanks,

Wei

By: Roman Pichler

Roman Pichler — Wed, 24 Apr 2019 07:29:10 +0000

In reply to Steve Forbes.

Thank you for your feedback Steve. Great to hear that you find it helpful to align people through shared goals.