Versions Compared

Key

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

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
1OOF

 

Meeting the following requirement for CMSO - Upgrade vulnerable packagesOOF - CMSOWill be taken up along with the feature implementation if it is required by the use casesProject team will try to take up activity if no new feature is plannedLowLowIdentified
2UUI

 

usecase UI dockers contain GPLv3

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-494

UUIWill take active action to contact Jira owner and find out witch package contains GPLv3Make the current dependencies work well and keep this problem to next releaseHighLowIdentified
3Policy

 

Some package upgrades (e.g., CDS) may require significant rework

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-439

PolicyWill continue to work on upgradesObtain a waiver for the problem packagesMediumMediumIdentified
4SDC

 

Some package upgrades may require significant rework

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-439

SDCWill continue to work on upgradesObtain a waiver for the problem packagesMediumMediumIdentified


































































































































...