Roadmapping
| Line 15: | Line 15: | ||
== References == | == References == | ||
| + | [[File:Desert.jpg|frameless|800px]] | ||
| + | Yes, its just a fucking desert, empty and devoid of all substance... Much like the course lectures :) | ||
<references/> | <references/> | ||
Revision as of 14:06, 16 February 2018
Abstract
Programs can become very complicated as they evolve. It can be easy for individual projects to lose track of the program goal. A program manager will have to coordinate between multiple projects each focusing on different areas such as stakeholders, technology, material resources, infrastructure etc. A program manager might have all the necessary resources to ensure a successful program but if none of these resources are working together or if projects meant to support further development are not in place when needed the program will fail. As described by the PMI-standard
“Program management is the centralized coordinated management of a program to achieve the program’s strategic objectives and benefits. It involves aligning multiple projects to achieve the program goals and allows for optimized or integrated cost, schedule and, effort.”[1]
Not only does Roadmapping help program managers align projects it also help them plan these projects efficiently. Furthermore Roadmapping helps programs managers handle and coordinate between different factors such as politics, economy, infrastructure, society etc.
This article will examine the following
1. Describe the relevance of Roadmapping in program management.
2. A detailed guide to the use of Roadmapping.
3. A critical reflection of the limitations of Roadmapping.
References
Yes, its just a fucking desert, empty and devoid of all substance... Much like the course lectures :)
- ↑ The standard for program Management, second Edition
