The Product Roadmap Maturity Model DEEP: Validation of a Method for Assessing the Product Roadmap Capabilities of Organizations

Product-Focused Software Process Improvement

Lang

2019

Self Cite

Context: Organizations are increasingly challenged by dynamic and technical market environments. Traditional product roadmapping practices such as detailed and Ąxed long-term planning typically fail in such environments. Therefore, companies are actively seeking ways to improve their product roadmapping approach. Goal: This paper aims at identifying problems and challenges with respect to product roadmapping. In addition, it aims at understanding how companies succeed in improving their roadmapping practices in their respective company contexts. Method: We conducted semi-structured expert interviews with 15 experts from 13 German companies and conducted a thematic data analysis. Results: The analysis showed that a signiĄcant number of companies is still struggling with traditional feature-based product-roadmapping and opinion-based prioritization of features. The most promising areas for improvement are stating the outcomes a company is trying to achieve and making them part of the roadmap, sharing or co-developing the roadmap with stakeholders, and establishing discovery activities.

Section: Problem Statement and Objectivementioning

confidence: 99%

What’s Hot in Product Roadmapping? Key Practices and Success Factors

Product-Focused Software Process Improvement

Lang

2019

Self Cite

“…there is poor communication and cooperation between the different departments of a company [ 2 ]. Moreover, stakeholders often do not have consistent and department-specific representations of a common high-level product roadmap that reflects their information needs (e.g., the department product management requires different information on the product roadmap than the department engineering) [ 3 ]. One consequence of this situation is that often each department identifies and pursues its own goals and creates its own roadmap independently of the larger goals of the company.…”

Section: Introductionmentioning

confidence: 99%

Product Roadmap Alignment – Achieving the Vision Together: A Grey Literature Review

Agile Processes in Software Engineering and Extreme Programming – Workshops

Bogazkoy

et al. 2020

Self Cite

Context: A product roadmap is an important tool in product development. It sets the strategic direction in which the product is to be developed to achieve the company’s vision. However, for product roadmaps to be successful, it is essential that all stakeholders agree with the company’s vision and objectives and are aligned and committed to a common product plan. Objective: In order to gain a better understanding of product roadmap alignment, this paper aims at identifying measures, activities and techniques in order to align the different stakeholders around the product roadmap. Method: We conducted a grey literature review according the guidelines to Garousi et al. Results: Several approaches to gain alignment were identified such as defining and communicating clear objectives based on the product vision, conducting cross-functional workshops, shuttle diplomacy, and mission briefing. In addition, our review identified the “Behavioural Change Stairway Model” that suggests five steps to gain alignment by building empathy and a trustful relationship.

Product Roadmapping Processes for an Uncertain Market Environment: A Grey Literature Review

Lecture Notes in Business Information Processing

Schneider

et al. 2021

material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. The publisher, the authors and the editors are safe to assume that the advice and information in this book are believed to be true and accurate at the date of publication. Neither the publisher nor the authors or the editors give a warranty, expressed or implied, with respect to the material contained herein or for any errors or omissions that may have been made. The publisher remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.