Roadmapping in Program Management
(→Understanding Roadmaps) |
(→How to read Roadmaps) |
||
| Line 26: | Line 26: | ||
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. | 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 Roadmaps=== | + | ===How to read Roadmaps (104/150)=== |
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. 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. | 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. 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. | ||
===Types of roadmaps=== | ===Types of roadmaps=== | ||
Revision as of 12:33, 11 September 2016
Contents |
Abstract (171/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.
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. As a third step, 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.
Understanding Roadmaps (46/100)
Roadmaps were first broadly introduced in the 1970s when pioneers like Motorola used them to integrate their technology and product development/planning. Since then, several types of roadmaps have been developed for different purposes (see "Types of Roadmaps"). Most roadmaps however share commonalities which are described below.
Key Aspects of Roadmaps (160/160)
Roadmaps are time-based charts that depict projects, initiatives, technologies and other planning objects on several layers. Typically, these layers can be joined to three main perspectives (blocks):
- Resource perspective (bottom-layers): e.g. technologies, resources
- Delivery perspective (middle-layers): e.g. products, services, systems
- Purpose perspective (top-layers): strategic objectives, markets, business
A more detailed overview including possible layer-categories can be found in figure XX.
The timeframe (x-axis) typically spans several years and may include the past as well for reference. Even though specific dates will increase the roadmap's explanatory power, relatively vague estimates (such as "now", "plans", "strategy") may be useful in some cases.
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 Roadmaps (104/150)
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. 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.
