This centralized page, for all El-Alto 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 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Aug 1, 2019 | After enabling Javascript (JS) coverage, the portal's coverage dropped from 67.3% to 24.6%. This is a huge drop, as the project contain good amount of Javascript code. The risk here is not achieve 55% coverage with JS in El Alto. | PORTAL | The team is planning to upgrade to latest Angular 6 which is in Typescript (rather than in Javascript), along with this new upgrade, the team will explore the test coverage process for typescript code. So, the recommendation is not to invest efforts in adding code coverage for old JS code, rather invest in typescript code. | For El Alto, it is recommended to disable JS code coverage and start enabling coverage for typescript code. However, achieving 55% code coverage in new Typescript code is aggressive for El Alto release. | High | Medium | InProgress on mitigation plan | |