Project Manager: Managing Changes to the Project Scope Document, Essay Example

Introduction

The Project Scope document provides the baseline terms of reference for a project. As time progresses elements of change occur and these need to be managed via change control procedures in a project.  This paper outlines the fundamentals of change control procedures in Project Management.

Change Control

There are two basic types of change condition on a project: (1) Off Specification – where an activity deviates from the baseline plan and original terms of reference. (2) Exception Condition – A serious situation of a deviation that has the potential to terminate the project unless management intervention is made.

Off Specification

This is generally a change situation within the scope and control of the Project Manager.  It may mean a potential time extension; need to allocate additional resources (time and cost implication).  This essentially causes a re-baseline of the project plan but is not serious enough to stop the project from being completed within an acceptable timeframe and to original scope.

Exception Condition

Here a serious change condition has occurred that may potentially terminate the project. The Project Manager will need Project Management Board approval in order to take corrective action.  In this case if the situation is serious enough the PM may even recommend closure of the project.  An example might be a company merger or takeover situation that changes the entire scope of the project.  In certain cases it may need a revised project scoping statement and new project plan or even a re-start of the project.  In all; cases configuration control (version control) of all documents is paramount in order to track the audit trail of change