You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This centralized page, for all Guilin 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 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
1ESRJuly 1st 2020The REQ-341 has dependency on ESR for updating the K8s cluster information.REQ-341To have the friends from Aarna network to help us in this functionality.In case ESR does not make it to Guilin, we will use the postman for updating the AAi with the detaisHighMedIn progress.
2SDCJuly 6th 2020The REQ-349 - Coverage of 55%SDCMinimize impact of changes to limit breakage of coverage metricswill request an exception for GuilinLowLow

Current metrics are at 54.8%, some sonar metrics do not show up on main page but are visible in details.

In Progress for improvments

3SDCJuly 6th 2020REQ 351 - Migration to Java 11SDCTry to get commitments from more companies to help on finishing the migrationwill request an exception for GuilinMediumLowMigration to Java 11 is well under way on main SDC project, still the complexity of project implies that there are several unknowns in completing this change
  • No labels