First of all we identify our project risks, which are let us know what to expect in the future and how to act during the problem.
1) Risks identification - We highlighted couple categories of risks, which are most important to be ready against them.
Procedural and technical failures – from failures of internal systems and control errors, organization, fraud, technical failures. Such as non- responding servers, any mistakes in the internal systems, broken servers, late updates, missing information, etc.
Human – from individuals or organizations, illness, death. For example if the main IT person do not work cause the illness, we have to be ready to have any other backup to take action if needed.
Operational – loss of control of organizational operations.
Reputational – damage to reputation in the market. Such as customers dissatisfaction of the slow app working.
2) Qualitative risk analysis – prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact. Our project idea related with the internet, servers and so on, so our main priority looking into probability of risks are to ensure a well-functioning app without any errors and failures. As a result we have priority of our risks.
1) Procedural and technical failures
2) Human
3) Operational
4) Reputational
3) Quantitative risk analysis – numerically analyzing the effect of identified risks on overall project objectives.
1) Procedural and technical failures – could bring dissatisfaction of customers. 2) Human – slower working of the app, errors and failures of the app cause the misunderstanding information of the servers. 3) Operational - loss of control of the organization. 4) Reputational- dissatisfaction of the customers, stakeholders, suppliers, employees.
4) Risk response planning – developing options and actions to enhance opportunities and to reduce threats to