Technology Roadmapping
(→Key Characteristics and Purposes) |
(→Key Characteristics) |
||
| Line 18: | Line 18: | ||
=== Key Characteristics === | === Key Characteristics === | ||
| − | Most common is the | + | Most common is the visualization of planning-layers (y-axis) over the time-domain (x-axis)(see figure X). Within the layers, boxes represent the projects (and their duration), product (lifecycles) and so on. Arrows generally depict the dependencies between elements and/or sequential activities. |
| − | |||
| + | |||
| + | In some cases however, there are deviations (e.g. Integration planning). | ||
=== Types of Technology Roadmaps by purpose === | === Types of Technology Roadmaps by purpose === | ||
Revision as of 11:50, 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."[1]
Bob Galvin, past Chairman of the Board of Motorola
Since then, numerous types of Technology Roadmaps and visualizations have been developed and used, thus emphasizing the methods variability as well as the need for customization to the practical case.
Key Characteristics
Most common is the visualization of planning-layers (y-axis) over the time-domain (x-axis)(see figure X). Within the layers, boxes represent the projects (and their duration), product (lifecycles) and so on. Arrows generally depict the dependencies between elements and/or sequential activities.
In some cases however, there are deviations (e.g. Integration planning).
Types of Technology Roadmaps by purpose
Products planning
Service/Capability planning
Strategic planning
Long-range planning
Knowledge asset planning
Programme planning
Process planning
Integration planning
Methodology and Application
HOW TO DO IT Methodologies and Steps here
Discussion
WHAT TO CONSIDER Discussion here
