Project Plans are notoriously difficult to derive. It is difficult to predict all of the activities needed and the timeline of those activities. Consequentially, some activity is missed. Maybe not missed, but the inspiration for the idea of the crutial activity is not forthcoming at the time of the project plan. (Basically we didn't think of it then, because the muse wasn't around) This type of risk is commonly referred to as "white space risk." White space risk is that some required activities won't be identified in advance, leaving gaps in the project plan. The other common risk is "integration risk." Integration risk is that all of the pieces won't come back together to get the desired end result. As a part of a project there are many simultaneous activities, and sometimes the group is too large and needs to break apart to achieve the desired result. The risk arises that after breaking apart it may be difficult to bring the project back to a central focus and fit the disparate parts together.
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
1 Comments to “Risk and Project Plans”
Extreme Programming (a.k.a. XP) reduces such risks because it is a deliberate and disciplined approach to software development. (for an introduction to XP see http://www.extremeprogramming.org).
Please share your thoughts and suggestions
-
Receive Our eNewsletter
The latest Project Management and Healthcare IT practices
-
About Me
Welcome to the Healthcare IT Project Management Blog of Elyse Nielsen. This is the place where I share the ideas I have learned, the things I’d like to remember, and my thoughts for a brighter future. Find out more.
Subscribe to Our Tips
This weblog is licensed under a Creative Commons License.