...
- Identified: a risk that has been identified, but has not yet been analyzed / assessed yet
- Assessed: an identified risk which currently has no risk response plan
- Planned: an identified risk with a risk response plan
- In-Process: a risk where the risk response is being executed
- Closed: a risk that occurred and is transferred to an issue or the risk was solved/avoided
- Not occurred: a risk that was identified but that did not occur
- Rejected: created and kept for tracking purposes but considered not to be used yet
Risk ID | Project Team or person identifying the risk | Identification Date | Risk (Description and potential impact) | Team or component impacted by the risk | Mitigation Plan (Action to prevent the risk to materialize) | Contingency Plan - Response Plan (Action in case of the risk materialized) | Probability of occurrence (probability of the risk materialized) High/Medium/Low | Impact High/Medium/Low | Status |
---|---|---|---|---|---|---|---|---|---|
1 | SDNC | 1/14/19 | NETCONF/TLS support is new in OpenDaylight Fluorine release. Thus, ONAP will be one of the early adopters and hence there is some element of risk. | SDNC/APPC | We will try to target NETCONF/TLS for an early sprint to allow ample recovery time if we need to fall back to NETCONF/SSH | ||||
2 | 15/01/19 | PNF use case being dependent on the delivery of the 5G use case, if it doesn't get deliver, then we won't be able to showcase the PNF use case in Dublin. | CCSDK CDS SO | Low | Assessed |