Project change management

Change is inevitable , But it needs to be standardized .

Changes often occur in the process of information system engineering construction , Many project failures are caused by improper handling of changes . Changes are positive and negative , Good change management can improve the quality of the project 、 speed of progress 、 Cost management is more effective .

One 、 The basic concept of project change management

The essence of change management , It is based on the increasingly rich project cognition in the process of project promotion , Constantly adjust the direction of project efforts and resource allocation , Meet the needs of the project to the greatest extent , Enhance project value .

1、 Reasons for project change
Negligence or negligence
Value added change
Emergency plan or avoidance plan
Perform passive adjustments resulting from inconsistencies with the benchmark
External events

2、 Project change classification
1） According to the nature of the change ： major alteration 、 Important changes 、 General changes . Control through different approval permissions .

2） According to the urgency ： Emergency change 、 Non urgent change . Through different change processing processes .

3） Divide according to the change contents , It can be divided into several sub industries , Different contents adopt different control methods .

3、 Meaning of project change
Change management is to make the project benchmark consistent with the actual implementation of the project , A set of management methods to deal with project changes . The result is either to reject change , Or adjust the project benchmark .

From the perspective of value-added resources , The substance of the change , Is to adjust the way resources are allocated , Or use the reserved resources in the project , Meet the needs of the project .

Two 、 Project change management principles

The principle of change management is project benchmarking 、 Standardization of change management process . Including the following ：

1、 Benchmark management
Benchmark is the basis for change . After the initial benchmark is established , After each change passes the review , Should be re benchmarked .

2、 Change control flow ：
Establish or select a change management process that meets the needs of the project , All changes must be controlled according to this control process .

3、 Clarify the organization and division of labor

4、 Evaluate the possible impact of the change

5、 Keep the relevant documents generated by the change properly

3、 ... and 、 Change management organization and working procedures

1、 Organization
Advocate decentralized operation , Specify the resource allocation convention . Generally, the agreed work is performed by the project implementer according to the benchmark , The operation authority is delegated to the project manager ; The reserve resources of the project are unauthorized , Support project change operations , The right belongs to the project sponsor , The representative is the management committee .

1）CCB
Project control committee or configuration control committee , Or similar organizations . Is the representative of all rights and interests of the project , Responsible for deciding which changes to accept . It is composed of relevant personnel , It usually includes decision makers of users and implementers .

Be careful CCB It's a decision-making body , It's not an operating agency , Usually only responsible for review , Decide whether to change , But don't propose a change plan .

2） project manager
The project manager is entrusted by the owner to be responsible for the operation process of the project , Rights are derived from the project charter , The authority to schedule resources is usually defined by benchmarks . The reserved resources not included in the benchmark can only be used after being approved by the authorized person .

3） The role of the project manager in change
Respond to change requests ; Evaluate the impact of the change on the project and the response plan ; Transform requirements from technical requirements to resource requirements , For the authorizer to make decisions ; Implement according to the review results , Adjustment datum ; Ensure that project benchmarks reflect project implementation .

2、 Working procedure
1） Propose and accept changes
2） Preliminary review of changes
3） Demonstration of change plan
4） The project management committee reviews
5） Issue change notice and organize implementation
6） Monitoring of change implementation
7） Evaluation of change effect
8） Judge whether the changed project has been put into the normal track

Four 、 Work content of project change management

Proposal of change 、 Treatment should be standardized , Especially when the overall pressure of the project is high . Batch processing can be used 、 Improve efficiency by prioritizing . If the project is small , The degree of association with other projects is small , The proposal and handling of changes can be handled simply and efficiently , But it still needs to be formal and standardized .

1、 Strictly control the submission of project change application
Strict control means , The change management system can ensure that the project benchmark can reflect the implementation of the project . All changes need to be submitted , But the efficiency can be improved according to the actual situation .

2、 Change control
1） Control of schedule change
Judge the current progress status , Control the factors that affect the progress , When progress changes , Manage it

2） Control of cost changes
Control the factors that affect the cost , Find out the cause of cost deviation , Managing change

3） Control of contract changes
Control contract modification

3、 The relationship between change management and other project management elements
1） Change management and overall management
Change management is a part of the overall project management .

2） Change management and configuration management
If the overall deliverables of the project are regarded as configuration items of the project , Change management can be seen as part of configuration management ;

Change management and configuration management can also be regarded as two sets of related mechanisms . When change comes , Configuration management invokes change management , Change management feeds the adjustment results back to configuration management .

5、 ... and 、 Version release and fallback plan

1、 Prepare before the software version is released

2、 Release the emergency fallback plan

3、 Summary of version release and rollback implementation process
In depth analysis of the reasons for fallback , To sum up your experience , Avoid fallback happening again ; Improve the fallback plan