Ability to convert Risk to an Issue
Presently, there are 2 tabs/pages for a project to log both Risks & Issues. However, there is no feature to convert an existing Risk to Issue which happen most of the times.
When this is available as a feature it becomes easier to see the trail from Risk to Issue and the mitigation's which taken/not taken which caused this risk to convert to an issue.
When this conversion happens the risk should be closed referring to the Issue ID so it also becomes intuitive for the users and will definitely help the project managers and the project teams to manage risks and issues more effectively.
Stefan Norton commented
The PMI technical definition of risk is an event that has between a 0% - 100% chance of happening. An Issue has a 100% chance of happening. When the item has a 0% chance of happening it is "closed." Risks and Issues are neither positive or negative they simply are. For example, one could exploit a positive risk for the increased benefit of everyone. Seeing as MS Proj is at its heart an Earned Value Management (EVM) tool a systematic way of taking an item and flagging it as "risk," "issue," "positive," "negative," and risk response ... etc would dovetail nicely. The ability to have "one to one," "Many to one," "one to many" and "many to many" between Risks, Issues, Responses to WBS items native to the MS Proj MPP file and associated PWA would be HUGE. (I cannot imagine the engineering/programming effort that it would take Microsoft to accomplish this but these are the same people that made MS Proj work in the first place So I know they can do it)
Dave Jones commented
What about simply copying a risk to an issue. The risk information should be maintained.
Many of our clients are asking for this. It aligns with the processes like PMI. This would be a great enhancement.
It also help the tool align (enforce) the standard methodologies.
Ian Bruckner commented
I like it, along with the comments. This helps answer larger organization questions:
1) How are we doing at preventing risks from becoming issues?
2) What things should we be paying more attention to as potential risks (issues that popped up without having been considered a risk)?
It would be a good feature to have it natively. But meanwhile, a SharePoint designer workflow can cover this requirement.
Question for Stephen: do you see risks and issues as being in the same list? I typically have them in separate lists (Risk Register list and Issue Tracker list).
Stephen Sanderlin commented
I think that this is a good idea, but I would like to see an option for the original risk stay open since it's possible for a risk to manifest more than once during the course of a project.
Agree with Joe's comment that it would be nice to have a new status for converted risks (I would even prefer the terminology "promoted" instead of "converted"), but think it would be better if it simply added the new issue as a related item instead of referencing it as a string somewhere.
Would be great if after you click the "Convert Risk to Issue" button, the status of the risk automatically changes to "Converted to Issue" and provided an Issue ID link to follow the trail.
Kevin Watson commented
Happy to see I am not the only one requesting, I just also posted this b4 I saw yours