D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

APPENDIX ‘A’

PROJECT SCOPE MANAGEMENT PLAN

DESIGNING AND CONSTRUCTION

Project Name OF CAFE AT MURREE EXPRESS Project Number 17082013
HIGHWAY, MUREE
Mr. Nadeem
Customer Zareeyat Group Of companies Prepared By
Ahmed

Document Change History

Created by: Mr. Nadeem Ahmed Created on Date: 28TH NOV, 2019
Change Changed by Reason Description Comment Approver
Date

1
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

TABLE OF CONTENTS

INTRODUCTION .................................................................................................................. 3
SCOPE MANAGEMENT APPROACH ....................................................................................... 3
ROLES AND RESPONSIBILITIES ............................................................................................ 8
SCOPE DEFINITION ............................................................................................................ 8
PROJECT SCOPE STATEMENT ............................................................................................. 9
WORK BREAKDOWN STRUCTURE ........................................................................................ 9
SCOPE VERIFICATION ....................................................................................................... 12
SCOPE CONTROL............................................................................................................. 13

2
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

INTRODUCTION
1. The Scope Management Plan provides the scope framework for this project.
This plan documents the scope management approach; roles and responsibilities as
they pertain to project scope; scope definition; verification and control measures; scope
change control; and the project’s work breakdown structure. Any project
communication which pertains to the project’s scope should adhere to the Scope
Management Plan.

2. The purpose of this project is to create a concrete plan for Reese's Cafe first
store located along side Muree hill. Our project aims to have all responsibilities and
tasks efficiently organized in order to plan the opening of our bussiness stategically and
on schedule.

3. Located at the start of expressway Muree, Reese's Cafe will rapidly establish
itself as a known brand in the Coffee shop industry. Our unique ability to achieve all
objectives will develop an unparalleled corporate culture creating a positive impact in
the food industry essential to productivity and success. By offering our customers value
and a unique new cafe experience this can be done effectively in all parts of our
bussiness model.

SCOPE MANAGEMENT APPROACH

4. For this project, scope management will be the sole responsibility of the Project
Manager. The scope for this project is defined by the Scope Statement, Work
Breakdown Structure (WBS) and WBS Dictionary. The Project Manager, Sponsor and
Stakeholders will establish and approve documentation for measuring project scope
which includes deliverable quality checklists and work performance measurements.
Proposed scope changes may be initiated by the Project Manager, Stakeholders or any
member of the project team. All change requests will be submitted to the Project
Manager who will then evaluate the requested scope change. Upon acceptance of the
scope change request the Project Manager will submit the scope change request to the
Change Control Board and Project Sponsor for acceptance. Upon approval of scope
changes by the Change Control Board and Project Sponsor the Project Manager will
update all project documents and communicate the scope change to all stakeholders.
Based on feedback and input from the Project Manager and Stakeholders, the Project
Sponsor is responsible for the acceptance of the final project deliverables and project
scope.

3
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

REQUIREMENT COLLECTION

INPUT:

Project charter

Project charter is already described in the document.

Stakeholder register:

Tools and Techniques:

Interview:

OUTPUT:

Requirement management plan:

SUBJECT REQUIREMENT STAKEHOLDERS

Site Selection

4
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

Site plan

Site coverage
and
Implementable
material site
coverage plan

Designing and
Architectural
work

Floor Plans

Elevations

Cross section
and Structural
details

5
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

SCOPE DEFINATION:

6
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

7
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

ROLES AND RESPONSIBILITIES

5. The Project Manager, Sponsor and team will all play key roles in managing the
scope of this project. As such, the project sponsor, manager, and team members must
be aware of their responsibilities in order to ensure that work performed on the project is
within the established scope throughout the entire duration of the project. The table
below defines the roles and responsibilities for the scope management of this project.
Name Role Responsibilities
Mr. Amir Mehmood Sponsor - Approve or deny scope change requests
as appropriate
- Evaluate need for scope change
requests
- Accept project deliverables
Mr. Nadeem Ahmed Project - Measure and verify project scope
Manager - Facilitate scope change requests
- Facilitate impact assessments of scope
change requests
- Organize and facilitate scheduled change
control meetings
- Communicate outcomes of scope
change requests
- Update project documents upon approval
of all scope changes
Mr Ashraf Kiani ( Team - Measure and verify project scope
Planning Manager) Leaders - Validate scope change requests
Ms. Rubina Khan ( - Participate in impact assessments of
Design Manager) scope change requests
Mr. Adil Rehman - Communicate outcomes of scope
(Structure Engineer) change requests to team
- Facilitate team level change review
process
Azhar (Sr.Architect) Team - Participate in defining change resolutions
Imran (Sr.Architect) Members - Evaluate the need for scope changes
Aneel (Jr.Architect) and communicate them to the project
Bakht (Draft person) manager as necessary
Farman (Draft person)
Atif (3d vizualizer)
Danish (Structure)

Table 1.1 : Scope Management Roles and Responsibilities

8
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

PROJECT SCOPE STATEMENT

7. The project scope statement provides a detailed description of the project,
deliverables, constraints, exclusions, assumptions, and acceptance criteria.
Additionally, the scope statement includes what work should not be performed in order
to eliminate any implied but unnecessary work which falls outside the of the project’s
scope.

8. This project includes the mockup design, manufacturing of mockup, installation of

on mockup, interfacing , testing, implementation, and an Operation Manual for assisting
both 1st and 2nd line maintenance. The main deliverable for this project is a completed
Mockup/Tester capable of testing various related to ABCsystem. This project will be
accepted once the Mockup has been successfully tested in both 1 st and 2nd line
maintenance shops and has been shown to be compatible with the company’s current
maintenance infrastructure. This project does not include ongoing operations and
maintenance of the mockup. Only internal personnel and resources may be used for
this project. Additionally, the project is not to exceed 30 days in duration or $1.00
Million in spending. Assumptions for this project are that support will be provided by the
project sponsor and all department managers and that adequate internal resources are
available for the successful completion of this project.

WORK BREAKDOWN STRUCTURE

9. In order to effectively manage the work required to complete this project, it will be
subdivided into individual work packages which will not exceed 40 hours of work. This
will allow the Project Manager to more effectively manage the project’s scope as the
project team works on the tasks necessary for project completion. The project is broken
down into seven phases: the plan phase; the mockup design phase; the mockup
manufacturing phase; the installation phase; the interfacing phase; testing phase and
close-out phase. Each of these phases is then subdivided further down to work
packages which will require no more than 40 hours of work and no less than 4 hours of
work (see WBS structure below).

9
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

C-130 Autopilot
LRUs...

LRUs Interfacing
Mockup Design Close out

Engineering Material System interface Post Project

Diagram Specificati... Looming Operation Manual QA report
uni... Report

Mockup
Manufacture

Frames Rails Mounts

Testing
LRUs Installation Planning

Resource Ground Checks Aerial Checks QC Checks

Scope Cost baseline Schedule
Calendar

Avionic Interface DC Power Servo Motors

Un...

ARINC 429 Bus RS232 Bus CSDB Bus

Replays SPD CB Panel Earthing

Figure 1.1: Work Breakdown Structure (WBS) Hierarchical Form

10
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

Level WBS Code Element Name

1 C-130 1 ABC Mockup
2 C-130 1.1  Planning
3 C-130 1.1.1 o Scope
3 C-130 1.1.2 o Cost baseline
3 C-130 1.1.3 o Schedule
3 C-130 1.1.4 o Resource Calendar
2 C-130 1.2  Mockup Design
3 C-130 1.2.1 o Engineering Diagram
3 C-130 1.2.2 o Material Specification
2 C-130 1.3  Mockup Manufacture
3 C-130 1.3.1 o Frames
3 C-130 1.3.2 o Rails
3 C-130 1.3.3 o Mounts
2 C-130 1.4  Installation
2 C-130 1.5  Interfacing
3 C-130 1.5.1 o Looming
3 C-130 1.5.2  System interface unit
4 C-130 1.5.2.1 o Avionic Interface Unit
5 C-130 1.5.2.1.1  ARINC 429 Bus Layout
5 C-130 1.5.2.1.2  RS232 Bus Layout
5 C-130 1.5.2.1.3  CSDB Bus Layout
4 C-130 1.5.2.2 o DC Power
5 C-130 1.5.2.2.1  Relays
5 C-130 1.5.2.2.2  SPD
5 C-130 1.5.2.2.3  CB Panel
5 C-130 1.5.2.2.4  Earthing
4 C-130 1.5.2.3 o Servo Motors
2 C-130 1.6  Testing
3 C-130 1.6.1 o Ground Checks
3 C-130 1.6.2 o Aerial Checks
3 C-130 1.6.3 o QC Checks
2 C-130 1.7  Close out
3 C-130 1.7.1 o Operation Manual
3 C-130 1.7.2 o QA report
3 C-130 1.7.3 o Post Project report

Figure 1.2, Work Breakdown Structure (WBS) Tabular Form

10. In order to more clearly define the work necessary for project completion the
WBS Dictionary is used. The WBS Dictionary includes an entry for each WBS element.
The WBS Dictionary includes a detailed description of work for each element and the

11
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

deliverables, budget and resource needs for that element. The project team will use the
WBS Dictionary as a statement of work for each WBS element.

WBS DICTIONARY

Level WBS Code Element Name Description Budget

1 C-130 1 ABC Mockup As req As req
2 C-130 1.1 Planning As req As req
3 C-130 1.1.1 Scope As req As req
3 C-130 1.1.2 Cost baseline As req As req
3 C-130 1.1.3 Schedule As req As req
3 C-130 1.1.4 Resource Calendar As req As req
2 C-130 1.2 Mockup Design As req As req
3 C-130 1.2.1 Engineering Diagram As req As req
3 C-130 1.2.2 Material Specification As req As req
2 C-130 1.3 Mockup Manufacture As req As req
3 C-130 1.3.1 Frames As req As req
3 C-130 1.3.2 Rails As req As req
3 C-130 1.3.3 Mounts As req As req
2 C-130 1.4 Installation As req As req
2 C-130 1.5 Interfacing As req As req
3 C-130 1.5.1 Looming As req As req
3 C-130 1.5.2 System interface unit As req As req
4 C-130 1.5.2.1 Avionic Interface Unit As req As req
5 C-130 1.5.2.1.1 ARINC 429 Bus As req As req
5 C-130 1.5.2.1.2 RS232 Bus As req As req
5 C-130 1.5.2.1.3 CSDB Bus As req As req
4 C-130 1.5.2.2 DC Power As req As req
5 C-130 1.5.2.2.1 Replays As req As req
5 C-130 1.5.2.2.2 SPD As req As req
5 C-130 1.5.2.2.3 CB Panel As req As req
5 C-130 1.5.2.2.4 Earthing As req As req
4 C-130 1.5.2.3 Servo Motors As req As req
2 C-130 1.6 Testing As req As req
3 C-130 1.6.1 Ground Checks As req As req
3 C-130 1.6.2 Aerial Checks As req As req
3 C-130 1.6.3 QC Checks As req As req
2 C-130 1.7 Close out As req As req
3 C-130 1.7.1 Operation Manual As req As req
3 C-130 1.7.2 QA report As req As req
3 C-130 1.7.3 Post Project report As req As req

Table 1.2: WBS Dictionary

SCOPE VERIFICATION
11. As this project progresses the Project Manager will verify interim project
deliverables against the original scope as defined in the scope statement, WBS and

12
D&M of C-130 Autopilot LRUs Testing Mockup Template Issued By: SZABIST PMO

Project Risk Management Plan

WBS Dictionary. Once the Project Manager verifies that the scope meets the
requirements defined in the project plan, the Project Manager and Sponsor will meet for
formal acceptance of the deliverable. During this meeting the Project Manager will
present the deliverable to the Project Sponsor for formal acceptance. The Project
Sponsor will accept the deliverable by signing a project deliverable acceptance
document. This will ensure that project work remains within the scope of the project on
a consistent basis throughout the life of the project.

SCOPE CONTROL
12. The Project Manager and the project team will work together to control of the
scope of the project. The project team will leverage the WBS Dictionary by using it as a
statement of work for each WBS element. The project team will ensure that they
perform only the work described in the WBS dictionary and generate the defined
deliverables for each WBS element. The Project Manager will oversee the project team
and the progression of the project to ensure that this scope control process if followed.

13. If a change to the project scope is needed the process for recommending
changes to the scope of the project must be carried out. Any project team member or
sponsor can request changes to the project scope. All change requests must be
submitted to the Project Manager in the form of a project change request document.
The Project Manager will then review the suggested change to the scope of the project.
The Project Manager will then either deny the change request if it does not apply to the
intent of the project or convene a change control meeting between the project team and
Sponsor to review the change request further and perform an impact assessment of the
change. If the change request receives initial approval by the Project Manager and
Sponsor, the Project Manager will then formally submit the change request to the
Change Control Board. If the Change Control Board approves the scope change the
Project Sponsor will then formally accept the change by signing the project change
control document. Upon acceptance of the scope change by the Change Control Board
and Project Sponsor the Project Manager will update all project documents and
communicate the scope change to all project team members stakeholders.

13