Risk

Latest revision as of 14:56, 28 February 2021

By Shakila Khan Malik s173780

[edit] Abstract

Risk is associated with everything, even when we talk about projects, programs and portfolios. It is important to keep risk in mind when working on a project, program and portfolio and identify them, as risk can lead to large costs, losses and project failures. The purpose of the article is to identify potential risks and put them into perspectives using risk management tools.

In order to identify and prevent risks in a project, it is necessary to have risk management. Risk management is a process for identifying risks in a project. Multiple tools can be used to reduce and prevent risks and uncertainties during a process or project. The aim is to ensure successful projects without major risks and unexpected events leading to high costs.

One of the risk management tools is “Failure mode and effects analysis” (FMEA). The FMEA is a process that identifies how and where the project might fail and assesses the different failures to identify which parts are most in need of change ^[1]. In addition, another management tool, the “fishbone diagram” can be used to track the causes of deficiencies or failures in the project. Some other risk management tools are “Post-project review” (PPR) and “Potential problem analysis” (PPA). The PPR analysis identifies potential failures and successes in a project, where the PPA determines what may go wrong in a process or development phase.

[edit] Risk

[edit] What is risk?

The definition of risk is possibility of a negative result/outcome, injury, loss or danger. It is always important to try to protect and prevent a risk from occurring, or at least be aware and prepare for the risk as well as the outcome. This also applies in organizations and companies where risk is associated in project, program and portfolio management. Uncertainty also plays a role here as risk is uncertain. No one knows what risk entails and when and how it unfolds. Uncertainty is lack of certainty, security and knowledge of something or a particular topic. Uncertainty is associated with projects, programs and portfolios as uncertainty and risk are connected, the more risks one can identify the more uncertainty is indicated.

Opportunities are risks that have a positive effect and it is possible to identify successes in projects, programs and portfolios. While threats are risks that have a negative effect in a project, program and portfolio. In this approach, risk management must be involved in order to identify risks, analyze risks, assess the likelihood of risk and impact and implement a solution if the various risks arise.

[edit] Risk Management

Risk, uncertainty and complexity are associated with any project. Some projects have greater and more risks while others have less and fewer. The Risk Management Life Cycle Framework is a tool that can be used by all project managers to help them identify risks and how they carry risks in a project, program or portfolio.^[2]

[edit] The Risk Management Life Cycle Framework contains of following steps:

• Plan Risk Management
• Identify Risks
• Perfom Qualitative Risk Analysis
• Perform Quantitative Risk Analysis
• Plan Risk Responses
• Implement Risk Responses
• Monitor Risks

The purpose of plan risk management is to create a plan that defines how the risk management processes are to be supported. It later helps identify risk. It is not possible to identify all the risks associated with a project or process in the beginning, as no one knows what may happen in the future and everything may change. Therefore, it is necessary to perform a qualitative risk analysis to prioritize the risks. The qualitative analysis is used to gain a better insight and an overview of various risks associated with a project or a process. The analysis focuses on the probability of occurrences. In addition, a quantitative risk analysis is performed to estimate the effect of the risk and find coherence between different risks. A plan risk response is necessary to control the effective respond actions for the overall risks. In the Implement Risk Responses phase, it is therefore possible for the project managers to see if the risks have been identified and treated. The last phase is monitoring risks, project, program and portfolio management teams assess the identified risks and control the risk management processes.

The risk management strategy is connected and linked to portfolios, programs and projects. Strategy identifies risks including threats and opportunities and transforms risk management strategy into actions, portfolios transform strategic goals into organizational value and abilities, programs define benefits and causes and lastly increase projects to higher levels when needed. ^[2]

[edit] Tools

As mentioned earlier, this wiki article contains several risk management tools, that can be used to manage a project. These tools can be adopted by the managers in any organization as the tools are guidance how to tackle and prevent risks and uncertainties in a project, program and portfolio management. It is important to use some risk management tools to identify risk and manage risk. Risk is not easy to identify and nor is it easy to manage risk in a project, program and portfolio. By using the different risk management tools such as failure mode and effects analysis, potential problem analysis and post-project review large and small risks are identified and managed easily.

Failure mode and effects analysis (FMEA) is a nice tool to identify how and where the project might fail and assesses the different failures to identify which parts are most in need of change. The Post-project review (PPR) is a tool that identifies potential failures and successes in a project. The potential problem analysis (PPA) is a tool that determines what may go wrong in a process or development phase.

[edit] Failure Mode and Effects analysis (FMEA)

The FMEA was developed in 1940s when the U.S. military systems became too complex. The FMEA tool identifies where the project might fail, and which parts are most in need of change to prevent risks and uncertainties. The FMEA tool can solve several risks in a manageable way. The failures are prioritized by their consequences and frequency, starting with the highest priorities ^[3].

Figure 1: The seven steps in FMEA (own figure)

The FMEA consists of 7 steps:

• The first step identifies the failures that might fail in the project.
• The second step identifies the root causes of the failures in the project.
• The third step identifies the effects of the failures.
• The fourth step critically identifies and prioritizes the failures, starting with the highest priority.
• The fifth step mitigate the failures and limits the failure modes.
• The sixth step is optimization and develops actions to prevent risks and uncertainties.
• The seventh step is the result, where the results of the FMEA are documented.

The management team must define the scope of the project and identify the failures that may fail in the project or program. Then, all processes are divided into subsequent steps to identify and find the root causes of the failures in the project. Each failure is analyzed separately to identify the major failures and the effects of the failures. Hereafter, the failures are identified and prioritized in order to start with the highest and largest failure. The failures have been mitigated and limited. Thus, it is possible to optimize and develop actions to prevent risks and uncertainties. The actions reduce the likelihood of failures and improve processes, products and services. Finally, the results of the FMEA are documented.

[edit] When and why should the tool be used

The FMEA tool is often used through a product, process and service design phase as it is possible to identify failure in the earlier stages. Moreover, the tool is also used before modifying an existing process in a different way and generally to analyse the failures of a project.

The benefits of using the tool are that the failures are identified at an early stage and prevent risks and uncertainties. Furthermore, the FMEA allows to a greater extent changes in the processes, products and services as it is possible to mitigate the risks. This makes it possible to come up with innovative ideas, changes in a project, program and portfolio along the way and listen to the customers’ wishes or requirements for a product or service. In addition, the use of the tool leads to cheaper solutions, as risks are identified and managed before the outcome. ^[4]

The table below shows how to possibly use the tool. The table contains 7 columns respectively stages, failures, consequences, severity, causes, occurrences and control where each column refers to each step described above.

The first column is stages, all stages in the project have to be defined and written in the column. The second column describes the failures, and the third column writes down the consequences of the failures. The fourth column contains the severity of the failures, where a number between 1-10 is given to describe the severity of the failures. The highest number is indicated for the largest failure that has the largest loss. The fifth column finds and describes potential causes. The sixth column describes the events of the failures as well as how often the failures occur. A number is given between 1-10, where the highest number is given for the failure that occurs frequently. Finally, the seventh column contains and describes the process control.

[edit] Potential problem analysis (PPA)

Another risk management tool is “Potential Problem Analysis”. The PPA implement innovation and focus on what might happened during the developing phase and how to deal with it. The tool determines what could go wrong in a project or process. The causes are assessed as the probability of occurrence and the difficulty of the consequences. ^[5]

The PPA tool consists of 7 steps ^[6]

• The first step is to identify the objectives by producing a flowchart.
• The second step is to list the potential problems by making a brainstorm with the problems.
• The third step is to rate the potential problems in terms of likelihood.
• The fourth step is to determine the risk number of the problems by multiplying the two numbers.
• The fifth step is to search for possible causes of the problems using a fishbone diagram.
• The sixth step is to estimate the probability of occurrence and try to prevent them.
• The seventh step is to develop actions to prevent causes or minimizing their effects.

Figure 3: Example of the PPA (own figure)

Figure 3 shows how the tool can be used. A table is set up with 8 columns respectively project stage, potential problems, likelihood, impact, PP risk number, possible causes, prevention measures and contingency plans. The project stage is described, the potential problems are identified. The likelihood/probability of failure is described by giving a number between 1-10, where 10 is given for the failure with the highest probability. Then it is described how much influence the failures have on the project or program. A PP-risk number is then calculated. Possible causes are identified to prevent and manage the risks and prevention measures are taken. Ultimately, a contingency plan is implemented.

The tool is primary used when working on a large and complex project and as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks. ^[7]

[edit] Post-project review (PPR)

Figure 4: Example of PPR (own figure)

Post-project review is a management tool that gives the opportunity to learn from previous projects. The purpose of the tool PPR is to analyze potential failures and successes of a project or process. It simplifies what went well and what could be better in a project. It minimizes risks and uncertainties as it is possible to learn from previous experiences and failures to improve future projects.

First and foremost, the scope of the project must be defined. Then it must be examined whether a similar project has been carried out. If this has been the case, the knowledge and experiences from the previous project must be used, investigated and implemented in the project. However, if a similar project has not been performed before, then prework must be done. The project can then be implemented. Lastly, it is important to share the experiences and knowledge of the system, what went well and what didn’t and why. Otherwise, future projects may not benefit from the PPR tool and therefore there are no reason to use the tool.

[edit] Pros and Cons

There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as money. In addition, all prework is done so there is no need to make duplications. This makes it possible to spend time researching what, where and why the previous project failed and thus improve it in the new project. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation but just copy the previous project. Another con is that project managers are often not prepared for unseen events in the project as they just follow the previous project. ^[8]

[edit] When to use the tool

The PPR tool is useful for large projects especially within IT as IT companies usually need formalized innovation strategy. The tool can be used in international IT companies that have implemented an IT solution or system in one country that must also be implemented in another country. The tool avoids uncertainties and duplications as using the tool lead to decreasing in prework. Furthermore, it makes sure that failures from previous projects don’t appear again in future projects.

[edit] References

1. ↑ http://www.innovation-portal.info/toolkits/fmea-failure-mode-effect-analysis/
2. ↑ ^{2.0 2.1} https://findit.dtu.dk/en/catalog/2472428928
3. ↑ ASQ. (2020). Learn about quality. Retrieved from Failure mode and effect analysis (FMEA): https://asq.org/quality-resources/fmea
4. ↑ Quality-One International - Discover the value. (2020). Quality-One International - Discover the value. Retrieved from Introduction to Failure Mode and Effects Analysis (FMEA): https://quality-one.com/fmea/
5. ↑ http://www.innovation-portal.info/wp-content/uploads/Potential-problem-analysis.pdf
6. ↑ https://hatrabbits.com/en/potential-problem-analysis/
7. ↑ https://www.kepner-tregoe.com/lp/problem-solving-and-decision-making-workshop/
8. ↑ http://www.innovation-portal.info/toolkits/post-project-reviews/