Project Management (iv)-risk management

This article mainly introduces how to identify risks before the project starts, and then how to identify the risks. A friend who needs to make a risk identification can follow the steps below to simply walk through it, or improve the project's success rate.
Note: This article is only for you to do risk identification chekclists, some of the above mentioned analysis methods are simply introduced

First, identify risks

1. Determine the person responsible for identifying the risk

Project managers should track risks and prepare corresponding response plans for identified risks

2. Time to identify risks

Risk identification should be performed during project initiation
3, the way of risk identification

(1), research project description and Project deliverables specification, identify potential risks in project requirements
(2), review project document, identify risks not identified in the preparation of documents such as project charters, personnel plans, project assignments, etc.
(3), visit project experts, figure out where the risk will appear
(4) Use of brainstorming
(5), analogy comparison method: Review the experience and lessons of similar projects
(6) Identification of the Fishbone diagram identifying the risk of the project
(7), Output risk list (chart i)

Detailed Project Inspection risk table address: project Management (v)-risk Test form

4. Determine the type of risk

(1), technology, quality risk
1. Reliance on technology or complex technology that has not been fully proven
2. Highly challenging performance objectives
3, the use of technology changes, the industry standard changes during the project, customer specifications for the product changes
(2), Project schedule risk
1, the project task corresponding time is accurate
(3) Risk of project management
1, the project manager experience, the use of management tools is appropriate, etc.
(4), organizational risk
1, too many projects, the current project is only one of the resources supply risk
2, human resources, etc. cannot be provided in time

Ii. Structural risk impact Analysis matrix for risk assessment
Risk assessment: To estimate and evaluate identified risks, the main task of risk estimation is to determine the probability and consequences of risk occurrence, and risk assessment is to determine the economic significance of the risk and to deal with the cost/effect analysis
1. Risk analysis
(1), in the likelihood of risk or the degree of influence is difficult to define precisely, the qualitative analysis method is very useful.
(2), risk qualitative analysis will produce risk levels of each risk factor,
For example: Very small, small, medium, large, very large

2. Quantitative Analysis of risk
The purpose of quantitative risk analysis is to analyze the probability of each risk and its impact on the project target, and then carry on the risk analysis after the risk analysis.
The method used is as follows

(1), Delphi method: Expert Evaluation method
(2) Sensitivity analysis: Which risks have a very large potential impact on the project
(3), decision Analysis: The use of decision trees in the form of analysis.
(4), Simulation: Project simulation through technology

After the identification and evaluation steps above we should output a table in the following format

Sample of Risk table before classification:

1. Risk category Probability Impact
2. Technically immature interface medium 2
3. High user concurrency may crash background larger 1
4. Note: Impact category value:1-disaster 2-Severe 3-slight 4-negligible

For most software projects, risk factors-cost, performance, support, and progress-are typical risk reference frames. This means that cost overruns, performance degradation, support difficulties, and progress delays all have a level value that leads to project termination. If the problem arises when a combination of risks exceeds one or more reference level values, the work of the project is terminated, and in the case of the project analysis, the risk level reference value is made up of a series of points, each of which is often referred to as a reference point or a critical point. If a risk falls on a critical point, you can use performance analysis, cost analysis, quality analysis, and so on to determine whether the project continues to work

Iii. developing a risk response plan

       1, risk avoidance
             Change the project plan to invalidate the threat of a specific risk
        2. Risk Transfer
             will have risks in the form of contracts, Transfer of insurance clauses to third parties for risk transfer: such as insurance purchase, or project outsourcing
        3, risk reduction
             reduce the probability or impact of adverse risk events to acceptable levels
         4, risk acceptance
            Accept risk in case of minor risks

The risk response plan will produce the following results
(1), risk identification, risk description, areas affected by the project, causes, form of impact on project objectives
(2) The role and responsibility allocation of risk management
(3), risk qualitative and quantitative analysis results
(4) Risk avoidance, reduction, transfer and acceptance strategies
(5) Risks that persist after using policies
(6), the implementation of the strategy of the specific steps
(7), strategy budget and schedule

Iv. Assessment of risk response plan
Experts in all aspects of the review

V. Use of risk assessment software for evaluation
Software Project Risk Tracking tool
One way to track risk is to import the risk into the defect tracking system, which identifies the risk items as resolved or not yet processed, and can also designate the project team members to solve the problem and arrange the order of processing. Software risk items can be arranged sequentially, according to the time of the defect and the person responsible for the arrangement. In this way, the defect tracking system is the job of tracking risk better and less monotonous.

Project Management (iv)-risk management