This centralized page, for all London projects, is aimed at identifying the risks as they are foreseen within the release life cycle.
A Risk that materialized becomes an Issue.
Status:
- 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 | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | CPS |
| Scope creep in work item #1 (state handling) (CPS R11 Release Planning#CPS-CORE/CPS-NCMPRequirements) corresponds to a delay in other work items such as #4 (reading data (single CM handle, synchronous only) | CPS | Better up front analysis of requirements and breakdown of jiras | Move some tasks to future work items to ensure timely finish of work item | High | Medium | Identified | |
| 2. | DCAE |
| REQ-1211 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) dcaemod-designtool & dcaemod-nifi-registry has dependency on upstream (NiFI) project which is currently on java8 | DCAE | Continue current version for London and assess /plan component (MOD) retirement for London release | Extend the Waiver/Exception filed for London release | High | Low | Identified | 07/11/22 - To be discussed with SEECOM on waiver extension |
| 3 | AAI |
| AAI | Make best efforts to resolve the global requirements and high issues | Raise an exception for this release and make best efforts to resolve | High | Low | |||
| 4 | AAI |
| Janusgraph does not support Java 11 REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) | AAI | Not much we can do repos affected: aai-common, aai-graphadmin, aai-resources, aai-traversal | Raise an exception for this release and hope janusgraph supports java 11 in the coming release | High | Low | ||
| 5 | POLICY |
| Very limited resources are available to deliver the Policy for the 5G SON use case, see POLICY-4108 - Getting issue details... STATUS | POLICY | If the amount of work is small, we can take the work during routine maintenance activities. | Use the existing policy and try to secure resources in future releases. | Low | Medium | Identified | Discussed with the 5G SON team |
| 6 | OOM & Integration |
| no PTL on both projects for this release | OOM & Integration | Ask community for Someone to take over the PTL roles | TBD | High | High | Identified | |
| 7 | DCAE |
| Due to recent changes in resource availability from Huawei India team, DCAE London commitments have to be reprioritized and adjusted. | DCAE | Make best efforts to resolve the key requirements and high priority issues | Defer impacted features/Jira to next release | High | Medium | Identified | |
| 8 | DCAE |
| New ML MS introduction under REQ-1215 E2E Network Slicing use case enhancements is under risk due to pending build issues and code refactoring resolution | DCAE | Make best efforts to resolve the open issues; logged LF ticket IT-24493 for troubleshotting jenkins issue | Proceed to merge once latest updates are verified successfully (both tox and docker execution); jenkins job error resolution can be worked in-parallel through LF ticket | High | Medium | Identified |