Development Management checklists (4)-Risk Management

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

This article mainly introduces how to identify risks step by step before the project starts.
You can follow the steps below to easily identify risks or improve the project success rate.
Note: This article is just the chekclists for risk identification. The analysis methods mentioned above are just a brief introduction.

I. Identify Risks

 

1. Determine the person responsible for risk identification

The project manager should track risks and prepare corresponding response plans for identified risks

 

2. Time for risk identification

Risk identification should be carried out during project startup

3. Risk Identification Methods

(1) research project description and specification requirements for project deliverables-> check for potential risks in project requirements
(2) Reviewing project documents> identifying risks not identified when preparing documents such as the project charter, Personnel Plan, and project task book
(3) visit a project expert to find out where risks may occur.
(4) brainstorm
(5) comparison by analogy: review lessons learned from similar projects
(6) Use a fish bone chart to identify project risks
(7) Output risk list (chart 1)

Detailed project Detection Risk table address: Development Management checklists (5)-risk detection table

 

4. determine risk types

(1) technical and quality risks
1. The degree of dependency on the use of unproven or complex technologies
2. extremely challenging performance goals
3. The technology used has changed, the industry standards have changed during the project, and the customer's requirements for product specifications have changed.
(2) project progress risks
1. Whether the time corresponding to the project task is accurate
(3) project management risks
1. Is the project manager's experience and management tools suitable?
(4) organizational risks
1. There are too many projects. The current project is only one of them. resource supply risks
2. Human resources cannot be provided in a timely manner

2. Construct a risk impact analysis matrix for risk assessment
Risk Assessment: it is necessary to estimate and evaluate identified risks. The main task of risk estimation is to determine the probability and consequence of risk occurrence, the risk assessment is to determine the economic significance of the risk and the cost/Effect Analysis of the handling.

1. Qualitative risk analysis
(1) qualitative analysis is useful only when the likelihood or extent of the risk is difficult to accurately define.
(2) Qualitative risk analysis will generate risk levels for each risk factor,
For example: small, small, medium, large, large

 

2. Quantitative Risk Analysis
The purpose of quantitative risk analysis is to analyze the probability of each risk and its impact on the project objectives. Generally, after qualitative risk analysis, quantitative risk analysis is performed.
The method used is as follows:

(1) Delphi method: Expert Evaluation Method
(2) Sensitivity Analysis: Which risks have great potential impact on the project?
(3) Decision Analysis: use decision trees for analysis.
(4) simulation: Project simulation through technology

After the above identification and evaluation steps, we should output tables in the following format:

Java code

1. Risk table samples before classification
3. Risk category probability impact
5. Immature Technical Interface medium 2
6. High user concurrency may crash. The background is large. 1
8. Note: impact category value: 1-2 of the disaster-critical 3-minor 4-negligible

Chart 1

For most software projects, the risk factors-cost, performance, support, and progress-are typical risk references. That is to say, there is a horizontal value that leads to project termination for cost overruns, performance degradation, support difficulties, and schedule delays. If the problem caused by a combination of risks exceeds one or more reference level values, the work of the project will be terminated. In the project analysis, risk level reference values are composed 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 the critical point, you can use performance analysis, cost analysis, and quality analysis to determine whether the project continues to work.

 

 

3. Develop risk response plans

1. Risk Avoidance
A threat that changes the project plan to invalidate a specific risk
2. Risk Transfer
Transfer risks to a third party in the form of a contract, insurance terms, etc.: for example, buy insurance, or outsource the project.
3. Risk reduction
Reduces the probability or impact of adverse risk events to the acceptable level.
4. Risk Acceptance
Accept risks when risks are not high

The risk response plan will produce the following results:
(1) risk identification, risk description, fields affected by the project, causes, and forms of affected project objectives
(2) Risk management roles and responsibilities
(3) risk qualitative and quantitative analysis results
(4) risk avoidance, reduction, transfer and acceptance strategies
(5) risks still exist after the policy is used
(6) specific steps of implementation strategy
(7) Budget and progress of the strategy

Iv. Review risk response plans

Reviewed by experts from various aspects

5. Use risk assessment software for evaluation
Software Project Risk tracking tool
One way to track risks is to input the risk into the defect tracking system. The defect tracking system can mark the risk items as resolved or not handled, and can also specify the project team members who solve the problem, and arrange the processing order. Software risk items can be listed in sequence, according to the time of occurrence of defects and the persons responsible for such information. In this way, the defect tracing system is able to better track risks and be less monotonous.

<Development Management checklists> by dylove98 @ Development Management checklists