Versions Compared

Key

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

...

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

Status
#1AAF11/6/2019AAF continues to have Resource issues for regular AAF work.No specific Team or component is impacted.If required, we will request a waiver for JUnit requirements.
MediumMediumUnknown
#211/6/2019

Description: Projects dependent on oparent are blocked from migrating to Java 11 until oparent v3 is released.

Risk: oparent v3 release may happen too late in the Frankfurt release cycle to enable projects to migrate to Java 11 on schedule.

All projects dependent on oparent.Release oparent v3 ASAP to give projects enough time to complete Java 11 migration within the Frankfurt schedule.Complete migration in the Guilin release (1H20)MediumLowV3 in process and expected to be released by the end of Nov '19.
#312/19/2020

DCAE - MOD delivery (Self Serve Control Loop)

Recent resource change impacts delivery of MOD scope planned under REQ-9                                                  

CLAMPPrioritizing MOD functional delivery for Frankfurt. CLAMP integration and other non-functional requirement (sonar coverage, https) will be deferred to GuilinComplete MOD delivery for Guilin release and continue SDC-DS for FrankfurtHighLow

1/9 - Assessed. CLAMP support through manual workaround for Frankfurt

12/19 - Will be reviewed early Jan and feasibility assessed

#4AAI1/9/2020

Description: AAI UI update to portal 2.6

Risk: Resource contention on AAI means that we might not make the backend software change by M2/M3

AAIAsked for resources, Amdocs has committed to provide a resource to look at it over next several weeks but M2/M3 is unlikelyPortal team might have suggestionHighLow, UI is not heavily used
#5AAI1/9/2020

Description: Securing Elasticsearch with FOSS

Risk: The AAI team does not have a path forward to enable encryption with a component with an acceptable license.  Reached out to Stephen Winslow for guidance and his response was that the approaches we had considered are unacceptable.  

AAISolicit suggestions for alternatives that can be used without license issuesContinue with unencrypted use of ElasticsearchHighLow
#6SDC1/13/2020The "OVP Testing and Certification Support Within SDC" feature might not be delivered in R6SDCAsking community for resourcesThe feature won't be deliveredHighMediumPlanned
#7SDC1/13/2020Secured connection to Cassandra might not be fully delivered in R6SDcAsking community for resourcesSecured connection will be developed in certain areas, while other areas will be left unsecured. Work will be completed in R7HighMediumPlanned