London Risks
- David McBride
- Lee Anjella Macabuhay
- Tony Hansen
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 | DCAE | 2023-01-24 | No PTL | DCAE | share responsibilities amongst committers | none | high | high | assessed | no commitment yet beyond M2 |
2 | DCAE | 2023-01-24 | No resources to meet compliance to global requirement REQ-1072 - Standardized logging fields | DCAE | none | get waiver for London | high | medium | assessed | |
3 | CPS | 2023-01-27 | Requirements are getting larger with very few resources | CPS | high | high | identified | |||
4 | ||||||||||
5 | ||||||||||
6 | ||||||||||
7 | ||||||||||
8 |