WEB Project Manager manual-[4] demand change management

Demand change management is the most important part of web project management. The effectiveness of demand change management directly affects the success of the project.

Attitude towards changes:
1. changes are inevitable.
2. Changes must be managed.
3. Actively discover the cause of the change, and make the change appear as early as possible to reduce the risks brought by the change.

Objectives of demand change management:
1. Relevant stakeholders must have a clear understanding of the changes.
2. Changes are under effective management.
3. minimize the risks caused by changes.

By developing a demand change process, we can ensure that demand changes in the project are effectively implemented to achieve the above objectives.

Demand change process:
1. determine the baseline of the requirement.
Generally, we use User case as the requirement baseline. Any requirement changes after User case is confirmed must follow the requirement change process. Requests that do not follow the demand change process will not be accepted.

2. First, the Project Manager receives the requirement for requirement change.
The requirement change reporter can be anyone in the project, including the product manager, customer service, developers, and testers.

3. The Project Manager evaluates the demand change.
The Project Manager can call relevant personnel to discuss the rationality, feasibility, implementation cost, and impact on the change.
As the project owner, the project manager is primarily responsible for project success. Therefore, the project manager is responsible for the decision makers of demand changes.
 
4. After the change request is confirmed, a dedicated person will record the change request (in the following format) and notify all members of the project. The following personnel are closely related to the demand change, and they must be aware of and acknowledge the change. Including (customer representatives, demand analysts, testers, and related developers ).
Format of the requirement change table:

Serial number

Change submission time

Change description

Change type (whether to modify the original requirements or add new requirements)

Cause

Change author

Developers

Impact on progress (workload)

5. After receiving the confirmed change request, the relevant personnel should do the following.
The requirement analyst modifies the requirement specification and user case.
The tester modifies the content of the test case.
Developer ModificationCode.

6. Demand freezing
The later the project arrives, the greater the impact of demand changes on the project. Therefore, we will enter the demand freezing stage and will not accept the changes.