In recent discussion I realize many people have difficulties distinguishing risk from Issues.
Risk definition in PMBOK5th is "An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project
objectives."
and Issue is define as " A point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements."
How do you get people to understand the differences? or you just don't differentiate both and put both in the risk register? Or you see issue as a risk that is materialized? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
An issue could be anything from a dispute, misunderstanding or a problem that might cause a Risk so I personally consider issues generally as a cause of Risks.
As you shared the PMBOK definition of Issue , and it is any open thing or dispute which is not settled. Examples
Developer come and say he has some issues with coming 9AM to office , for next one month he wants to come at 11 AM, you as Project Manager finding it difficult to give this flexibility, so you raise the Issue in Issue Log and work for finding some solution to it.
How is it different from Risk ? it has no uncertainty, mean the thing is clear what developer want , it may have impact of project that is why it is not resolved. The way we resolve the issue may trigger new risk.
So an issue could be a trigger or predecessor to a risk?
Saving Changes...
Dominic LawProduct Manager| PCCW GlobalHappy Valley, Hong Kong
My understanding is: Issue has already happened, while Risk has not happened yet.
...
1 reply by Vincent Guerard
Jan 26, 2017 11:44 AM
Vincent Guerard
...
Hi Dominic Thanks for your input
So an issue is already happened, it is not a risk by itself. Can the uncertainty of the way the issue could be resolve be a risk?
Saving Changes...
Carlos TessoreDr.| RManagementMontevideo, Montevideo, Uruguay
When we are talking about a risks it is something that may happen or not. Issues are a reality perhaps a threat that has already materialized.
Risk management is different from issue management, the methodologies differs since the first is a possibility and the second is a reality.
An issue could be anything from a dispute, misunderstanding or a problem that might cause a Risk so I personally consider issues generally as a cause of Risks.
Hi Rami, Thanks for you input
So an issue could be a trigger to a risk? Saving Changes...
As you shared the PMBOK definition of Issue , and it is any open thing or dispute which is not settled. Examples
Developer come and say he has some issues with coming 9AM to office , for next one month he wants to come at 11 AM, you as Project Manager finding it difficult to give this flexibility, so you raise the Issue in Issue Log and work for finding some solution to it.
How is it different from Risk ? it has no uncertainty, mean the thing is clear what developer want , it may have impact of project that is why it is not resolved. The way we resolve the issue may trigger new risk.
So an issue could be a trigger or predecessor to a risk?
...
1 reply by Saket Bansal
Jan 28, 2017 1:35 AM
Saket Bansal
...
Yes Issue can be Trigger , or can be an predecessor of risk . We can have issue which just get reported and solved and it never become risk, say someone raised an issue that he should also get weekly status report, you added the person in your communication plan after reflecting on his need. Issue closed . and not necessary has any risk linked to it.
My understanding is: Issue has already happened, while Risk has not happened yet.
Hi Dominic Thanks for your input
So an issue is already happened, it is not a risk by itself. Can the uncertainty of the way the issue could be resolve be a risk?
...
1 reply by Dominic Law
Jan 26, 2017 8:34 PM
Dominic Law
...
At project start there should be a risk register. During the course of the project some risks may materialize, and these have become issues. The risk register should have some mitigation proposals, so most likely these would be the first actions to take for the issues. And there should be continued follow-up of the issues until they are solved and also the impact to the overall project is under control.
When we are talking about a risks it is something that may happen or not. Issues are a reality perhaps a threat that has already materialized.
Risk management is different from issue management, the methodologies differs since the first is a possibility and the second is a reality.
Hi Carlo, thanks for your feedback.
Can the issue management generate a risk? Saving Changes...
Carlos TessoreDr.| RManagementMontevideo, Montevideo, Uruguay
An issue can be the result of the materialization of a risk and the same time it can generate new risks. Saving Changes...
Dominic LawProduct Manager| PCCW GlobalHappy Valley, Hong Kong
Jan 26, 2017 11:44 AM
Replying to Vincent Guerard
...
Hi Dominic Thanks for your input
So an issue is already happened, it is not a risk by itself. Can the uncertainty of the way the issue could be resolve be a risk?
At project start there should be a risk register. During the course of the project some risks may materialize, and these have become issues. The risk register should have some mitigation proposals, so most likely these would be the first actions to take for the issues. And there should be continued follow-up of the issues until they are solved and also the impact to the overall project is under control. Saving Changes...
"I do not know anyone who has got to the top without hard work. That is the recipe. It will not always get you to the top, but should get you pretty near."
Community Champion
