Technology Roadmapping
(→Key Characteristics and Purposes) |
(→Key Characteristics and Purposes) |
||
Line 12: | Line 12: | ||
''"[...] assure that we put in motion today what is necessary in order to have the right technology, processes, components, and experience in place to meet the future needs for products and services."'' | ''"[...] assure that we put in motion today what is necessary in order to have the right technology, processes, components, and experience in place to meet the future needs for products and services."'' | ||
+ | |||
Bob Galvin, past Chairman of the Board of Motorola | Bob Galvin, past Chairman of the Board of Motorola | ||
+ | |||
+ | Since then, numerous types of Technology Roadmaps have been developed and used, thus emphasizing the methods variability as well as the need for customization to the practical case. Common to all of them is their fundamental architecture, that includes different planning-layers (y-axis) and the time domain (x-axis). | ||
WHY TO DO IT AND WHAT IT LOOKS LIKE | WHY TO DO IT AND WHAT IT LOOKS LIKE |
Revision as of 10:30, 8 September 2016
Contents |
Abstract
Abstract here
Overview
Technology Roadmapping aligns technology development with strategic business objectives over a specific timeframe. The general idea is to create fit across all planning-objects. Instead of having multiple seperated planning-layers (such as technology-plan, project-plan, and product-plan) a Technology Roadmap therefore integrates these to form one holistic approach that coordinates the different layers and takes into account their interdependencies, mutual requirements and synergies.
Key Characteristics and Purposes
Technology Roadmaps were introduced by Motorola in the 1970s with the purpose to:
"[...] assure that we put in motion today what is necessary in order to have the right technology, processes, components, and experience in place to meet the future needs for products and services."
Bob Galvin, past Chairman of the Board of Motorola
Since then, numerous types of Technology Roadmaps have been developed and used, thus emphasizing the methods variability as well as the need for customization to the practical case. Common to all of them is their fundamental architecture, that includes different planning-layers (y-axis) and the time domain (x-axis).
WHY TO DO IT AND WHAT IT LOOKS LIKE Key Characteristics Different Purposes
Methodology and Application
HOW TO DO IT Methodologies and Steps here
Discussion
WHAT TO CONSIDER Discussion here