This centralized page, for all Kohn 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 | CPS |
| Scope creep in work item #1 (state handling) (CPS R11 Release Planning#CPS-CORE/CPS-NCMPRequirements) corresponds to a delay in other work items such as #4 (reading data (single CM handle, synchronous only) | CPS | Better up front analysis of requirements and breakdown of jiras | Move some tasks to future work items to ensure timely finish of work item | High | Medium | Identified | |