WEB Project Manager manual-[6] risk management

Risk management is one of the most important tasks for project managers in web projects. Risk management is a continuous process throughout the project. Risk management includes risk identification, risk estimation, Risk Resolution, and risk management strategies.

In actual web projects, project risks are mainly manifested in the following situations. Understanding these helps the Project Manager identify these risks at the beginning of the project and take measures to avoid or reduce them.

I. Web project risk list:
1: demand change risk: the demand has been baseline, but there are still changes that will affect the project.
How can we reduce the occurrence of such risks?
(1) The demand discussion in the early stage should be detailed and complete. The scope and function description of the requirements must be clear.
(2) A demo is required in the requirement document. For web projects, images can better illustrate problems than text.
(3) Identify the decision makers (usually product managers, relevant functional supervisors, and customer service personnel) who need the project. All the requirements must be recognized by them.
(4) The customer's full participation in the project helps reduce such risks. Customers are required to participate in the requirement discussion, requirement confirmation, user case confirmation, and customer acceptance in the test phase.
(5) When a demand change occurs, the change process is strictly followed.

2. Technical Risks: technical difficulties encountered during the development process may lead to a delay in development time or the demand may have to be changed.
How can we reduce the occurrence of such risks?
In the technical evaluation phase before the project starts, clarify technical difficulties and arrange personnel to overcome them in advance. If the problem cannot be solved within the expected time, the demand side can be requested to change the demand.

3. Quality risk: for web projects, quality risk mainly refers to developmentCodeQuality.
How can we improve the quality of developer development?
(1) when preparing a project plan, evaluate the development time as much as possible. Reasonable Development time has a great impact on the development quality.
(2) there is a set of strict and feasible code specifications, which are strictly followed during coding and strictly assessed during code review.
(3) Before coding, developers should be familiar with the Framework.
(4) A good system design document is very important for guiding development.

4. Resource risks: the human resources required by the project cannot be put in place on time, resulting in resource risks.
How can we reduce the occurrence of such risks?
In this case, you need to apply for resources in advance during project planning and continuously communicate and coordinate during the project process.

II. Key Points of project risk management:
1. The above-mentioned risk management refers to the risks that can be expected to occur, and those that cannot be expected will not fall into the scope of risk management. This also shows that the project manager's experience and knowledge are critical to the ability to manage risks.
2. a detailed project plan and quality assurance for each key point during project execution are necessary to reduce project risks.
3. Risk report is an effective means for project teams and leaders to understand project risks.
The risk report format is usually:

Serial number

Risk Overview

Impact on projects

Solution (countermeasure)