Oracle Practice

PROJECT MANAGEMENT PLAN

<……………………………..>

Author: ……………………..
Creation Date: December 22, 2015
Last Updated: December 22, 2015
Document Ref: Project Management Plan (Charter)
Version: Draft v.1

Approvals:

Ibrahim Alshutabi

1 | Page Fall 2023-2024

Document Control

Change Record

Date Author Version Change Reference

Oct 7, Tareq Almekhlafi

2023

Reviewers

Name Position

Distribution

Copy Name Location

No.

1 Library Master Project Library

2
3

Note To Holders:
If you receive an electronic copy of this document and print it out, please write your name on the
equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover, for
document control purposes.

2 | Page Fall 2023-2024

 Contents
Document Control 2
Introduction 5
Purpose 5
Background 5
Project objectives 5
Scope and Application 5
Related Documents 6
Scope 7
Scope of Project 7
Project Constraints and Assumptions 7
Scope Control 9
Approach 10
Project Methods 10
Strategy 10
Project Work Plan 10
Acceptance 10
Project Tasks, Deliverables, and Milestones 11
Planning Approach 11
Project Deliverables 11
Control and Reporting 12
Risk and Issue Management 12
Change Control 12
Status Monitoring and Reporting 13
Reviews 14
Work Management 15
Communication Model 15
Meeting Preparation 16
Meeting Structure 16
Workplan Control 17
Resource Management 18
Configuration Management 19
Deliverable Review and Acceptance 19
Document Sign-Off Process 19
Process 19
Deliverable Acceptance Criteria 20
Document Naming Conventions 20
Document Storage File Structure 21
Directory Change Control 21
Drive and Base Directory 21
Project Subdirectory Structure 21
Level 1 - Phase Level 21
Level 2 – Work Package Level 21
Level 3 to N - Details Level 22
Quality Plan 23
Approach 23
Guiding Principles 23
Quality Overview, Client Expectations and Requirements 24
Quality Overview 24
Scope 24
Roles and Responsibilities 24
Quality Assurance Activities 26

3 | Page Fall 2023-2024

 Quality Techniques 26
Audit Approaches 26
Non-Conformance Management / Escalation Procedures 27
Escalation procedures 27
Product QA Process Flowcharts 28
LIU Quality Assurance Program (QA) 29
Project management Quality Assurance Process (PMQ) 29
Quality Assurance Audit Plan 30
Follow up Committee Meetings 30
Project Planning 31
Quality Plan Review and Approval 31
Appendix A – Statement of Work 32
Appendix B – Workplan 33
Appendix C – SENYORITA, LIU Project Team Contact Information 34
Appendix D – Key tasks and responsibility for data conversion. 35
Appendix E – Deliverables 36
Appendix F – Risk and Issue Log 37
Appendix G – Change Request Forms (CRF) 38
Appendix H – Change Control Log 39
Appendix I – Project Status Report 40
Appendix J – Customer Acceptance Criteria 41
Appendix K – UAT Sign-off Letter 43
Appendix L – Go Live Certificate 44
Appendix M – Project Closure Certificate 45
Appendix N – Minute of the Meeting 46
Appendix O – Detailed Deliverable List 47

4 | Page Fall 2023-2024

Introduction

Purpose
The main goal of this project is to collect all SENYORTA’s processes and operations in one system.

Background
SENYORITA, wholly owned by the AMERCANA company. SENIORITA was founded in
1996. Initially focusing on producing potato chips, corn snacks & Biscuits, business grew
rapidly demanding expansion of the production facilities and the diversification of
products.

Project objectives
 The most important purpose of this project is to collect all SENYORTA’s
processes in one system as mentioned above.
 To make sure that operations are continuously improved
 Measure progress
 Solve problems

Scope and Application

This project management plan defines Scope of work, Objectives, Approach, Project tasks, Quality and Work
Management.

The following topics will contain the standards and procedures to be followed on the
project:
➢ Control and Reporting (issue management, scope change control, progress
reporting, etc.)
➢ Work Management (management of tasks)
➢ Resource Management (management of staff including Roles and
Responsibilities, as well as physical resources)
➢ Quality Management (reviews of deliverables, testing.)
➢ Configuration Management (how project intellectual capital and software are
to be managed.)
➢ The plan will be applied to both LIU and SENYORITA responsibilities across
the project.

5 | Page Fall 2023-2024

Related Documents
Stakeholders of the Project Management Plan can also refer to the following
documents when needed
1. LIU Contract with SENYORITA
2. SENYORITA RFP
3. LIU Proposal
4. Statement of Work

Scope

Scope of Project
The scope of the project has been detailed in the statement of work document. Refer to
statement of work page 32 on this document

Project Constraints and Assumptions

In order for LIU to meet the project commencement date and other milestones date, the
following assumptions have been made in the Project Management Plan:

• Information from suppliers must be delivered within a day to prevent disastrous

stations.
• LIU makes advantage of the infrastructure that SENYORITA has currently put in place,
but it also requires that the target modules' requirements should be ready before the
project begins.
• A load balancer can be used by SENYORITA's IT infrastructure to manage the data
volume indicated in the RFP in the production environment.

• The SENYORITA hardware supporting the Oracle application is expandable to handle

the extra load the suggested module would cause.

• This project does not include any operating system or application version upgrades.

• As stated in the job scope, only one location (Sana'a) will receive the deployment.

• Tongue:
Deployment of the system will include an English version. Each document and piece of
information that LIU prepares and presents will be

6 | Page Fall 2023-2024

Scope Control

The control of changes to the scope identified in this document will be managed through
the Change Control procedure defined later in the Project Management Plan, using
Change Request Forms to identify and manage changes, with client approval for any
changes that affect cost or schedules for the project.

7 | Page Fall 2023-2024

Approach
Project Methods
Project services go through an approval process by SENYORITA. Upon completion of
all deliverables according to the detailed list of deliverables, SENYORITA will be asked
to sign a Certificate of Acceptance as proof of successful completion of the project within
the defined scope.

Strategy
Our strategy is to implement SENIORITA’s requirements by using Oracle software
functionality.

Project Work Plan

Acceptance

Project services are subject to SENYORITA's approval process. SENYORITA will be

required to sign a Certificate of Acceptance as evidence of the project's successful
completion within the specified scope once all deliverables have been completed in
accordance with the comprehensive list of deliverables.

8 | Page Fall 2023-2024

Project Tasks, Deliverables, and Milestones

Planning Approach

Project Deliverables

Process Deliverables Document Doc Id Signoff

Needed
Project Start Up Project work plan YES WM.020 YES
Project management frame work YES BT.070 YES
Functional Prototype (FP) iteration NO N/A

Future process model (Requirement definition

YES RD.011.1 YES
document)

Inception Future enterprise structure YES TA.040 NO

Conduct functional prototype (FP) NO N/A YES
Functional design document YES AN.050 YES
Cutover strategy YES TS.020.1 YES
Gap document YES AN030.1 NO
Revised future process YES AN030.1 YES
Elaboration Updates gap document YES AN030.2 YES
Refine cutover strategy YES TS.020.2 YES
Construction Technical Design Document YES DS.080 NO
User manuals YES DS.070 YES
Prepare UAT Test Script YES TE.025 NO
Finalize Cut Over Strategy YES TS.020.3 YES
UAT Instance Installation by client NO N/A NO
Application Setup Documents YES DS.030 NO
Go Live (Acceptance Certificate) YES N/A YES
Production Post production support , Project Closure
YES N/A NO
document

9 | Page Fall 2023-2024

Control and Reporting

Risk and Issue Management

Change Control

Propose Changes

Monitor Changes

Status Monitoring and Reporting

Reviews

10 | Page Fall 2023-2024

Work Management

Communication Model
Meeting/ Activity Responsibility Suggested Frequency Purpose

Meeting Preparation

Meeting Structure
Proposed Meeting Opening items

Proposed Meeting Closure items

Workplan Control

11 | Page Fall 2023-2024

Resource Management

12 | Page Fall 2023-2024

Configuration Management

Deliverable Review and Acceptance

Document Sign-Off Process

LIU PM sends the documents required a sign-off from the Functional Lead and copy the Document
Controller in SENYORITA, the document

Process

Deliverable Acceptance Criteria

Refer to Appendix J

Document Naming Conventions

Convention Description Sample

Document_Title template file name as per framework Future_Process_Model
version

Document Storage File Structure

Directory Change Control

Drive and Base Directory

Project Subdirectory Structure

Level 1 - Phase Level
Level 2 – Work Package Level
Level 3 to N - Details Level

Project Directory Design

13 | Page Fall 2023-2024

-

14 | Page Fall 2023-2024

Quality Plan

Approach
Guiding Principles
The following key principles will be used to guide the SENYORITA:
QA is Time Well Spent:
Studies have shown that each hour spent on QA activities saves from 3 to 10 hours in downstream
costs. Activities such as Design Reviews eliminate defects that would need to be corrected later at
much higher cost.
Defect Prevention over:
A defect due to a bad requirement is 50 to 200 times more expensive to correct during build than if
it had been corrected in the requirements phase. The focus of the Quality Assurance thread will be
to prevent such defects from being introduced in the first place.
100% Defect-Free is not possible:
A common misconception is that all defects need to be resolved before a product is considered
complete. Due to the complexity of most development projects, it is nearly impossible to remove all
defects. It has been observed that the optimal point of defect removal is between 90-95%. This
represents the best trade-off between schedule and quality.
Build in Quality, Rather Test Bugs Out:
It is important to note that testing only uncovers the defects introduced in the earlier stages of the
development lifecycle. Testing by itself does not correct quality a problem, no more than stepping
on a scale makes you lose weight. Sufficient time will be spent to ensure high quality both in the
requirements and design before development even begins.
Quality is Everyone’s Responsibility
From Project Leadership providing sufficient resources to perform proper QA, to the individual
developer participating in Code Reviews, it is every team member’s responsibility to act in a way
that guarantees the quality of the end-product.

15 | Page Fall 2023-2024

Quality Overview, Client Expectations and Requirements

Quality Overview
LIU’s approach to developing and implementing the SENYORITA Project Quality Assurance Plan
will be one of constant review and revision, with the intent and commitment to continually
improve quality of implementation and processes throughout the LIU Project.

Scope
The scope of the Quality Plan document is to:
• Define the relevant roles for managing and supporting project and implementation quality
• Identify the activities that the project will perform to support the goal that the delivered solution
meets its intended business needs (i.e., activities that validate that the project team creates the right
solution)
• Identify the activities the project will perform to in a way such that the solution meets its agreed
requirements (i.e., activities that verify the solution meets its agreed requirements)
• Identify the project’s strategy for auditing project team compliance to the organizational set of
standards and processes

Roles and Responsibilities

16 | Page Fall 2023-2024

 Role Resource Responsibilities

17 | Page Fall 2023-2024

Quality Assurance Activities
Quality assurance activities will be centered on:
• Conformance to the Project Management Plan.
• Conformance to the Configuration Management Plan.
• Conformance to SENYORITA policies and procedures.
• Evaluation of general system designs.
• Evaluation and verification of Test Plans.
• Evaluation of in-line code documentation and other system related documentation.
• Use of Quality Assurance checklists and other validation techniques

Quality Techniques
Several Quality techniques will be used in this project. These techniques include:
1. Checklists
2. Peer Reviews (Client reviews)
3. Solution SME
4. Quality Reviews

Audit Approaches
1. Milestone Based
For this approach quality assurance audits are planned at the end of major milestones or
project phases, and focus on the activities that lead up to the milestone.
2. Deliverable Based
Following this approach quality assurance audits are performed upon completion of
major deliverables or work products. These audits focus on the deliverables and activities
for creating them.
3. Scheduled Following
This approach the quality assurance audits are based on a schedule and focus on auditing
all processes

18 | Page Fall 2023-2024

Non-Conformance Management / Escalation Procedures
Non-conformances identified during a quality review represent risk to the project and therefore
need to be documented, addressed, and tracked to closure. Once a review is complete the non-
compliances found are documented and shared with the project managers and team leads. It is the
responsibility of the project team to address the identified nonconformance, and it is the Project
Manager’s responsibility to monitor the non-conformance resolution, verify the closure of
corrective actions, escalate outstanding nonconformance, and escalate risks when necessary. Once
outstanding non-conformances are escalated they will be addressed during Follow up Committee
Meetings.

Escalation procedures
The following table outlines the escalation procedures the project will follow if nonconformance is
not being addressed in a timely manner.

Escalation Criteria
#
Escalation Path / Level Level of Risk Age of Non-Compliance

1 Escalate to the PM, High 1-5 days

Escalate to the Practice Head / Project
2 Low, Medium 6- 10 days
Director
Medium ,Hig
3 Escalate to Project sponsor >10Days
h

19 | Page Fall 2023-2024

Product QA Process Flowcharts
The Product (System Functional Deliverables) QA process is executed by the Domain Manager, SME and project team to assure the
compliance of the document formatting and content to the deliverable document criteria.

20 | Page Fall 2023-2024

LIU Quality Assurance Program (QA)

The LIU Quality process works to assure the compliance of the Project management objectives and customer satisfaction, and
works along the project as a project quality advisor and auditor.

Project management Quality Assurance Process (PMQ)

*Highlighted activities are QA activities

21 | Page Fall 2023-2024

Quality Assurance Audit Plan
The purpose of conducting quality audits is to verify that the processes and standards defined by the Project Plans are followed.
The following table outlines, at a high level, when each process area will be audited and which assets in the process area will be
part of the audit.

The Audits milestones could vary due to complexity of the project or client needs as per contract

Process to be Who
# Audited Work to be Audited When* Type of Audit
1

10

* Frequency may be adjusted during the project as required by project progress and quality of work product

Follow up Committee Meetings

At the inception of the Program, a Follow-up Committee will be formed to ensure project progress.
This committee will meet on a periodically basis (as per the communication plan)

22 | Page Fall 2023-2024

Project Planning
Project planning is also a critical component of the overall Quality Management Plan.
Project work plans will be developed based on the standard activities and deliverables outlined in
the project methodologies. Project management and team leads will develop the work plan and
must agree with the work estimates, timing, and responsibilities. The work plan will be regularly
updated and will reasonably reflect overall project status. Project status reports will be developed
regularly and will include dates, distribution list, accomplishments and planned activities, major
issues, and corrective steps for areas requiring action.

Quality Plan Review and Approval

The following principles will apply with regard approval review of the quality plan:

● The Quality Plan will be distributed to the customer Project management team for review and
comment.

● Updates from the review cycle will be incorporated and submitted for approval.

● The Quality Plan may also be reviewed and updated as a result of the status meetings.

● The Quality Plan will be reviewed and if needed, updated when transitioning between phases
of the project.

23 | Page Fall 2023-2024

Appendix A – Statement of Work
Refer to SOW

Document History

Date Version Author Comments

10-Aug-2015 1.8 Final Version

18-Aug-2015 2.0

24 | Page Fall 2023-2024

Appendix B – Workplan

25 | Page Fall 2023-2024

Appendix C – SENYORITA, LIU Project Team Contact Information

SENYORITA Project Team Contacts List

Name Role Tel-Ex Email

SENYORITA Management Team Contacts List

Name Role Mobile Email

Project Sponsor
Project Director
Project Manager

LIU Project Team Contacts List

Name Role Mobile Email

LIU Management Team Contacts List

Name Role Mobile Email

Ibrahim AlShutbi Project Manager Ibrahim.shutbi@LIe.com

26 | Page Fall 2023-2024

Appendix D – Key tasks and responsibility for data conversion.

Data Conversion
Team Roles (Who) Responsibility Deliverables
Stages
Extract SENYORITA Team SENYORITA Extracted Data in Text format (xls)
Transform
SENYORITA Team SENYORITA Cleansed data in xls format
(Cleanse)

Conversion Mapping Document with column

SENYORITA team /
Map SENYORITA mapping where required and any workarounds for
LIU Team
missing data in required columns.

Data Upload Programs (using SQL Loader)

Load LIU Team LIU
Data upload into Oracle Applications system

Reconcile SENYORITA Team SENYORITA Verify & Reconcile uploaded data with legacy system

27 | Page Fall 2023-2024

Appendix E – Deliverables
Process Deliverables Document Doc ID Signoff Needed
Project Start Up Project Work Plan Yes WM.020 Yes
Project Management Frame work Yes BT.070 Yes
Functional Prototype(FP) Iteration No N/A No

Future Process Model (Requirement

Inception Yes RD.011.1 Yes
Definition Document)

Future Enterprise Structure Yes TA.040 No

Conduct Functional Prototype (FP) No N/A Yes
Functional Design document* Yes AN.050 Yes
Cutover Strategy Yes TS.020.1 Yes
Gap Document Yes AN030.1 No
Revised Future Process ( With
Yes RD.011.2 Yes
Addendum)
Elaboration Update Gaps documents Yes AN.030.2 Yes
Refine Cutover Strategy Yes TS.020.2 Yes
Technical Design Document* Yes DS.080 No
User Manuals Yes D0.070 Yes
Construction Prepare UAT Test Script Yes TE.025 No
Finalize Cut Over Strategy Yes TS.020.3 Yes
UAT Instance Installation by client No N/A No
Application Setup Documents Yes DS.030 No
Go Live (Acceptance Certificate) Yes N/A Yes
Production Post production support , Project
Yes N/A Yes
Closure document

Note:

● Some of the above deliverables may be combined into one document deliverable

28 | Page Fall 2023-2024

Appendix F – Risk and Issue Log

PROJECT ISSUES LOG

Project Name: Babco
Project Manager: Ibrahim Alshutabi Today's date:
Basic Fields Status
Issue Issue Name Description / Background Raised By Date Status Date
ID Raised Closed
dd-
dd-mmm- mmm-yy
yy

PROJE
CT
ISSUE
S LOG
1 2
3 (High)
Project Name: (Low) (Medium)
Ibrahim Today's
1 (Low)
Project Manager: Alshutabi date:
2
(Medium)
3 (High)

Basic Fields Category Fields

Risk ID Ris Status Raised By Raise Action Impact
k Date Plan (ref) on
project
Impac Exposur activitie
Probability t e s

29 | Page Fall 2023-2024

Appendix G – Change Request Forms (CRF)
CHANGE REQUEST

Agreement no: Change Request no:

Title of Change Request:

Originator: Date:

Description of the requested change:

Reason for request:

Business case for request:

Include internal and external cost estimates

Signed (SENYORITA) :

Name

30 | Page Fall 2023-2024

Appendix H – Change Control Log

Change Control Log

*
Indica
Project Name: te:

Project Manager: High

Medi
um
** Proposed, *** Increase, **** Increase,
Authorized, Rejected, Decrease, No Decrease, No
Low Deferred Impact Impact
Impac
t
Reque Dat Cha Impa Analy
Cha Reque ster e nge ct sis
nge sted Phone Log Deta Level Impact on Impact on State
ID By # ged ils * CurrentStatus** budget*** schedule**** ment

31 | Page Fall 2023-2024

Appendix I – Project Status Report

Project Status Report for

Customer

Project
Customer Name name
Current
Prepared By Stage
From date To Date
Date of preparation

General Status

Milestones
Name of Planned Remarks
Srl No Status
milestone date
1
2
3

Deliverables
Name of Planned Remarks
Srl No Status
Deliverable date
1
2
3

Milestones planned for next

period
Name of
Srl No
milestone
1
2
3

Deliverables planned for

next period
Name of
Srl No
deliverable
1
2
3

Open Issues with customer

Srl No Issue Remarks
1
2
3

32 | Page Fall 2023-2024

Appendix J – Customer Acceptance Criteria
Process Deliverables Document Doc ID Signoff Acceptance Criteria
Needed
Project Start Up •Fit for purpose
•Includes the WBS and milestone
Dates for project
•Includes the tasks/work Plans for the
project and associated start, finish
dates and duration details
Project Work Plan Yes WM.020 Yes
•Highlights key dependencies
between tasks / work strSENYORITA
Includes resource allocation for each
task
•Sign-off the final plan by
SENYORITA project manager
•Should be fit for the purpose
•To be within the project Scope,
communication, Risk & Issue ,
Project Configuration management and
Management Frame Yes BT.070 Yes Quality plan
work •awareness session to be conducted
with SENYORITA project team
• Sign-off by SENYORITA project
manager
Functional Attendance sheet
Prototype(FP) No N/A No
Iteration
Inception
Future Process Refer to deliverable sign-off process
Model
(Requirement Yes RD.011.1 Yes
Definition
Document)
Future Enterprise A hardcopy of TA-40 will be issued
Yes TA.040 No
Structure and get sign-off
Conduct Functional
No N/A Yes
Prototype (FP)
Functional Design A hardcopy of AN-50 will be issued
Yes AN.050 Yes
document* and gets sign-off
A hardcopy of TS-020 will be issued
Cutover Strategy Yes TS.020.1 Yes and gets sign-off

Gap Document Yes AN030.1 No

Revised Future A hardcopy of RD-011.2 will be issued
Process ( With Yes RD.011.2 Yes and gets sign-off
Addendum)
Elaboration
A hardcopy of AN.030.2 will be issued
Update Gaps
Yes AN.030.2 Yes and submitted to Babco PM to take
documents
decision on the GAPS if any
Refine Cutover A hardcopy of TS-020.2 will be issued
Yes TS.020.2 Yes
Strategy and gets sign-off
Technical Design
Yes DS.080 No
Document*
Construction User Manuals Yes D0.070 Yes A hardcopy of D0.070 will be issued
and gets sign-off

33 | Page Fall 2023-2024

 Process Deliverables Document Doc ID Signoff Acceptance Criteria
Needed
Prepare UAT Test
Yes TE.025 No
Script
Finalize Cut Over A hardcopy of TS.020 will be issued
Yes TS.020.3 Yes
Strategy and gets sign-off
UAT Instance
Installation by No N/A No
client
Application Setup
Yes DS.030 No
Documents
Go Live A hardcopy of Acceptance Certificate
(Acceptance Yes N/A Yes will be issued and gets sign-off and
Certificate) stamped
Production Post production A hardcopy of project Closure
support , Project Yes N/A Yes Certificate issued and gets signed-off
Closure document and stamped

34 | Page Fall 2023-2024

Appendix K – UAT Sign-off Letter
UAT Sign-off

Project ID UAT Start date <dd-mon-yy>

Project Name UAT End date <dd-mon-yy>
Customer Name Date of Sign-off <dd-mon-yy>
Number of defects Number of changes
reported during UAT reported during UAT
Number of changes Number of changes
implemented during pending
UAT
Name of the Customer’s representative

Details of Team Involved in UAT

Name Role

Details of Deliverables
Name of the deliverable Delivered to Date of delivery
<dd-mon-yy>
<dd-mon-yy>
<dd-mon-yy>

Dear Sir,

This is to certify that the User Acceptance Test for <Project Name> has been successfully completed at
<location1, location2…. >.
We further certify that all the defects reported during UAT have been fixed and implemented at the
location(s) mentioned above.
Notes on Open Issues:

Customer’s Remarks:

Signature of LIU
Representative
Signature of the
Customer

35 | Page Fall 2023-2024

Appendix L – Go Live Certificate

SENYORITA Project Go-live Certificate

Client:

Project:

Initiated by: Date:

Milestone Reference: Type: ✔ Go Live

❑ Production System Handover

❑ Completed Support

❑ Completed Projects

❑ Other (Please specify)

Oracle Applications Implementation - Acceptance

Exclusions

The Oracle Applications Implementation (Service Sector wave) has been completed by LIU and the implementation is reviewed
by SENYORITA and fully meets the objectives expressed by SENYORITA and the system passes all acceptance criteria of
SENYORITA. The deliverable supporting the implementation is considered completed.
The project is deemed completed and closed with go-live and post production support is started

CLIENT Representative Date: _________________

LIU Representative: Date: _________________

36 | Page Fall 2023-2024

Appendix M – Project Closure Certificate

37 | Page Fall 2023-2024

Appendix N – Minute of the Meeting

38 | Page Fall 2023-2024

Appendix O – Detailed Deliverable List
Process Deliverables Doc Doc Sign File Name convention Who Will Sign-off the
ume ID off Document
nt Nee
ded
Project Work Plan 150101 WM EN SENYORITA
WM. ver2.0 Final
Start Up Project Work Plan Yes Yes project manager <
020
Mahmoud Dasht
Project Managment Plan SENYORITA
Project Management BT.0 150101 BT70 EN ver2.0 Final
Yes Yes project manager <
Frame work 70
Mahmoud Dasht
Functional Prototype(FP)
No N/A No
Iteration
---Future Process Model Respective
Inception Future Process Model
RD.0 150101 RD.011 EN ver2.0 Functional Lead
(Requirement Definition Yes Yes Final
11.1
Document)
---Future Enterprise SENYORITA
Future Enterprise TA.0 Structure 150101 TA.40 EN project manager <
Yes No ver2.0 Final
Structure 40 Mahmoud Dasht

Conduct Functional
No N/A Yes
Prototype (FP)
---Functional Design 150101 A hardcopy of AN-
Functional Design AN.0 AN.50 EN ver2.0 Final
Yes Yes 50 will be issued
document* 50
and gets sign-off
Cutover Strategy 150101 SENYORITA
TS.02 TS.020.1 EN ver2.0 Final
Cutover Strategy Yes Yes project manager <
0.1
Mahmoud Dasht
---Gap Document 150101
AN0 AN030.1 EN ver2.0 Final
Gap Document Yes No
30.1
---Revised Process Model A hardcopy of RD-
Revised Future Process RD.0 150101 RD.011.2 EN ver2.0 011.2 will be issued
Yes Yes Final
( With Addendum) 11.2 and gets sign-off
Elaborati
on
---Updated Gap Document A hardcopy of
150101 AN030.2 EN ver2.0 AN.030.2 will be
AN.0 Final issued and
Update Gaps documents Yes Yes
30.2 submitted to Babco
PM to take decision
on the GAPS if any
Revised Cutover Strategy A hardcopy of TS-
TS.02 150101 TS.020.1 EN ver2.0 020.2 will be issued
Refine Cutover Strategy Yes Yes Final
0.2 and gets sign-off

---Technical Design 150101

DS.08.1 EN ver2.0 Final
Technical Design DS.0
Yes No
Document* 80
Construct
ion
--- User Manual A hardcopy of
D0.0 150101 Do.70 EN D0.070 will be
User Manuals Yes Yes
70 ver2.0 Final issued and gets
sign-off
Prepare UAT Test Script Yes TE.0 No --- Test Scripts
25 150101 TE.025 EN
ver2.0 Final

39 | Page Fall 2023-2024

 Process Deliverables Doc Doc Sign File Name convention Who Will Sign-off the
ume ID off Document
nt Nee
ded
--- Cutover Strategy 150101 A hardcopy of
TS.02 TS.020.3 EN ver2.0 Final TS.020 will be
Finalize Cut Over Strategy Yes Yes
0.3 issued and gets
sign-off
UAT Instance Installation
No N/A No
by client
--- Application Setp 150101
Application Setup DS.0 DS.030 EN ver2.0 Final
Yes No
Documents 30

A hardcopy of
Acceptance
Go Live (Acceptance Certificate will be
Yes N/A Yes
Certificate) issued and gets
sign-off and
stamped
Productio A hardcopy of
n project Closure
Post production support ,
Yes N/A Yes Certificate issued
Project Closure document
and gets signed-off
and stamped

40 | Page Fall 2023-2024