[Project Management] project management-Risk Management

I. Main process of risk management

Risks in software projects refer to the damages or losses that may occur during software development and the software products themselves. The purpose of risk management is to identify potential problems before they arise, so that risk management activities can be planned and called as needed throughout the product or project lifecycle to mitigate the adverse impact on achieving the goal.

To achieve this goal, risk identification, risk analysis, risk plan, and risk control need to be performed cyclically throughout the project's lifecycle) and risk tracking (track) until all risks of the project are identified and resolved.

 

Ii. Risk Management Plan

After the project owner is determined, a project risk management plan should be formulated to clarify the risk owner, risk evaluation criteria and risk management strategies of the project. The risk management plan will be submitted to the manager as part of the project plan. The risk owner can be the project owner or a project member designated by the project owner. Its primary responsibility is to track risks and implement them.

 

Iii. Risk Identification

Risk management activities first identify and assess potential risk fields, which is the most important step in risk management. Risk identification cannot be completed at one time, and should be carried out on a regular basis from the beginning to the end of the project.

1. risk source

Risk sources can be found in the project process or in the project content. Risks may occur at all stages of the project's lifecycle. According to the characteristics of the software project, the risk sources can be divided into the following three categories:

1. Sources of technical risks: including sources of technical risks such as demand changes and technical development capabilities

2. Management Risk Sources: including decision-making, budget, and other management-related risk sources

3. commercial risk sources: including customer satisfaction, customer feedback, and other commercial risk sources

2. Timing and methods of risk identification

Risk identification does not have a single method and tool. It is a smart knowledge management process. It is best to be attended by project members. The main time for risk identification is:

At the initial stage of the project and when major turning points or important project changes occur, these changes usually refer to costs, progress, scope or personnel.

Identify risks systematically: Use the following three simple methods to identify risks: Risk checklist, regular (such as weekly meetings, before milestones), and daily input (such as daily morning meetings ).

3. Risk records

The risks identified by the project should be recorded in the risk management table, and the risk category should be specified for the project, and the basic information of the project should be recorded, includes risk classification, risk description, and specifying a unique risk ID for each risk in a project, and recording the risk discovery date.

 

Iv. Risk Analysis

There are many potential risks identified through the risk identification process, but these potential risks have different effects on the project. Risk analysis determines the importance of various risks through analysis, comparison, evaluation, and other methods, so that the project implementers focus on important risks, effectively control the overall risks of the project.

1. Risk impact objects

The risk impact object means that once a risk occurs, it will have an impact on one or more aspects of the project, before determining the severity of risk consequences, determining the relationship between risk impact objects helps to better assess risks, so as to "prescribe the right medicine" and develop more effective risk response measures.

Risks mainly affect the quality, cost, and duration of the project. In many cases, a risk may affect both the cost and the collection period. In this case, you need to estimate the impact of the risk on the above three aspects, this is used to determine the most influential object of the risk.

2. risk parameters and risk levels

The risk is evaluated based on the risk assessment criteria identified in the Plan, the risk possibility and consequence severity are determined, and the risk coefficient is calculated.

 

V. Risk tracking and reporting 1. Risk tracking

The risk tracking frequency can be determined based on the risk level. High-level risks are implemented frequently, while low-level risks can be tracked at intervals for a long time. Because some risks may occur at a specific stage and do not need to be monitored immediately, you can also define the start time of risk tracking and track risks from this time.

When tracking risks, the risk owner re-evaluates the risk parameters and risk levels, monitors the risk status, updates risk response measures, and records the tracking information. Each risk trace must record one trace at a time. Tracking information includes implementation of risk mitigation measures, risk changes, and causes of risk closure.

This risk can be disabled when the risk falls to an acceptable range or disappears. When closing a risk, you must specify the reason for closing the risk in the remarks. For example, if there are three new interns in the project team, the personnel risk is disabled.

2. risk reporting and Measurement

Project risks should be reported to managers in weekly reports, milestone reports, and project summary reports. The weekly report reports the current status of all risks, and the Milestone Report and project summary report also need to measure and analyze risks.

 

---------------------------------------------------------------------------

Http://blog.csdn.net/arui319

The Android Application Development solution has been published. You are welcome to purchase and read it.

This article can be reproduced, but please keep the above author information.

Thank you.

---------------------------------------------------------------------------