PROJECT MANAGEMENT CYCLE:PROJECT RISK MANAGEMENT

By -
3. PROJECT RISK MANAGEMENT
Processes

Project risk management involves four processes:

1. Risk identification

2. Risk quantification

3. Risk response development

4. Risk response control

These processes are designed to evaluate the possible risk events that might influence the project and integrate proper measures to handle uncertainty in the project-planning monitoring and control activ- ities.

Description

A risk event is a discrete random occurrence that (if occurring) affects the project. Risk events are identified based on the difficulty to achieve the required project outcome (the characteristics of the product or service), constraints on schedules and budgets, and the availability of resources. The environment in which the project is performed is also a potential source of risk. Historical information is an important input in the risk-identification process—knowledge gaps are a common source of risk in projects. Risks are generated by different sources, such as technology—an effort to develop, use, or integrate new technologies in a project creates a knowledge gap and consequently risks. External risks such as new laws or a strike in government agencies may generate project risks. Internal sources within the project or its stakeholders may also do so. The probability of risk events and the magnitude of their affect on the project success are estimated during the risk-quantification process. This process is aimed at an effort to rank risks in order of the probability of occurrence and the level of impact on the project. Thus, a high risk is an event that is highly probable and may cause substantial damage to the project.

Based on the magnitude of risk associated with each risk event, a risk response is developed. Several responses are used in project management, including:

• Risk elimination: In some projects it is possible to eliminate some risks altogether by using a different technology, a different supplier, etc.

• Risk reduction: If risk elimination is too expensive or impossible, risk reduction may be used by reducing the probability of a risk event or its impact or both. A typical example is redundancy in R&D projects when two mutually exclusive technologies are developed in parallel to reduce the risk that a failure in development will harm the project. Although only one of the alternative technologies will be used, the redundancy reduces the probability of a failure.

• Risk sharing: It is possible in some projects to share risks (and benefits) with some stakeholders such as suppliers, subcontractors, partners, or even the client. Another form of risk sharing is with an insurance company.

• Risk absorption: If a decision is made to absorb the risk, buffers in the form of management reserve or extra time in the schedule can be used. In addition, contingency plans may be appropriate tools to help in coping with the consequences of risk events.

Since information is collected throughout the life cycle of a project, additional information is used to continuously update the risk-management plan. Risk-response control is a continuous effort to identify new sources of risk, update the estimates regarding probabilities and impacts of risk events, and activate the risk-management plan when needed. Constantly monitoring the project progress in an effort to update the risk-management plan and activate it when necessary can reduce the impact of uncertainty and increase the probability of successful project completion.

Comments

Post a Comment

Popular posts from this blog

DUALITY THEORY:THE ESSENCE OF DUALITY THEORY

By -
Image
THE ESSENCE OF DUALITY THEORY Given our standard form for the primal problem at the left (perhaps after conversion from another form), its dual problem has the form shown to the right. Thus, with the primal problem in maximizatio n form, the dual problem is in minimization form instead. Furthermore, the dual problem uses exactly the same pa r amete r s as the primal problem, but in different locations, as summarized below. 1. The coefficients in the objective function of the primal problem are the right-hand sides of the functional constraints in the dual problem. 2. The right-hand sides of the functional constraints in the primal problem are the coef- ficients in the objective function of the dual problem. 3. The coefficients of a variable in the functional constraints of the primal problem are the coefficients in a functional constraint of the dual problem. To highlight the comparison, now look at these same two problems in matrix notation (as introduced at the beginn...
Read more

NETWORK OPTIMIZATION MODELS:THE MINIMUM SPANNING TREE PROBLEM

By -
Image
THE MINIMUM SPANNING TREE PROBLEM The minimum spanning tree problem bears some similarities to the main version of the shortest-path problem presented in the preceding section. In both cases, an undi r ecte d and connected network is being considered, where the given information includes some mea- sure of the positive length (distance, cost, time, etc.) associated with each link. Both problems also involve choosing a set of links that have the shortest total length among all sets of links that satisfy a certain property. For the shortest-path problem, this property is that the chosen links must provide a path between the origin and the destination. For the minimum spanning tree problem, the required property is that the chosen links must provide a path between ea c h pair of nodes. The minimum spanning tree problem can be summarized as follows: 1. You are given the nodes of a network but not the links. Instead, you are given the po- tential links and the positive length for each ...
Read more

INTEGER PROGRAMMING:THE BRANCH-AND-CUT APPROACH TO SOLVING BIP PROBLEMS

By -
TH E BRANCH-AND-CUT APPROACH TO SOLVING BIP PROBLEMS Integer programming has been an especially exciting area of OR since the mid-1980s be- cause of the dramatic progress being made in its solution methodology. Background To place this progress into perspective, consider the historical background. One big break- through had come in the 1960s and early 1970s with the development and refinement of the branch-and-bound approach. But then the state of the art seemed to hit a plateau. Rel- atively small problems (well under 100 variables) could be solved very efficiently, but even a modest increase in problem size might cause an explosion in computation time be- yond feasible limits. Little progress was being made in overcoming this exponential growth in computation time as the problem size was increased. Many important problems arising in practice could not be solved. Then came the next breakthrough in the mid-1980s, with the introduction of the b r an c h- and-cu t approach to sol...
Read more