Roadmapping in Program Management - Revision history

Tkokotas at 14:04, 18 December 2018

2018-12-18T14:04:53Z

← Older revision		Revision as of 14:04, 18 December 2018
Line 1:		Line 1:
			''Developed by Sebastian Bauer''


	=='''Overview'''==		=='''Overview'''==
	A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success;'' Springer. [http://www.springer.com/de/book/9783642339226 Link]</ref> Due to this holistic approach, technology roadmaps are a valuable tool for program management in organisations in two ways:		A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success;'' Springer. [http://www.springer.com/de/book/9783642339226 Link]</ref> Due to this holistic approach, technology roadmaps are a valuable tool for program management in organisations in two ways:

Sebastian Bauer: /* Guideline for facilitation */

2016-09-26T14:23:47Z

Guideline for facilitation

← Older revision		Revision as of 14:23, 26 September 2016
Line 121:		Line 121:

	=='''Guideline for facilitation'''==		=='''Guideline for facilitation'''==
	Numerous process descriptions of how to carry out roadmapping exist (e.g. T-Plan-process<ref name="phaal2"/>, Integrated Roadmap process <ref name="ZVEI"> Behrendt, Siegfried (editor) (2007): ''Integrated Technology Roadmapping: A practical guide to the search for technological answers to social challenges and trends''; Zentralverband Elektrotechnik und Elektroindustrie e.V.. [https://www.izt.de/fileadmin/publikationen/IZT_WB87.pdf Link]</ref>, Program roadmap process <ref name="Byrne">Byrne, Kevin et al. (2013): ''How to Prepare a Program Roadmap''; Journal of Evonomic Development, Management, IT, Finance and Marketing, Issue 6.</ref>). They differ vastly due to the different purposes and types of roadmaps, however they all point out three main aspects that are essential to any roadmap:		Numerous process descriptions of how to carry out roadmapping exist (e.g. T-Plan-process<ref name="phaal2"/>, Integrated Roadmap process <ref name="ZVEI"> Behrendt, Siegfried (editor) (2007): ''Integrated Technology Roadmapping: A practical guide to the search for technological answers to social challenges and trends''; Zentralverband Elektrotechnik und Elektroindustrie e.V.. [https://www.izt.de/fileadmin/publikationen/IZT_WB87.pdf Link]</ref>, Program roadmap process <ref name="Byrne">Byrne, Kevin et al. (2013): ''How to Prepare a Program Roadmap''; Journal of Evonomic Development, Management, IT, Finance and Marketing, Issue 6. [http://www.gsmi-ijgb.com/Documents/JEDMITFM%20V6%20N1%20P01%20Kevin%20Byrne%20-Program%20Roadmap.pdf Link]</ref>). They differ vastly due to the different purposes and types of roadmaps, however they all point out three main aspects that are essential to any roadmap:
	{\| class="wikitable"		{\| class="wikitable"
	\|+Key steps of the roadmapping process		\|+Key steps of the roadmapping process

Sebastian Bauer: /* Guideline for facilitation */

2016-09-26T14:22:44Z

Guideline for facilitation

← Older revision		Revision as of 14:22, 26 September 2016
Line 121:		Line 121:

	=='''Guideline for facilitation'''==		=='''Guideline for facilitation'''==
	Numerous process descriptions of how to carry out roadmapping exist (e.g. T-Plan-process<ref name="phaal2"/>, Integrated Roadmap process <ref name="ZVEI"> Behrendt, Siegfried (editor) (2007): ''Integrated Technology Roadmapping: A practical guide to the search for technological answers to social challenges and trends''; Zentralverband Elektrotechnik und Elektroindustrie e.V..</ref>, Program roadmap process <ref name="Byrne">Byrne, Kevin et al. (2013): ''How to Prepare a Program Roadmap''; Journal of Evonomic Development, Management, IT, Finance and Marketing, Issue 6.</ref>). They differ vastly due to the different purposes and types of roadmaps, however they all point out three main aspects that are essential to any roadmap:		Numerous process descriptions of how to carry out roadmapping exist (e.g. T-Plan-process<ref name="phaal2"/>, Integrated Roadmap process <ref name="ZVEI"> Behrendt, Siegfried (editor) (2007): ''Integrated Technology Roadmapping: A practical guide to the search for technological answers to social challenges and trends''; Zentralverband Elektrotechnik und Elektroindustrie e.V.. [https://www.izt.de/fileadmin/publikationen/IZT_WB87.pdf Link]</ref>, Program roadmap process <ref name="Byrne">Byrne, Kevin et al. (2013): ''How to Prepare a Program Roadmap''; Journal of Evonomic Development, Management, IT, Finance and Marketing, Issue 6.</ref>). They differ vastly due to the different purposes and types of roadmaps, however they all point out three main aspects that are essential to any roadmap:
	{\| class="wikitable"		{\| class="wikitable"
	\|+Key steps of the roadmapping process		\|+Key steps of the roadmapping process

Sebastian Bauer: /* Toolbox - Support the process */

2016-09-26T14:21:57Z

Toolbox - Support the process

← Older revision		Revision as of 14:21, 26 September 2016
Line 176:		Line 176:
	#[https://en.wikipedia.org/wiki/Delphi_method '''Delphi-method'''] should be used to gather inside and outside expert's opinions on the initiatives and developments. (Step 3)		#[https://en.wikipedia.org/wiki/Delphi_method '''Delphi-method'''] should be used to gather inside and outside expert's opinions on the initiatives and developments. (Step 3)
	#[https://en.wikipedia.org/wiki/Valuation_(finance) '''Valuation techniques'''] such as net-present value, discounted cash flow, balanced scorecard or the like should be used to assess the different options (projects, technologies, etc.). (Step 3 and 4)		#[https://en.wikipedia.org/wiki/Valuation_(finance) '''Valuation techniques'''] such as net-present value, discounted cash flow, balanced scorecard or the like should be used to assess the different options (projects, technologies, etc.). (Step 3 and 4)
	#'''Linking grids''' similar to Quality Function Deployment these grids link and translate higher-level aspects into lower-level requirements. Thus, they are crucial when linking the roadmaps layers. (See <ref name="phaal2">Phaal, Robert et al. (2001): ''Technology Roadmapping: linking technology resources to business objectives''; University of Cambridge.</ref> for further explanation.) (Step 3)		#'''Linking grids''' similar to Quality Function Deployment these grids link and translate higher-level aspects into lower-level requirements. Thus, they are crucial when linking the roadmaps layers. (See <ref name="phaal2">Phaal, Robert et al. (2001): ''Technology Roadmapping: linking technology resources to business objectives''; University of Cambridge. [https://www.sopheon.com/wp-content/uploads/Article-TechnologyRoadmapping.pdf Link]</ref> for further explanation.) (Step 3)
	#[https://en.wikipedia.org/wiki/Scenario_analysis '''Scenario Techniques'''] should be used to create different pathways and to assess possible future developments. (Step 4)		#[https://en.wikipedia.org/wiki/Scenario_analysis '''Scenario Techniques'''] should be used to create different pathways and to assess possible future developments. (Step 4)
	<br />		<br />

Sebastian Bauer: /* Technology Roadmapping in Program Management */

2016-09-26T14:20:51Z

Technology Roadmapping in Program Management

← Older revision		Revision as of 14:20, 26 September 2016
Line 47:		Line 47:
	Considering the different program performance domains, roadmaps can play out their strengths in program-strategy-alignment, as well as in benefit-orientation and holistic program design.		Considering the different program performance domains, roadmaps can play out their strengths in program-strategy-alignment, as well as in benefit-orientation and holistic program design.
	That being said, they may also be used in the same way for projects (on a smaller scale) as well as to ensure fit within portfolios of projects and programs.		That being said, they may also be used in the same way for projects (on a smaller scale) as well as to ensure fit within portfolios of projects and programs.
	To realize these benefits, roadmaps should be defined when initiating a program and constantly revised over the course of it, to manage the design as well as the execution. Therefore, especially in the program management context, roadmaps are to be seen as dynamic documents.<ref name="Milosevic"> Milosevic, Dragan et al. (2007): ''Program Management for Improved Business Results''; John Wiley & Sons Inc.. </ref>		To realize these benefits, roadmaps should be defined when initiating a program and constantly revised over the course of it, to manage the design as well as the execution. Therefore, especially in the program management context, roadmaps are to be seen as dynamic documents.<ref name="Milosevic"> Milosevic, Dragan et al. (2007): ''Program Management for Improved Business Results''; John Wiley & Sons Inc.. [http://eu.wiley.com/WileyCDA/WileyTitle/productCd-111862792X,subjectCd-BA31.html Link] </ref>

	{\| class="wikitable"		{\| class="wikitable"

Sebastian Bauer: /* References */

2016-09-26T14:19:05Z

References

← Older revision		Revision as of 14:19, 26 September 2016
Line 303:		Line 303:
	==References==		==References==
	<references />		<references />
	Links are provided where possible.		Links are provided where possible.<br \>
	Please note that all figures without explicit citation were created by the author.		Please note that all figures without explicit citation were created by the author.

Sebastian Bauer: /* References */

2016-09-26T14:18:45Z

References

← Older revision		Revision as of 14:18, 26 September 2016
Line 303:		Line 303:
	==References==		==References==
	<references />		<references />
			Links are provided where possible.
	~~Note:~~ all figures without explicit citation were created by the author.		Please note that all figures without explicit citation were created by the author.

Sebastian Bauer: /* Understanding Technology Roadmaps */

2016-09-26T14:16:29Z

Understanding Technology Roadmaps

← Older revision		Revision as of 14:16, 26 September 2016
Line 8:		Line 8:

	=='''Understanding Technology Roadmaps'''==		=='''Understanding Technology Roadmaps'''==
	Technology 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 (e.g. ''Service/Capability Roadmap'' for service-driven companies or ''knowledge asset roadmap'' for knowledge-driven companies). What they have in common is the approach of extrapolating or ‘’forecasting’’ effects of certain elements into the future and/or ''backcasting'' future goals/expected trends into current activities.<ref name="bernal"> Bernal, Luis et al. (2009): ''Technology Roadmapping Handbook''; University of Leipzig.</ref> In order to visualise these aspects, most roadmaps share certain commonalities described below.		Technology 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 (e.g. ''Service/Capability Roadmap'' for service-driven companies or ''knowledge asset roadmap'' for knowledge-driven companies). What they have in common is the approach of extrapolating or ‘’forecasting’’ effects of certain elements into the future and/or ''backcasting'' future goals/expected trends into current activities.<ref name="bernal"> Bernal, Luis et al. (2009): ''Technology Roadmapping Handbook''; University of Leipzig. [http://www.vgu.edu.vn/fileadmin/pictures/studies/MBA/Handbook_Roadmapping.pdf Link]</ref> In order to visualise these aspects, most roadmaps share certain commonalities described below.

	===Key Aspects - What they look like===		===Key Aspects - What they look like===

Sebastian Bauer: /* Overview */

2016-09-26T14:15:37Z

Overview

← Older revision		Revision as of 14:15, 26 September 2016
Line 1:		Line 1:
	=='''Overview'''==		=='''Overview'''==
	A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success; Springer. [http://www.springer.com/de/book/9783642339226 "Link"]</ref> Due to this holistic approach, technology roadmaps are a valuable tool for program management in organisations in two ways:		A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success;'' Springer. [http://www.springer.com/de/book/9783642339226 Link]</ref> 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 analyse and define''' the need for initiatives and/or programs as well as their design;

Sebastian Bauer: /* Overview */

2016-09-26T14:15:05Z

Overview

← Older revision		Revision as of 14:15, 26 September 2016
Line 1:		Line 1:
	=='''Overview'''==		=='''Overview'''==
	A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success; Springer. [[http://www.springer.com/de/book/9783642339226 Link]]</ref> Due to this holistic approach, technology roadmaps are a valuable tool for program management in organisations in two ways:		A 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.<ref name="moehrle">Moehrle, Martin et al. (editors) (2012): ''Technology Roadmapping for Strategy and Innovation: Charting the route to success; Springer. [http://www.springer.com/de/book/9783642339226 "Link"]</ref> 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 analyse and define''' the need for initiatives and/or programs as well as their design;