SharePoint List Data Elements Descriptions Risks ID ID number of the risk (automatically assigned in numerical order by SharePoint) – Date Raised date the risk was identified – Risk (Title) short name to identify the risk – Description description of the risk – Probability likelihood that the risk will occur (descriptive words used: Very Unlikely, Low, Maybe, – Probably, Very Likely, and Very High) Impact effect to the project if the risk event occurs (descriptive words used: Very Low, Low, – Moderate, High, or Very High) Score (Matrix) those risks trending towards high impact and high probability will require more – extensive review regularly by the project team; to allow for easier oversight and prioritization of risks, the following scoring table will be used Owner person(s) responsible for monitoring the risk – Assigned To person(s) responsible for the risk if it should occur – Agreed Response strategy that is most likely to be effective – Avoid entails changing the project plan to eliminate the risk or condition or to protect the – project objectives from its impact Transfer seeks to shift the consequence of a risk to a third party together with – ownership of the response (transferring the risk simply gives another party responsibility for its management, it does not eliminate it) Mitigate seeks to reduce the probability and/or consequences of an adverse risk event – to an acceptable threshold (taking early action to reduce the probability of a risk occurring or its impact on the project is more effective than trying to repair the consequences after it occurs) Accept indicates that the project team has decided not to change the project plan to – deal with a risk or is unable to identify any suitable response strategy Response Plan actions the project team or the assignee will follow should the risk – Date Triggered date the risk occurred –
SharePoint List Data Elements Descriptions Risks ID – ID number of the risk (automatically assigned in numerical order by SharePoint) Date Raised – date the risk was identified Risk (Title) – short name to identify the risk Description – description of the risk Probability – likelihood that the risk will occur (descriptive words used: Very Unlikely, Low, Maybe, Probably, Very Likely, and Very High) Impact – effect to the project if the risk event occurs (descriptive words used: Very Low, Low, Moderate, High, or Very High) Score (Matrix) – those risks trending towards high impact and high probability will require more extensive review regularly by the project team; to allow for easier oversight and prioritization of risks, the following scoring table will be used Owner – person(s) responsible for monitoring the risk Assigned To – person(s) responsible for the risk if it should occur Agreed Response – strategy that is most likely to be effective Avoid – entails changing the project plan to eliminate the risk or condition or to protect the project objectives from its impact Transfer – seeks to shift the consequence of a risk to a third party together with ownership of the response (transferring the risk simply gives another party responsibility for its management, it does not eliminate it) Mitigate – seeks to reduce the probability and/or consequences of an adverse risk event to an acceptable threshold (taking early action to reduce the probability of a risk occurring or its impact on the project is more effective than trying to repair the consequences after it occurs) Accept – indicates that the project team has decided not to change the project plan to deal with a risk or is unable to identify any suitable response strategy Response Plan – actions the project team or the assignee will follow should the risk Date Triggered – date the risk occurred
SharePoint_List_Data_Elements_Descriptions.docx