The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "PROC04 Risks review"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
| '''Related document'''<br> | | '''Related document'''<br> | ||
| | | | ||
[https://documents.egi.eu/document/2595 https://documents.egi.eu/document/2595] | [https://documents.egi.eu/document/2595 https://documents.egi.eu/document/2595] | ||
[https://wiki.egi.eu/wiki/EGI-Engage:Risk_Plan https://wiki.egi.eu/wiki/EGI-Engage:Risk_Plan]<br> | [https://wiki.egi.eu/wiki/EGI-Engage:Risk_Plan https://wiki.egi.eu/wiki/EGI-Engage:Risk_Plan]<br> | ||
|} | |} | ||
| Line 40: | Line 40: | ||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. | ||
= Timing = | = Timing = | ||
Risk review take place every 3 months starting from October 2015<br> | Risk review take place every 3 months starting from October 2015<br> | ||
= Steps = | = Steps = | ||
| Line 53: | Line 53: | ||
! Action | ! Action | ||
|- valign="top" | |- valign="top" | ||
| 1 | | 1 | ||
| <br> | | <br> | ||
| QM | | QM | ||
| Organize face to face meetings with all WP leader<br> | | Organize face to face meetings with all WP leader<br> | ||
|- valign="top" | |- valign="top" | ||
| 2 | | 2 | ||
| <br> | | <br> | ||
| WP leaders<br> | | WP leaders<br> | ||
| | | | ||
With QM review risks assigned to WP. | With QM review risks assigned to WP. | ||
*identifying deprecated risks<br> | *identifying deprecated risks<br> | ||
*reassessment of impact and probability of existing risks<br> | *reassessment of impact and probability of existing risks<br> | ||
*reviewing of risk response<br> | *reviewing of risk response<br> | ||
*identification of new risks <br> | *identification of new risks <br> | ||
|- valign="top" | |- valign="top" | ||
| 3 | | 3 | ||
| <br> | | <br> | ||
| Technical Coordinator (TC)<br> | | Technical Coordinator (TC)<br> | ||
| | | | ||
Approve/reject/suggest changes in Risk registry<br> | Approve/reject/suggest changes in Risk registry<br> | ||
|- valign="top" | |- valign="top" | ||
| 4<br> | | 4<br> | ||
| <br> | | <br> | ||
| QM<br> | | QM<br> | ||
| Inform WP leader about outcome of TC review<br> | | Inform WP leader about outcome of TC review<br> | ||
|- valign="top" | |- valign="top" | ||
| 5<br> | | 5<br> | ||
| <br> | | <br> | ||
| QM<br> | | QM<br> | ||
| Circulate final version of risk registry to AMB and PMB<br> | | Circulate final version of risk registry to AMB and PMB<br> | ||
|- valign="top" | |- valign="top" | ||
| 6<br> | | 6<br> | ||
| <br> | | <br> | ||
| | | QM<br> | ||
| Circulate final version of risk registry to CB | | Circulate final version of risk registry to CB | ||
|} | |} | ||
<br> | |||
<br> | |||
= Revision History = | = Revision History = | ||
Revision as of 12:02, 1 June 2016
| Title | Risks review |
| Link | https://wiki.egi.eu/wiki/PROC04_Risks_review |
| Owner |
Quality Manager |
| Status | Approved |
| Approval date | 28 Oct 2015 |
| Related document |
Overview
The goal of this procedure is to identify risks and plan proper response to prevent risk occurrence.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Timing
Risk review take place every 3 months starting from October 2015
Steps
| Step | Responsible | Action | |
|---|---|---|---|
| 1 | QM | Organize face to face meetings with all WP leader | |
| 2 | WP leaders |
With QM review risks assigned to WP.
| |
| 3 | Technical Coordinator (TC) |
Approve/reject/suggest changes in Risk registry | |
| 4 |
QM |
Inform WP leader about outcome of TC review | |
| 5 |
QM |
Circulate final version of risk registry to AMB and PMB | |
| 6 |
QM |
Circulate final version of risk registry to CB |
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|