change management process , typical flow diagram / guideline

1. Perform Change Management
Change Management is the process of monitoring and
controlling changes within a project. By managing the
implementation of change, you can:
Reduce the impact of changes to the project
Identify new issues and risks as a result of changes
raised
Ensure that changes do not affect the project's ability
to achieve its desired objectives
Control the cost of change within the project
Change Management is comprised of a set of processes,
roles and documents for managing change in the project,
each of which are described as follows.
Change Management Process
Projects are typically undertaken within changing business environments, so it's inevitable that
during the life of your project, there will be some element of change required. Whether a
customer requests a change to their requirements, management requests a change in
priorities or team members request a change in roles, you will need an effective Change
Management Process to minimize the resulting impact on your project.
Change Management first begins with the completion of a Change Request Form, which allows
team members to describe the nature of the change identified. The Project Manager will
investigate this change request and determine whether the change is critical to the project's
success. If they believe that the change must be implemented then he or she could,
depending on the extent of that change, request approval from the Project Board. Following
approval, the change is scheduled and implemented accordingly. Finally, the Project Manager
will review the change to ensure that it has had the desired effect on the project and close it in
the Change Register.
The following diagram depicts the processes undertaken to monitor and control within the
project.

2. A more detailed description of the Change Management Process follows.
Identify Change
The first step in the change process is to identify the need for change. Any team member can
suggest a change to the project, if he or she believes it is needed to keep the project

3. producing deliverables to the customer's specified requirements. After identifying a need for
change, the team member records relevant information on a Change Request Form
(commonly called a CRF), describing the change, and identifying drivers, benefits, costs and
likely impact of the change on the project. The CRF is forwarded to the Project Manager for
review and approval.
Review Change
The Project Manager investigates the change to identify the reason for it and its impact. Then
he or she decides whether it is critical to the successful delivery of the project. Changes which
are not critical to project delivery should be avoided whenever possible to prevent "scope
creep" (i.e. the gradual increase in scope throughout the Project Lifecycle).
If the change is deemed critical to success, the Project Manager either approves the request or
seeks approval for the CRF raised. In some cases, the Project Manager has the direct authority
to approval minor change requests; however, in most cases the Project Manager needs to
seek CRF approval from the Project Board.
Approve Change
The Project Board reviews the details in the CRF to determine whether or not the change
should be implemented. Based on the level of risk, impact, benefits and cost to the project, it
may decide to decline, delay or approve the change request.
Implement Change
The Project Manager approves all changes, which are then are scheduled and implemented
accordingly. After implementation, the Project Manager reviews the effects of the change on
the project to ensure that it achieved the desired outcome, when the change is then closed in
the Change Register.
Throughout the Change Management Process, the Project Manager can monitor and control
changes to the project by keeping this Change Register up-to-date.