5.

Scope Management Plan

5.1 General Project Information

Project Name: Laboratory Development Project

Location: Mechanical Engineering Building, University of Alberta,
Edmonton, Canada
Project Manager: Shannon MacDonald

5.2 Scope Assumptions

It is assumed that all changes to the project scope will required notification to
the following stakeholders: The project owner Dr Lipset, Shannon MacDonald
Project Manager for Chrome Engineering, Researchers using the lab 1-38,
Mechanical Engineering Technician responsible for commissioning the lab (via
Dr. Glen Thomas).

5.3 Scope Constraints

It is assumed that creation, changes, updates to project scope will require

approval of the project owner Dr. Lipset and the Project Manager for Chrome
Engineering Shannon MacDonald.

5.4 Scope Risks

We have found that some of the supporting stakeholder information such as

researcher surveys are slow to respond. This may cause scope dependency
risks.

5.5 Production of a detailed Project Scope Statement

Upon receipt of client feedback, stakeholder feedback (researcher surveys) we

will update any new or improved details of the project and product scope into
the preliminary version as well as new details found from the development of
the Work Breakdown Structure into the production of the detailed Project Scope
Statement.

Creation of the Detailed Scope Statement Documentation and updates will be

primarily handled by team member Sean Hodgson. All additions, changes,
corrections, and updates are to be submitted in writing via an approved ECR
(see appendix 5.9 for ECR form). This process will be described further in
 section 5.8, but will require the involvement of the requesting stakeholder, the
Chrome Engineering Project Manager Shannon MacDonald, and the Project
Client Dr. Lipsett.

5.6 Creation of Work Breakdown Structure

The creation of the work breakdown structure for this project will follow the
following steps. The project team for Chrome Engineering will evaluate the
detailed project scope statement, its deliverables and overall project work and
break it down into smaller more manageable pieces. These pieces will be
illustrated and further broken down using a graphical representation via a
network diagram. The components of the network diagram will be further
expanded upon in the creation of a WBS dictionary.

Creation of the WBS documentation and updates will be primarily handled by

team member Anand Rohit. All additions, changes, corrections and updates
are to be submitted in writing via an approved ECR (see appendix 5.9 for ECR
form). Any team member or the client can submit to Anand Rohit a completed
ECR, however it must have signed approval from both the Project Manager and
the Client Dr Lipsett.

5.7 Formal Verification and Acceptance

The final product produced for Dr. Lipsett by Chrome Engineering will be the
planning documents for the Laboratory Development Project. Our completion
and success in this project is dependent on the quality of these documents.

The minimum required level of detail of these documents must outline is listed
in the Detailed Project Scope Statement.

Assessment from the client on the quality of the project deliverables will be
based on the completeness of the project management and planning details in
the final project deliverable. This assessment will be completed with a written
review provided by an independent third party (Prof. Sami Fahmy) who will
evaluate the quality of the project management documentation provided by
Chrome Engineering and will assign a grade for this documentation.

5.8 Scope Control and Change Management

The Detailed Project Scope Statement will continue to develop with the
progress of the project. New requirements/need to be updated and approved.
All additional unexpected details must be recorded and as such the Project
Scope Statement should be updated in a formal manner. It should be
understood that additional requirements added on by the client can and most
likely will impact the overall schedule and cost of the project which is why all
changes to Project Scope require formal approval of both the project manager
and the client.

Any major change to the scope of a project requires the submission of an ECR

by a Stakeholder. This ECR is evaluated by both the project manager and the
Client Dr. Lipsett in terms of feasibility. To approve the scope change the client
must come to some understanding of the impact of the scope change to both
time and cost and approve these impacts. If the ECR is approved, the scope
documents are updated and the Project Manager notifies the appropriate
stakeholders. If the ECR is not approved the scope documents are not
approved and the Project Manager notifies the appropriate stakeholders.
5.9 Appendix: Engineering Change Request Form (ECR)

ECR# Chrome Engineering ECR Form Date Page 1 of

To: From:
Title of Change:
Priority: (Low, Medium, High) Need Date:

Project: Laboratory Development Project

Configuration Items Affected:

Justification for change

Description of Change (if necessary continue on next page)

Signature of Originator:
____________________________
Signature of Project Manager:
____________________________
Signature of Client:
____________________________