What is the difference between a risk and an issue?
Anonymous
I am working with some folks who are PMs but not in the IT field. I'm a PM in the IS department and couldn't actually come up with a good clear distinction between an issue and a risk for the folks that I'm working with. Can someone help me define these two? Thanks. Saving Changes...
Debarshi DuttaProject Manager| Tech Mahindra India Pvt. Ltd.Kolkata, West Bengal, India
A Risk is an event which if happens may potentially have a positive or negative effect on the project.
Risk identification is a continuous process and starts as early as in the planning stage.
Risk has an impact (I) and a probability of occurence(P) and the value of the multiple of IXP gives a quantitative measure of the risk, against which resources may be reserved.
An issue is an event that has occurred, usually has a negative impact on the project and needs to be resolved.
An issue can happen anytime, but if due diligence is given to risk management, there would be fewer negative risks turning into issues. Saving Changes...
Mel BostHead Project Closeout and Lessons Learned Advisory Services Practice| BOT InternationalCave Creek, Az, United States
An issue may or may not present a deviation in expected versus actual results for a project activity. A risk is an event which, if it is triggered, almost always creates a deviation in performance which is adverse to the intended direction of the project and which must be planned for through "triggers" and "mitigation plans." Saving Changes...
Hopefully the originator has received an appropriate response by now, however, I do want to weigh in.
An issue arises as a result of a consequence. A risk is a chance of loss.
Example Scenario:
In installing a patch to a production system, a consequence is that the patch will not work properly. If the patch does not work properly, the risk is that the system will shut down. You resolve the issue of the non-working patch, and mitigate the event of the risk of a system shutdown. This scenario suggests that a consequence can lead to a loss. Saving Changes...
Mel BostHead Project Closeout and Lessons Learned Advisory Services Practice| BOT InternationalCave Creek, Az, United States
Let me join this conversation also. In my Project Closeout and Lessons Learned Framework, I define a Significant Event in a project whcih may become a candidate for a Lesson Learned. There is a relationship between "Risk" and "Lessons Learned" in that, if a "potential Signficant Event" is identified as a "Risk," then it may become a candidate for a Lesson Learned if the "risk" is triggered in the project. "Significant Events" in projects create deviations between expected and actual results and "risks," if triggered, to the same thing. Not all "Issues" create these deviations and that is a major difference between a "risk" and an "issue." Saving Changes...
Wai Mun KooPMO Director| Intergraph PP&MSingapore, Singapore
If issue is what has happened and risk is what potentially may happen but has not happened yet, then is it suffice to say that 'a risk turns into an issue when the event happens?'
Interestingly that we have a whole volume of material in PMBOK that talks about risk management, but not so much on managing issue. Saving Changes...
A risk is something that could possible impact your project in the future. An issue is something that is impacting your project now. Risk and issue management require planning. A risk generally has a mitigation strategy and contingency plan.
For more information on risk and issue management, see the Primer on Risk and Issue Management here:
Wayne KremlingSr Project Manager - Retired| Boeing - RetiredSt. George, UT, United States
Hassib is 100% correct. A risk is something that has a probability of occuring and you need to decide what you will do about it (avoid, transfer, mitigate, or accept), an issue has occurred and has a negative impact that must be dealt with (recovery).
In the PMBOK(r) 4th edition, page 275 it states "A project risk that has occurred can also be considered an issue" Saving Changes...
Ted GhineaSVP COO| T3 Technologies, LLCReston, Va, United States
Risks are anticipated issues, events, or dependencies that
may disrupt execution of a project within planned scope, schedule and cost. It has a probability attached to it.
An issue is a matter in question or dispute that is
disruptive to the smooth execution of a project as planned. There is no probability attached it it, it is a certitude. Saving Changes...
