Risk Management Plan by 2G5kbw

VIEWS: 2 PAGES: 4

									                   Scope Management Plan


Project Name:        California Statewide VINE
Department:          Professional Services
Project Manager:     Stephen Adams
Date:                November 19, 2007
                                             Scope Management Plan




PURPOSE OF THE DOCUMENT ........................................................................ 1

CHANGE CONTROL ROLES AND RESPONSIBILITIES ................................... 1

BASELINE THRESHOLDS ................................................................................. 1
    Scope Baseline Threshold ........................................................................................... 1
    Schedule Baseline Threshold ..................................................................................... 1
    Cost Baseline Threshold ............................................................................................. 1

CHANGE CONTROL PROCEDURES ................................................................. 1
    Methods Used to Initiate Change Requests .............................................................. 1
    Change Request Format ............................................................................................. 2
    Preliminary Analysis Ownership and Responsibilities ........................................... 2
    Detailed Analysis Ownership and Responsibilities .................................................. 2

REFERENCED DOCUMENTS ............................................................................ 2

DOCUMENT REVISION HISTORY...................................................................... 2
                                 Scope Management Plan

PURPOSE OF THE DOCUMENT
The purpose of this Project Scope Change Plan is to establish a plan to govern how baseline
changes are controlled during Project Execution and Control.

CHANGE CONTROL ROLES AND RESPONSIBILITIES
The Project Manager has the ability to submit a Project Change Control Document in the
following scenarios:
      To redefine the scope of the project for the customer or Project Sponsor – either adding
       or deleting from the project baseline as defined in the Contract, Project Requirements
       Document or previously-approved Project Change Control Documents.
      To redefine items that may not be technically feasible after discussions with the Subject
       Matter Experts or technical staff.
The final authority for the approval of any Project Change Control Document resides with the
Project Sponsor and customer. If a Project Change Control Document is submitted and not
approved, the original scope of the project will remain as the approved baseline. Once a Change
Control Document is approved, any changes to the budget or schedule will be incorporated into
project documentation and become the new approved baseline.
NOTE: The Change Control Document is used to track the changes to the project baseline.
Changes may or may not cause additions/deletions to the budget or schedule. The Change
Control Documents are appended to the Project Requirements Document throughout the project
to capture the overall scope of work.

BASELINE THRESHOLDS
Scope Baseline Threshold
Any change to the scope of a project after approval of the Contract and/or the Project
Requirements Document objectives will require a Project Change Control Document.

Schedule Baseline Threshold
Any change in the delivery date of greater than one (1) month will require a Project Change
Control Document.

Cost Baseline Threshold
Any change in the approved estimate greater or less than ten percent (+/- 10%) will require a
Project Change Control Document.

CHANGE CONTROL PROCEDURES
Methods Used to Initiate Change Requests
The following methods may be used to outline proposed changes, in order to initiate a change
request:



07/05/2012                                     1                                     Version 1.0
                                  Scope Management Plan

            A telephone conversation between the Project Manager and/or Project Sponsor, and
             the customer.
            An email to the Project Manager and/or Project Sponsor from any individual
             approved by the customer to submit change requests
            Meeting minutes recorded during customer meetings

Change Request Format
A change request should include the specific change(s) requested, along with any approval
already given by the Project Sponsor and the customer for the change if the change was not
initiated by the customer.

Preliminary Analysis Ownership and Responsibilities
A Change Request must be appropriately analyzed to determine the impact to the project. The
Project Manager will be responsible for ownership of the primary analysis to determine if the
Change Request is possible, given any limitations on schedule, scope, or resources.

Detailed Analysis Ownership and Responsibilities
The deliverable owner most affected by a potential change will be assigned the responsibility of
conducting a detailed analysis to determine if the Change Request is possible, given any
limitations on schedule, scope, or resources. This analysis will be provided to the Project
Manager in a timely manner to allow for discussions with and recommendations to the Project
Sponsor and the customer.

REFERENCED DOCUMENTS
   1. Project Change Control Document




                                 Document Revision History

   Version       Date                     Changes                          Updated By
     1.0        4/30/07   Original document                             C. Higginbotham




07/05/2012                                      2                                    Version 1.0

								
To top