Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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


CPSIdentified

Lack of resources to deliver London high bugs/issues & global requirements

REQ-1207 

REQ-439

REQ-441

serverId

Risk IDProject Team or person identifying the riskIdentification DateRisk (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

StatusNotes
1CPS

 

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)Better up front analysis of requirements and breakdown of jiras Move some tasks to future work items to ensure timely finish of work itemHighMediumIdentified









2DCAE 

 

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

DCAEContinue current version for London and assess /plan component (MOD) retirement for London releaseExtend the Waiver/Exception filed for London releaseHighLow

07/11/22 - To be discussed with SEECOM on waiver extension











3AAI

  

Jira Legacy
serverSystem Jira
4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-3494
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-3292

AAIMake best efforts to resolve the global requirements and high issuesRaise an exception for this release and make best efforts to resolveHighLow









4AAI

  

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-traversalRaise an exception for this release and hope janusgraph supports java 11 in the coming releaseHighLow









5POLICY

  

Very limited resources are available to deliver the Policy for the 5G SON use case, see Jira LegacyserverSystem JiracolumnIds









issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyPOLICY-4108POLICYIf 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.LowMediumIdentifiedDiscussed with the 5G SON team6OOM & Integration

 

no PTL on both projects for this releaseOOM & IntegrationAsk community for Someone to take over the PTL rolesTBDHighHighIdentified









7DCAE 

 

Due to recent changes in resource availability from Huawei India team, DCAE London commitments have to be reprioritized and adjusted.DCAEMake best efforts to resolve the key requirements and high priority issuesDefer impacted features/Jira to next releaseHighMediumIdentified









8DCAE 

 

New ML MS introduction under  REQ-1215 E2E Network Slicing use case enhancements  is under risk due to pending build issues and code refactoring resolutionDCAEMake best efforts to resolve the open issues; logged LF ticket IT-24493 for troubleshotting jenkins issueProceed to merge once latest updates are verified successfully (both tox and docker execution); jenkins job error resolution can be worked in-parallel through LF ticketHighMediumIdentified