|
|
|
# Risk Management Plan
|
|
|
|
|
|
|
|
| RISK ID | Description | Severity | Probability | Risk | Preventive measures If escalated |
|
|
|
|
|: -: |: -: |: -: |: -: |: -: |: -: |: -: |
|
|
|
|
| RIS01 | The member of the group becomes ill with the flu 3 | 5 | 15 | Wash your hands | Reported to Whatsap |
|
|
|
|
| RIS02 | The project manager is inoperative | 3 | 1 | 3 | Tasks are distributed to the group in advance. | Choose a new Project Manager as appropriate. |
|
|
|
|
| RIS03 | Insufficient human resources 4 | 2 | 8 | Consider the extent to which a group is appropriate Deleting or reducing features
|
|
|
|
| RIS04 | Delay in required decisions 3 | 2 | 6 | Trying to preliminarily consider decisions in advance. | Let's go to pizza and make a decision with a vote
|
|
|
|
| RIS05 | Labor estimates are significantly exceeded 4 | 4 | 16 | Assess more times than upper and lower Reduce the scale if needed, will be further evaluated on the top cover in the future. |
|
|
|
|
| RIS06 | Participation of stakeholders is inadequate 4 | 2 | 8 | Attract stakeholders actively Answers very aggressively required. |
|
|
|
|
| RIS07 | The team's expertise is inadequate 4 | 5 | 20 | Active contact with the support team Studying until the expertise is sufficient and, if necessary, reduced the scope
|
|
|
|
| RIS08 | The specifications do not meet end user needs 5 | 3 | 15 | The needs of end users are assessed at different stages of the project. | Reconfigured more when listening to users. |
|
|
|
|
| RIS09 | The configuration does not take into account the existing operating environment 4 | 3 | 12 | Discuss topics with stakeholders at various stages of the project The situation is evaluated and conflicting determinations are removed
|
|
|
|
| RIS10 | The configuration process is not phased efficiently 2 | 2 | 4 | Issue tracker is used actively | The tracker is cleaned so that it gets a good grip again. |
|
|
|
|
| RIS11 | All members of the group are ill 5 | 1 | 5 | Wash your hands | Operate in accordance with the [* Exceptions *] (https://gitlab.labranet.jamk.fi/PRJTEAM-H/halinallet/wikis/Viestintasuojelu#poustotapahtumat) communication plan |
|
|
|
|
| RIS12 | No one is interested anymore and people stop working 5 | 1 | 5 | Candy and liquor Operate in accordance with the [* Exceptions *] (https://gitlab.labranet.jamk.fi/PRJTEAM-H/halinallet/wikis/Viestintasuojelu#poustotapahtumat) communication plan |
|
|
|
|
| RIS13 | System error or human error destroys project folders 5 | 1 | 5 | Keeping backups of the most important files | Let's get in touch with labels and pray |
|
|
|
|
|
|
|
|
### Description of the stability classes
|
|
|
|
|
|
|
|
| Severity class Description | Change |
|
|
|
|
| ----: |: ----: |: ----: |
|
|
|
|
| 1 | Limited impact as a single case |
|
|
|
|
| 2 | A clear impact on the result of the project, but the result is, however, all the right |
|
|
|
|
| 3 | Significant effect on the result, but the project can still be completed | |
|
|
|
|
| 4 | High impact on project success |
|
|
|
|
| 5 | Very great impact, project-destructive. | |
|
|
|
|
|
|
|
|
### Descriptions of probability classes
|
|
|
|
|
|
|
|
| Probability class Description | Change |
|
|
|
|
| ----: |: ----: |: ----: |
|
|
|
|
| 1 | Very unlikely | |
|
|
|
|
| 2 | Unlikely | |
|
|
|
|
| 3 | Possible | |
|
|
|
|
| 4 | Probable | |
|
|
|
|
| 5 | Almost sure | | |
|
|
|
\ No newline at end of file |
