|
|
| Line 1: |
Line 1: |
| | | | |
| − | == Abstract == | + | == Abstract (0/150)== |
| | Abstract here | | Abstract here |
| | | | |
| | | | |
| | | | |
| − | == Overview == | + | == Roadmap Methodology (0/500)== |
| − | 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 == | + | === Purpose (0/150)=== |
| − | 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."''<ref>[''A/B''] ''http://tfi.com/pubs/w/pdf/ti_sroadmaps.pdf'' </ref>
| + | === Key Aspects (0/350)=== |
| | | | |
| − | Bob Galvin, past Chairman of the Board of Motorola
| + | == Roadmaps for Program Management (0/700)== |
| | | | |
| − | 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.
| + | === Definition of Programs (0/300)=== |
| | | | |
| − | === Key Characteristics === | + | === Administration of Programs (0/400)=== |
| − | 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.
| + | |
| | | | |
| | + | == Roadmapping Process (0/1.000)== |
| | | | |
| − | | + | == Discussion (0/500)== |
| − | 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
| + | |
| − | | + | |
| − | == References ==
| + | |
| − | | + | |
| − | <references/>
| + | |
