The Phenom

Scope Management Plan

The Phenom

Submitted By:
Ameer Hamza, Umar Khalid

Submission Date:
3 June, 2019
Table of Contents

1. MANAGEMENT APPROACH------------------------------------------------------------------------- 2

2. SCOPE DEVELOPMENT ------------------------------------------------------------------------------- 2

3. COLLECT PROJECT REQUIREMENTS ------------------------------------------------------------ 2

4. SCOPE DEFINITION ------------------------------------------------------------------------------------ 2

5. PROJECT SCOPE STATEMENT ---------------------------------------------------------------------- 3

6. DELIVERABLES ACCEPTANCE -------------------------------------------------------------------- 5

7. SCOPE CONTROL --------------------------------------------------------------------------------------- 5

8. WORK PERFORMANCE DATA ---------------------------------------------------------------------- 5

9. APPROVED ----------------------------------------------------------------------------------------------- 6

10. PLAN APPROVAL ------------------------------------------------------------------------------------- 6

1
1. MANAGEMENT APPROACH
The term “project scope” refers to the sum of all products, services and results that will be provided
as the project.

The purpose of this scope management plan is to set forth the plans and procedures for defining,
developing, monitoring, controlling, changing, implementing and verifying the project scope. It’s
the intent of scope management to ensure the completion of all the work required, and only the
work required, to complete the project successfully.

The project manager will assume overall responsibility for project scope management. The people
listed below will assume the following scope management responsibilities:
Roles Responsibilities
Project Manager Abdullah Khan
Project Sponsor HBL, Rawalpindi
Project Team Lead Project Manager
Project Team Members The Phenom

2. SCOPE DEVELOPMENT
The scope of this project is defined in the Scope Definition section, below. Development of the
project scope began with an examination of the following sources:
• Project Charter
• Applicable codes, regulations, statutes and laws
• Stakeholders
• Organizational Process Assets

3. COLLECT PROJECT REQUIREMENTS

The complete requirements gathering and definition process is described in the Requirements
Management Plan and all known project requirements are set forth in the Requirements
Traceability Matrix. The Requirements Traceability Matrix is included in the Requirements
Management Plan.

4. SCOPE DEFINITION
The project scope baseline is comprised of the project scope statement and the work breakdown
structure.

2
5. PROJECT SCOPE STATEMENT
Project Name The Phenom P1 Date 8 September, 2018

Project MIS 000357 Project Abdullah Khan

Number Manager

Business Need / Project Objectives

The proposed system can identify the person who has obtained the equipment for his/her use. And
provide safety measures.
It is designed to provide the luxury of a modern automobiles.

Generate reports on all equipment checked out by employees.

Project Description and How it Meets the Business Need

One of the most important goal of this project is cost reduction made possible by fewer control
of assets, by better visibility of lost/stolen/damaged car, which in turn leads to better cost
allocation decisions, and by more efficient processes.

Project Requirements

Determine which type of assets will be part of this project.

Establish suitable depreciation method for fixed assets.

Establish assets handling, maintenance, procurement and other necessary departments.

Project Deliverables

The main deliverable of this project will be a redesigned and upgraded assets management system
that is usable, compliant with accessibility requirements and more manageable.

3
Project Does Not Include

Construction and redesigning of existing department.

Development of any other unit.

Decision

Approved Rejected

Approved with modifications Deferred

Required Modifications

Additional Comments

4
6. DELIVERABLES ACCEPTANCE
Describe the manner in which project deliverables will be formally presented and accepted. Will
they be presented at the end of each phase? Will they be presented at regular intervals? Who will
present the project deliverables and to whom will they be presented?
Role Responsibility
Internal inspection/audit team Verifies the project deliverables
Project team members Presents the project deliverables
Project manager Reviews the project deliverables
Project sponsor/client Accepts or rejects the project deliverables

7. SCOPE CONTROL
Controlling project scope is the process of monitoring the status of the project scope and
managing changes to the scope baseline. Who is responsible for monitoring the project scope to
ensure the project remains within the scope baseline? What processes will be used?

8. WORK PERFORMANCE DATA

What work performance data will be captured? Who will track the number of change requests
received? Who will track the number of deliverables completed? Variance Analysis

Variance analysis is a technique used for determining the cause of any difference and the degree
of any difference between the scope baseline and the actual performance. Describe the processes
for performing variance analysis. When is corrective or preventative action required? Change
Requests

All requests for change must be submitted in writing. The following people may initiate changes
to the project scope:

5
 • Project sponsor
• Project Manager
• Project team members
• Other project stakeholders

9. APPROVED
When a change request is approved, the project manager will track the approval on the change
request log found in scope statement. The project manager will also ensure implementation of the
change, as it was submitted and approved. Where implementation affects changes to the project
management plan, the project manager will revise the plan and distribute notice of the revisions in
accordance with the procedures set forth in the communication management plan.

When a change request is approved with modifications, the project manager will track the modified
approval on the change request log. The project manager will also ensure implementation of the
change, as it is modified.

Where implementation affects changes to the project management plan, the project manager will
revise the plan and distribute notice of the revisions in accordance with the procedures set forth in
the communication management plan.

Rejected
When a change request is rejected, the project manager will track the rejection on the change
request log and provide written notice of the rejection to the party who initiated the change. No
further action will be taken.

10. PLAN APPROVAL

By signing below, I, ____________________________ in my capacity as Project Sponsor approve

of this Scope Management Plan.

Name: HBL, Rawalpindi Title: ACM, Rawalpindi.

______________________________________________________________________
Signature Date
Approved

6
7