Technology Roadmapping
(→Key Characteristics and Purposes) |
(→How to read a Roadmap) |
||
| (18 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | == Abstract == | + | == Abstract (167/200)== |
| − | + | A technology roadmap is a time-based chart that aligns multiple planning layers (such as marketing-, product-, development-plan) with strategic business objectives. Its main idea is to create one integrated planning approach. This way, strategic pathways towards specific trajectories can be found, compared and decided while taking into account the planning elements’ interdependencies, mutual requirements and synergies. Due to this holistic approach, (technology) roadmaps are a valuable tool for program management in organisations in two ways: | |
| + | #To analyse and define the need for initiatives and/or programs as well as their design; | ||
| + | #To administer programs and their underlying activities including their interdependencies. | ||
| + | In this article, the key aspects of roadmaps and their purposes are described. Afterwards, the utilisation and the benefits of roadmapping for program management are discussed both for definition as well as administration purposes. Finally, an approach to facilitate a continuous roadmapping process is presented alongside key aspects of best practises. Finally limitations are discussed including comparison with different program management approaches, and supporting measures. | ||
| − | == | + | == Roadmap Methodology (0/600)== |
| − | + | Originally, roadmaps were developed as "Product Roadmaps" that integrated technology and product planning. One of the most prominent pioneers of this approach was Motorola in the 1970s. | |
| + | Over time, and depending on their utilisation different roadmaps for different purposes emerged. However all of the share a common architecture. | ||
| − | == Key | + | === Key Aspects (0/350)=== |
| − | + | Roadmaps are time-based charts that depict projects, initiatives, technologies and other planning objects on several layers. Typically, these layers can be joined into three main perspectives (blocks): | |
| − | + | #Resources Perspective (bottom-layers): e.g. technologies, resources; | |
| + | #Delivery Perspective (middle-layers): e.g. products, services, systems; | ||
| + | #Purpose Perspective (top-layers): e.g. markets, business, strategy. | ||
| − | + | A more detailed overview can be found in figure XX. | |
| − | + | The timeframe (x-axis) typically spans several years and may include the past as well for reference. Depending on the purpose, it can also include non-specific time designations such as "Now", "Plan", "Stratagy" and the like. | |
| − | + | Within this framework, bars, milestones and arrows are arranged to represent the activities/initiatives etc. and their interrelations. | |
| − | + | ||
| − | + | ||
| + | However, timeframe, layers as well as the type of activities etc. represented often are (and should be) subject to customization according to the specific case. The most important aspect for this customization is the purpose of the roadmap that may differ broadly. | ||
| − | === | + | === How to read a Roadmap === |
| + | Typically roadmaps can be understood following a diagonal from the bottom-left to the top-right corner (as indicated in figure XX). Depending on the direction along this line, one follows either the market pull or technology push. Following the top-down direction, the market pull is first represented by the strategic business goal, that propagates through the product portfolio plan, and finally the technologies and resources to be developed. Thus a holistic approach to fulfilling market needs can be tracked and/or planned. The other way around (bottom up) one may estimate the effects of a new technology and how it can affects future products and therefore shape markets. | ||
| − | == | + | === Purposes (0/150)=== |
| − | + | == Roadmaps for Program Management (0/700)== | |
| − | + | ||
| − | == | + | === Definition of Programs (0/300)=== |
| − | + | === Administration of Programs (0/400)=== | |
| − | Discussion | + | |
| + | == Roadmapping Process (0/1.000)== | ||
| + | |||
| + | == Discussion (0/500)== | ||
Latest revision as of 09:20, 11 September 2016
Contents |
[edit] Abstract (167/200)
A technology roadmap is a time-based chart that aligns multiple planning layers (such as marketing-, product-, development-plan) with strategic business objectives. Its main idea is to create one integrated planning approach. This way, strategic pathways towards specific trajectories can be found, compared and decided while taking into account the planning elements’ interdependencies, mutual requirements and synergies. Due to this holistic approach, (technology) roadmaps are a valuable tool for program management in organisations in two ways:
- To analyse and define the need for initiatives and/or programs as well as their design;
- To administer programs and their underlying activities including their interdependencies.
In this article, the key aspects of roadmaps and their purposes are described. Afterwards, the utilisation and the benefits of roadmapping for program management are discussed both for definition as well as administration purposes. Finally, an approach to facilitate a continuous roadmapping process is presented alongside key aspects of best practises. Finally limitations are discussed including comparison with different program management approaches, and supporting measures.
[edit] Roadmap Methodology (0/600)
Originally, roadmaps were developed as "Product Roadmaps" that integrated technology and product planning. One of the most prominent pioneers of this approach was Motorola in the 1970s. Over time, and depending on their utilisation different roadmaps for different purposes emerged. However all of the share a common architecture.
[edit] Key Aspects (0/350)
Roadmaps are time-based charts that depict projects, initiatives, technologies and other planning objects on several layers. Typically, these layers can be joined into three main perspectives (blocks):
- Resources Perspective (bottom-layers): e.g. technologies, resources;
- Delivery Perspective (middle-layers): e.g. products, services, systems;
- Purpose Perspective (top-layers): e.g. markets, business, strategy.
A more detailed overview can be found in figure XX.
The timeframe (x-axis) typically spans several years and may include the past as well for reference. Depending on the purpose, it can also include non-specific time designations such as "Now", "Plan", "Stratagy" and the like.
Within this framework, bars, milestones and arrows are arranged to represent the activities/initiatives etc. and their interrelations.
However, timeframe, layers as well as the type of activities etc. represented often are (and should be) subject to customization according to the specific case. The most important aspect for this customization is the purpose of the roadmap that may differ broadly.
[edit] How to read a Roadmap
Typically roadmaps can be understood following a diagonal from the bottom-left to the top-right corner (as indicated in figure XX). Depending on the direction along this line, one follows either the market pull or technology push. Following the top-down direction, the market pull is first represented by the strategic business goal, that propagates through the product portfolio plan, and finally the technologies and resources to be developed. Thus a holistic approach to fulfilling market needs can be tracked and/or planned. The other way around (bottom up) one may estimate the effects of a new technology and how it can affects future products and therefore shape markets.
