diff --git a/.github/ISSUE_TEMPLATE/risk.md b/.github/ISSUE_TEMPLATE/risk.md new file mode 100644 index 00000000..5e599994 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/risk.md @@ -0,0 +1,59 @@ +--- +name: Risk +about: Document project risks +title: "[RISK]" +labels: risk +assignees: '' + +--- + +## Title +*What is the risk we need to manage?* +
+ +## Description +*Describe the potential risk. For instance: Item A cannot be completed until Item B has been purchased but approval has been delayed, or Item A requires resources that have not been identified and the project is currently resource constrained.* + +
+ + +## Category + +- [ ] Timeline +- [ ] Resource +- [ ] Environment +- [ ] Customer/Partner +- [ ] Regulatory or compliance +- [ ] Financial (cost/revenue) +- [ ] Regulatory or compliance +- [ ] Something else? Please suggest a category. + +
+ +## Potential Impact (1 - 10) +*A quantitative rating of the potential impact on the project if the risk should materialize. Impact in a Risk Register should be scored on a scale of 1 – 10 with 10 being the highest impact.* + +
+ + +## Probability (1 - 10) +*The likelihood that the risk will occur at some point in the duration of the project. This should be quantitative like Potential Impact not qualitative (high, medium or low). If you use qualitative measures you cannot calculate a Risk Score, which is done by multiplying Probability and Impact and you can easily convert a number to a descriptor e.g. 1-3 = “Low”, 4-6 = “Medium” and 7-10 = “High”.* + +
+ + +## Risk Score (Impact x Probability) + +
+ + +## Likely Outcome +*The likely consequence or impact of the risk if it materializes.* + +
+ + +## Prevention and Mitigation +*Action plan to prevent a given risk from occurring, or contingency plans if the risk occurs.* + +