Program Risk vs Project Risk: in your opinion, what are the differences? (hint: this is a trick question with no wrong or right answers).
The question is tricky because it makes some assumptions: your PMO or Program Office has reached a level of maturity such that examination of higher level risk is considered and Project Risk is standardized and effective.
I'm interested in those who have experience (even in the slightest) of considering higher level Program Risk, corresponding processes, and the ultimate ... formalization.
I want to hear your experiences and whether or not the question itself even makes any sense in your organization.
I'm interested in those who have experience (even in the slightest) of considering higher level Program Risk, corresponding processes, and the ultimate ... formalization.
I want to hear your experiences and whether or not the question itself even makes any sense in your organization.
LinkedIn Groups |
2. Knightian uncertainty is defined as the possible opportunity or threat that can be foreseen, but cannot be quantified. (Example: Should the EU bail out the Greeks or not? We can predict what may happen either way, but cannot quantify the effects, so we're indecisive.) 3. Clausewitzian friction is defined as the accumulated unpredictable events that actually occur when executing plans. It can be predicted nor quantified. When any of these types of uncertainties threaten a single business case AND can be mitigated by a decision of the project's sponsor/board it's a project uncertainty. If the threat is to multiple business cases OR the mitigation requires more decision power, the uncertainty should be dealt with at program or portfolio level. Posted by Dennis van der Spoel |
I'm not talking about the specific global risks that you mention (however your question does answer mine in a way), nor do I have anything specific in mind. I want to toss it out and see experiences and interpretations.
However, the lack of response tells me most if not all of us haven't considered Program risk as its own entity ... for any number of reasons.
Personally I was asked to develop separate Program level Risk definitions and processes in an immature healthcare PMO. The PMO was disbanded before any processes could be put into place.
I'm trying to think of a scenario where there could be a Program risk that wouldn't impact (roll down to) at least one project. I was thinking of politics at level removed from a Project that would impact a Program, but it any of these risks, impacted a Program then they would also be Project risks.
I don't know that there are Program only risks.