Technology roadmapping—A planning framework for evolution and revolution

Phaal, Robert; Farrukh, Clare; Probert, David

doi:10.1016/s0040-1625(03)00072-6

Cited by 913 publications

(600 citation statements)

References 17 publications

Supporting

Mentioning

511

Contrasting

Unclassified

Order By: Relevance

“…The case shows how feature trees can integrate roadmapping [35] and software specification. It has extended a the layered form of product roadmaps encountered in small companies [40] with explicit traceability to product feature.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Release Planning with Feature Trees: Industrial Case

Fricker

Schumacher

2012

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and motivation] Requirements catalogues for software release planning are often not complete and homogeneous. Current release planning approaches, however, assume such commitment to detail -at least implicitly. [Question/problem] We evaluate how to relax these expectations, while at the same time reducing release planning effort and increasing decisionmaking flexibility. [Principal ideas/results] Feature trees capture AND, OR, and REQUIRES relationships between requirements. Such requirements structuring can be used to hide incompleteness and to support abstraction. [Contribution] The paper describes how to utilize feature trees for planning the releases of an evolving software solution and evaluates the effects of the approach on effort, decision-making, and trust with an industrial case.Keywords: features, abstraction, release planning, roadmapping, case study. IntroductionSoftware releases are planned by allocating requirements to development projects [1]. A strategic release plan aligns the development of an evolving software solution with market and stakeholder needs, company objectives, and constraints such as time and resources. Release planning is a central concern in iterative development, where multiple iterations, rather than a single project, are defined [2]. Release planning involves the following steps [3]. Requirements are elicited and specified. Criteria [4] are defined to evaluate and prioritize requirements [5]. Releases are then scoped by allocating the prioritized requirements to development projects. The resulting release plans are implemented, delivered, and analyzed with post-release reflections [6].Requirements that enter release planning are often of low quality [7]. Their homogeneity [8], completeness, and understanding [9] are hard to ensure due to the limited effort invested before a development project is funded. This situation contradicts with the assumptions of release planning approaches that scope projects simply by prioritizing and allocating available requirements. Consequently, the results are not trusted and not used for guiding ensuing development steps [10].Release Planning with Feature Trees: Industrial Case 289 This paper describes in detail how to hide the requirements-related problems by structuring the release planning inputs. The approach, whose initial ideas were introduced in an earlier position paper [11], is based on variability modeling [12] that allows abstracting from requirements with AND, OR, and REQUIRES relationships [13]. Variability is here used to structure decision options [14] for product evolution. This paper then introduces an industrial case [15] to understand how to use variability modeling in a real-world context of continuous agile product management [16]. Evaluated were feasibility of the approach and its effects on effort, decision-making, and trust were evaluated.The paper is structured as follows. Section 2 describes background and motivation. Section 3 introduces variability-based release planning. Section 4 describe...

show abstract

Section: Discussionmentioning

confidence: 99%

“…To define the feature's development timing the product manager decided to use a detailed, layered product roadmap [35] with a time horizon of two years. Figure 6 shows an extract of the detailed first-year plan.…”

Section: Media Archive Of the Arts Feature Treementioning

confidence: 99%

Release Planning with Feature Trees: Industrial Case

Fricker

Schumacher

2012

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

show abstract

“…Based on the significant work of Phaal et al [14], who summarized previous TRM methods and constructed an effective qualitative composing model, TRM research has already been extended from qualitative study only to a combination of qualitative and quantitative methodologies. Representatively, Huang et al [7] introduced a bibliometrics technique-based four-dimensional TRM for the science and technology planning of China's solar cell industry; Zhang et al [22] combined TRM model with Triple Helix innovation and Semantic TRIZ concepts, and presented an empirical study on China's dye sensitized solar cell industry; Lee et al [11] proposed a scenario-based TRM that involved with a plan assessment map and an activity assessment map for organizational plans, which also engaged the Bayesian network for topology and a causal relations definition.…”

Section: A Technology Roadmappingmentioning

confidence: 99%

“…The traditional Technology Roadmapping (TRM) approaches, described as a representative, prominent, and flexible instrument for long-range technological forecasting and strategic planning, make good sense to actively incorporate business data into planning procedures [14,19]. However, standing on the new situation of the Big Data age, the way that the current TRM study used to transfer vague human thoughts to defined numerical values [9] is still unfavorable, and the combination of qualitative and quantitative methodologies is also not as smart as what we imagine.…”

Section: Introductionmentioning

confidence: 99%

Semi-automatic Technology Roadmapping Composing Method for Multiple Science, Technology, and Innovation Data Incorporation

Zhang

Chen

Zhu

2016

Innovation, Technology, and Knowledge Management

View full text Add to dashboard Cite

Abstract--Since its first engagement with industry decades ago, Technology Roadmapping (TRM) is taking a more and more important role for technical intelligence in current R&D planning and innovation tracking. Important topics for both science policy and engineering management researchers involves with the approaches that refer to the real-world problems, explore value-added information from the complex data sets, fuse the analytic results and expert knowledge effectively and reasonable, and demonstrate to the decision makers visually and understandable. Moreover, the growing variety of science data sources in the Big Data Age increases these challenges and opportunities. Addressing these concerns, this paper proposes a TRM composing method with a clustering-based topic identification model, a multiple science data sources integration model, and a semi-automated fuzzy set-based TRM composing model with expert aid. We focus on a case study on computer science related R&D. Empirical data from the United States National Science Foundation Award data (innovative research ideas and proposals) and Derwent Innovation Index data source (patents emphasizing technical products) provide vantage points at two stages of the R&D process. The understanding gained will assist in description of computer science macro-trends for R&D decision makers.

show abstract

“…Roadmapping is described as the use of a time-based (and often graphical) framework to develop, represent and communicate strategic plans, in terms of the co evolution and development of technology, products and markets; and integrating technology developments with business planning as one of its main perspectives [7].…”

Section: Previous Workmentioning

confidence: 99%