Project Management Plan

Project Management Plan Process Area: Project Management Doc ref: I3/<Project Name>/PMP/01
<CUSTOMER/PROJECT> Applicable Process Doc: PROPJM01
PROJECT MANAGEMENT PLAN
ORACLE SSI
<CUSTOMER/PROJECT>
Author: <Author>
Creation Date: January 15 2013
Last Updated Date: <Date as per change record>
Document Ref: I3/<Project Name>/PMP/01
Version: <Draft 1A>
Approvals:
<Approver 1> Country Project Manager
<Approver 2> SSI PMO Manager/ Delivery Group Manager
File ref: <filename> Page 2

Company Confidential - For Internal Use Only
Document Control
Change Record
Date Author Version Change Reference
<Date> <Author> Draft 1A No previous document
Reviewers
Name Position
<PMO / DGM name> PMO Manager, Delivery Group Manager Oracle SSI
<QA name> Quality Analyst, Oracle SSI
<Oracle Country PM name> Oracle Country Project Manager
Distribution
Copy Name Location/Title

No.
1 Project Management Project Repository (SVN in GCDP/Beehive Workspace)

2 Project Manager Oracle Country
Note to Holders:
If you receive an electronic copy of this document and print it out, you should write your name on the front
cover (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).
Note to Author:
All instructions will be highlighted in green. On completion of the document, delete all highlighted portions of
the document including this section.
Content that needs to be updated is given in blue font. On completion of the document change the font color to
black.

Contents
Document Control....................................................................................................................3
Contents.....................................................................................................................................4
Introduction..............................................................................................................................5
Purpose...............................................................................................................................5
Engagement Summary.....................................................................................................5
Related Documents...........................................................................................................6
Objectives and Scope...............................................................................................................6
Project Objectives..............................................................................................................6
Scope...................................................................................................................................6
List of Tasks and Deliverables........................................................................................6
Key Dates & Milestones...................................................................................................6
Project Life Cycle...............................................................................................................7
Pre-requisites.....................................................................................................................7
Dependencies and Constraints.......................................................................................7
Work Environment...........................................................................................................7
Data Management.............................................................................................................8
Deliverables Acceptance..................................................................................................8
Project Organization and Governance..................................................................................9
Project Resource Management........................................................................................9
Project Organization Chart..............................................................................................9
Project Roles & Responsibilities......................................................................................9
Communication Plan......................................................................................................11
Project Governance Structure........................................................................................11
Engagement Satisfaction:...............................................................................................12
Project Monitoring, Control and Reporting.......................................................................12
Risk and Issue Management..........................................................................................12
Change Control Process.................................................................................................13
Status Monitoring and Reporting.................................................................................14
Quality Management Plan....................................................................................................14
Standards and Methodology.........................................................................................15
Quality Reviews..............................................................................................................15
Testing Procedure...........................................................................................................16
Decision Analysis and Resolution................................................................................16
Causal Analysis and Resolution...................................................................................16
Quality Assurance...........................................................................................................16
Configuration Management Plan........................................................................................17
Configuration Control....................................................................................................17
Release Management......................................................................................................17
Appendix A - Engagement Types........................................................................................18
Appendix B - Configurable Items list for the Project........................................................20

Introduction
Purpose
This document provides details on the approach/process applicable to the <development/implementation>
activities executed by Oracle SSI during the <Project name> project. This document is used
 To Establish the operational procedures for the project including customer specific management
requirements
 As basis for monitoring and controlling the project
SSI Project Manager is responsible for creation and maintenance of this document as part of Project planning
process with inputs from stakeholders.
The approval and mutual acceptance of this document by both SSI and country project managers, at the start of
the project will help in setting right expectations and controlling the project effectively.
Critical Success Factors

The critical success factors to meeting the objectives of this project are:
* Strong executive sponsorship and management support to the project team
* Adequate project staffing for the expected goals and timeline to be met.
* Timely feedback on documents while they are circulated in the draft mode to minimize time for
formal signoff.
* Timely decision making and signoffs.
* Involvement of key users from all stakeholder parties wherever required
* Clear roles and responsibilities defined between various teams.
* Clear and timely communication between the teams.
* A committed and well-informed project manager and project team having a thorough
understanding of the project goals and milestones
* A comprehensive project work-plan and Project Management Plan
* A defined and maintained project infrastructure throughout the project duration
* A focus on quality and efficiency
* A thorough understanding of known project risks and assumptions throughout the executive
committee and project teams.
* Willingness of the users to accept new ideas and ways of functionality. Users need to make efforts
to reduce / minimize custom extensions to the applications.
* Proactive working by the project teams.
* A thorough understanding of the final Business Solution by the teams.
Engagement Summary
This key objectives of this engagement is available in the proposal attached below
<Insert the latest approved proposal document (Mandatory to insert, reference is not acceptable)>
< For projects with no proposal, include Pricing/Estimate details here, >
The engagement type of the project is <Fixed price /Time and Material>

Description of Engagement type and related engagement rules are available in Appendix A
Related Documents
List the documents related to this engagement.
Reference Document Name Dated Author

ICC/PO / CLA <ICCPO_FileName.xls> <DD-MON-YYYY> <Name of the person who
generated the ICCPO>
Proposal <Proposal_Ver.doc> <DD-MON-YYYY> <Bid Owner who wrote the
Proposal>
Objectives and Scope
Project Objectives
< Mention the objective of the project >
The objectives of the project are to:
 <Objective 1>
 <Objective 2>
Scope
The project scope has been defined during the project presales phase in the proposal document. The control of
changes to the scope identified in proposal will be managed through the Change Control procedure defined in
the Control and Reporting Section of the this document.
< Copy scope section from proposal here. Any scope ageed over and above proposal scope should be added here
>
List of Tasks and Deliverables

< List the tasks and Deliverables as agreed and applicable at project start. List of Deliverables will differ based on
projects for e.g. Custom Development, Interfaces and Conversions, Upgrades, E2E, Fusion, BIApps, Integration.
Important: Actual Deliverables/CIs to be clearly mentioned here>
Task Deliverable Responsibility
Key Dates & Milestones

<The key project milestones and their respective target months/date are summarized below>
Sl. no. Milestone Deliverables / Events Month / Date

Sl. no. Milestone Deliverables / Events Month / Date
The Project Manager identifies other related and dependent plans and schedules related to the project. The
project activities will be tracked using a Project Schedule created in alignment with such documents.
Project Life Cycle

< Mention the delivery framework to be used for the project, if delivery framework is not available, mention the
project life cycle phases below >
Pre-requisites
Following are identified to be the pre-requisites for this project:
Connectivity to the development/test environment used by the SSI project team, with the required access and
software installed on these servers.
<Add any other project specific Pre-Requisites, or refer to the Proposal>
Dependencies and Constraints

<Copy relevant content from proposal >
Work Environment
Projects work environment is set based on the organization’s work environment standards.
<Mention Work locations>
Software/technology used
Hardware platform/ configuration
Environment type Owned by Access requirement for Access Method

SSI team
<Development> <SSI/OD/Customer> <VPN/ OCCN>
<Test> <SSI/OD/Customer> <VPN/ OCCN>
< Also include DBA, backup strategy, language translation needs, setups, data volumes etc as applicable >
Data Management
This section details for managing critical data from both customer and Oracle end. Access to such data will be
restricted and controlled based on contractual requirements and SSI QMS guidelines on Configuration
Management and record maintenance.
Non Disclosure Agreement required: <Yes / No>
<If Yes, specify requirements>
Project deliverables including code units and other Project related documentation will be maintained under
appropriate level of configuration management. Refer to Configuration Management section of this document
and Appendix B for list of identified configuration items
<Please update the table as per project requirements>
Sl Data Content and Format Privacy and Security Requirements

No.
1. <Test data> <Specify – Data dump / data <Specify For example, encrypted,
file> accessible only to project team etc>
2. <Development / Test / <Specify - Electronic content in <Specify, for example restricted to
Production> Environment remote servers> team members through VPN
Access Requirements tokens / login credentials>
3. Project metrics data Delivery Tracking System Accessible to SSI Project Manager,
Sponsor, PMO and QA
4. Specify, Customer <Specify - For example code <Specify>
supplied components, if units received for upgrade>
any
5. <Add any other managed
data>
Deliverables Acceptance
The deliverables of <Project Name> will go through acceptance by <Company Long Name> as and when they are
delivered. Also a formal Acceptance will be required within < number of days > of final delivery. The procedure
to be used for this is as follows:
* Environment: In terms of setup and patch levels, the acceptance-testing environment will be
the same as the one provided to Oracle SSI for development.
* Test results: Testing will be performed as per business/test scenarios provided to Oracle SSI and
demonstration of expected results and compliance with specification will be treated as
acceptance. In case of conflict in expected results and specification, then change management
process to be followed.
At the end of the planned timeframe for Acceptance Testing, if no issues or bugs are pending resolution against
a delivered pack or developed unit, Oracle SSI will be given acceptance. In the event of issues or acceptance not
being formally communicated, the deliverable will be deemed as accepted.
<Acceptance is applicable to Fixed Price engagement. For Time and Material the acceptance testing time frame
to be planned in advance to plan for the resource requirement to support testing and the same to be mentioned
in this section>
Delivery Notes
Contractual deliverables will be delivered formally and release packs with multiple object/files will be delivered
with an accompanying Release Note, stating the contents of the release pack.

Project Organization and Governance

Project Resource Management
The human resource requirements will be identified during the project preslaes. Project Manager will revalidate
and finalize the resource requirements in the project initiation stage. The project team assignments and changes
to assignments will be done in Resource Management system
Project Organization Chart
Project Roles & Responsibilities

The following table details the major roles and responsibilities of the project organization. Detailed description
of roles and responsibilities are available as part of proposal and relevant process descriptions (SSI roles):
Oracle Role Responsibility
Project Manager Project Planning, Monitoring and control

Scope control and project commercials
Communication and stakeholder management
Status reporting and project performance analysis
People Management and team member feedback
Initiate and conduct decision analysis meetings as required and implement
decisions
Configuration controller for the project having responsibility of creation and or
implementation of project repository and access control
Responsible to ensure all required configurable items are placed in the
repository in a timely manner
Solution Owner Solution Architecture
Deliverable reviews
Guidance and support to project team
Functional Consultant Requirement analysis and clarifications
Functional guidance to team members
Test case preparation and reviews
Functionality Testing

Oracle Role Responsibility
Technical Lead Requirement analysis and clarifications

Approach review
Design and development
Deliverable reviews
Guidance and support to team members
Contribute to defect analysis and corrective actions
Technical Consultant Design and development
Unit Testing and Deliverable reviews
Quality Champion Finalize Quality Control approach – set project standards, naming conventions,
versioning standard and checklists
Assist project manager in planning review and testing for the project
Assess effectiveness of QC activities and plan and conduct QC audits
Coordinate defect analysis and corrective actions
<Add other roles, as

appropriate>
Stakeholder Role Responsibility
Oracle Country Project Provide inputs to as specified in proposal - requirement documentation and
Manager / Customer clarification
Project infrastructure provisioning
Timely acceptance of deliverables
Timely sign-off of commercials (payment cross-charges, timesheets (if
applicable), contract extensions, change requests)
Attend progress reviews and resolve issues
Project Sponsor Executive Sponsorship and Management support
Participate in Project Governance calls
Address issues and project escalations from Group Delivery Managers and other
stakeholders
Delivery Group Manager Provide resources
Participate in kick-off meeting
Review Project Management related documentation
Review the project progress, risks and issues, Review Change requests
Participate in Project Governance calls
Address issues and project escalations from Project Manager and other
stakeholders
PMO Participate in kick-off meeting
Review the project progress, risks and issues, Review Change requests
QA Representative Participate in the kick off meeting
Assist Project Manager to tailor processes and approve process exemptions
Participate in the project progress reviews
Perform project compliance checks and Configuration Audits
Provide process orientation to team and share lessons / best practices
Collect metrics
Delivery Back Office Back office support – Project Setup, Transaction Controls, Follow up on cross
charges
ESM collection
Solution Center Support for Infrastructure, networking related issues

Communication Plan
Contact Information
Name Project Role Email ID Phone Number(s)

Meeting
Schedule
OSSI
Meeting Name Purpose Schedule Attendees
Internal Project Progress Review project progress, Project Manager, PMO /

Fr> Project
Review
Oracle <Country> risks, issues, performance Delivery Group
data Manager, QA, <Add as
appropriate>
Project Progress Review Review project status, risks, Project Manager, Oracle
<y>
with country Oracle issues, project commercials Country Project Governance
Manager, <Add as Structure
appropriate>
Oracle
Governance Call <List attendees>
SSI
<Add>
follows a Governance model wherein communication takes place at 3 different levels between Oracle SSI and
Oracle Country.
Governance Plan
Governance Calls are planned calls between Oracle SSI Stakeholders and Oracle Country/Customer
Stakeholders. These calls can be done monthly or upon achieving a project milestone.
Escalation Matrix
 Level 1 Escalation: First level escalation to be done when the issues / problems have not been resolved by
the functional or technical lead / project team or issues or defects which were repeated again and again.
 Level 2 Escalation: Second level escalation to be done when the issues / problem have not been resolved
by the Project Manager.
 Level 3 Escalation: Third level escalation to be done when the issue / problem has not been resolved after
the second level of escalation
Escalation Point Suggested Country SSI Contact / Email ID Contact Numbers Additional
Contact Information
Level 1 <Country Contact> <SSI Project Manager> <Contact no.>

Level 2 <Country Contact> <SSI Group Delivery Manager> <Contact no.>
Level 3 <Country Contact> <SSI Group Head> <Contact no.>
Engagement Satisfaction:
During the course of the project, Oracle SSI Project Manager or Oracle SSI PMO/QA team representative will
request for intermediate feedback from Oracle <Country> Project Manager. At the end of the project, final
feedback ratings will be collected from Oracle <Country> project manager.

Project Monitoring, Control and Reporting

The Project Monitoring, Control and Reporting process ensures the progress of the project in accordance with
the plan and achievement of project objectives. The project schedule is updated to reflect the status of project
activities. The project performance measures and metrics are collected and analyzed by Project Manager and
team. This process reports progress status externally and internally to stakeholders. Project Manager reviews
project progress information and initiate appropriate actions to address deviations from the plan. . The
monitoring, control and reporting process include:
 Risk and Issue Management
 Problem Management
 Change Control
 Status Monitoring and Reporting
Risk and Issue Management
Risk and Issue Management Approach

The approach for managing project risks and issues is as follows:
 Identifying and logging issues and risks
 Prioritizing issues and risks
 Assigning issues to person(s) responsible for owning resolution and for performing impact analysis as
required
 Tracking and reporting issues and risks status Escalating issues including how long the issue stays at one
level before it is escalated to the next level of Project Governance structure.
The intended result is a minimal backlog of unresolved issues, thus providing the lowest practical impact to the
project.
The following risks have been identified that may affect the project during its progression. If the risks are not
mitigated with active support from all concerned parties, then it may adversely affect the project in terms of
cost, schedule or the quality of deliverables.
Risk Risk Description Risk Category Risk Impact

No.
<Note: List the external risks that are to be shared with the country / customer PM. Both internal and external
risks should be captured in RAW>
Problem Management
Record Issue Details
 The technical issues related to project are recorded in Project Issue Log.
 The offshore Oracle SSI development team will take up the issues recorded, as above, for resolution.
Issue Resolution

 Oracle SSI lead will investigate the issue and assign the issue to team members for further investigation
and the team lead/member will update Project Issue Log with the resolution information or request for
more information/clarification.
 Oracle country then verifies the resolution to the issue and accepts the resolution.
 Status of Issues will be reviewed at progress meetings with Oracle country Project Manager.
Change Control Process
Change control management

The following section describes the situations that bring change control into effect and how the changes are
processed.
 Change identification/qualification: Change requests could be due to (but not limited to):
 Additions/changes to tasks and deliverables listed in tasks & deliverables section of proposal.
 Changes to complexity of the objects in scope from that mentioned in the proposal
 Changes to objects or programs due to change in functional setups
 Wait time incurred due to but not limited to system down time, delay in providing clarifications, delay
by customer in providing approved input documents, non-availability of users to test the delivered
object etc
 Issue raised as defect by country/customer, but upon analysis and classification is a change for SSI
 Change to the approach or technology used from that described in the proposal.
 Changes to program to handle problems detected during testing that are related to data (cleanliness),
design being not appropriate to data or database.
 Post delivery support beyond what has been presented in this document/proposal.
 Non-availability of environment.
 Change Impact: The impact is analyzed and shared with the Oracle Country Project Manager. It could be
in terms of cost, effort and/or schedule.
 Change Communication: Oracle SSI Project Manager will prepare a change request form with details of the
change and its impact on the project. Oracle SSI Project Manager will seek approval for the Change
Request from Oracle Country project manager. A copy of the same will be uploaded to <SVN in GCDP/
Beehive Workspace>.
 Change approval: The Oracle Country Project Manager needs to approve the changes in scope, schedule,
effort and commercials before the work commences. The approval can be provided in terms of formal
‘Change Request’ or ‘Approval to spend additional effort’.
Status Monitoring and Reporting

The Status Monitoring and Reporting Procedure define how the project will collect, assess, report and act on
information about the progress of the engagement. During this engagement progress will be assessed and
documented via the following progress reports and meetings.
Project Progress Reporting

 On a <weekly basis/agreed frequency> <Agreed Frequency to be mentioned explicitly in this PMP> the Oracle
SSI project manager prepares a Status Report and sends it to the Oracle Country Project Manager. The PPR
will communicate details such as weekly progress and planned work, risks, issues etc.
 The Oracle SSI Project Manager and key team members from Oracle SSI will have <weekly basis/agreed
frequency> <Agreed Frequency to be mentioned explicitly in this PMP> conference calls to review the Project
progress with Oracle Country Project Manager and team.
 Minutes of all meetings held between Oracle SSI and Oracle Country Project Manager would be recorded. The
minutes state the issue, actions to be taken, by whom and by when. The actions will be reviewed during
subsequent meetings.

 Internal PPR with the PMO/GDM, QA will be conducted <weekly/fortnightly/monthly> <retain only the
relevant frequency> and Minutes will be recorded. The frequency of the PPR could be changed and such
changes will be reflected in the PMP.
Quality Management Plan

This section defines how the quality of the project processes is to be determined (process reviews) and how the
quality of the deliverables produced during the project is to be determined (reviews). This section also defines
how deliverables will be physically assessed for functionality (testing), and what measurements will be collected
during the project.
< List the Quality Control Approach identified for the project. This section to be filled in by the Lead/Quality
Champion` identified for the project>
Standards and Methodology

The following standards are to be used during this engagement:
 Documentation Standards - as defined in <state the title and document reference of the standards
document>
 Technical Standards - <list each standard e.g., Analysis Standards, Design Standards, etc. and state the
title and document reference of the standards documents>
 Naming conventions will be followed as defined in <state the title and document reference of the
standards document>
 Agree on the Tools, Technology, Checklists, Re-usables, and Best Practices as applicable for the particular
service. <Give the details here on Tools/Technology/Re-usables/Best Practices/pointers to where we can
find Checklists>
Quality Reviews
The below review approaches will be followed to ensure quality of deliverables
 Peer Review: Reviews will be carried out for each deliverable (documentation and software) by
walkthrough or inspection. A record of all comments found during deliverable reviews will be kept both
as evidence of review and in order to check resolution of actions.
 Health Checks: If the project warrants, then a SME who is outside the Project Team will conduct Health
Check and follow-up on actions to closure. <Add frequency / milestones when Health checks will be
conducted. PM / Lead to decide this at the start of the project and document it in the PMP>
During this engagement, the following reviews / assessments will be conducted:

<Note: Change the list based on the engagement / project / proposal /etc. .>
Deliverable / task Review performed by Remarks

Functional design Solution owner / Functional lead
/Quality Champion
Solution approach Solution owner
Technical design Solution owner / Technical lead/Quality
Champion
Code walkthrough/ Technical lead/Quality Champion
review

Unit test scripts Technical Lead / Functional Lead/Quality

Champion
System test scripts Technical Lead / Functional Lead/Quality
Champion
Technical unit tests Technical consultant/Quality Champion
Test & Instance Strategy Solution owner / Functional lead/Quality
Champion
Test Plan and Solution owner / Functional lead /
Performance Testing Plan Technical Lead/Quality Champion
Functional tests Functional consultant/Quality Champion
Installation tests Technical consultant / Technical lead
/Quality Champion
Release Verification QA Representative
Testing Procedure
The procedure to be followed for testing requires that a test specification (also referred to as a test plan) is
produced prior to conducting any testing, which specifies the test steps to be conducted and the data to be
used. On completion of testing actual test results will be documented to show the results of each test step.
Defects identified in testing will be fixed by the developer and re-tested. Internal defects raised will be
tracked in the review comments log (RCL) and customer reported defects will be tracked in the project issue
log
Testing Testing performed by Remarks
Peer Testing Technical lead/Quality Champion
System testing Technical lead/Quality Champion/

Functional consultant
Integration testing Technical lead/Quality Champion/

Functional consultant
UAT Customer/ 3rd party
Decision Analysis and Resolution
Decision Analysis and Resolution will be used for decision making /resolving conflicts during the project
execution. It could be used for the approach meeting for deciding the design approach either for each
object/module or for the project, wherever multiple alternatives exist.
DAR could be applied on the following areas, Align contents properly.
<List areas where project team will be applying DAR :
 Add / release / change of critical resources (people /hardware)
 Solution Approach selection
 Make – reuse analysis
 Prioritization of objects/Deliverables
 Specific training requirements>
 Project Management decisions

 Add if required
Causal Analysis and Resolution

Causal Analysis and Resolution will be applied for
 Identifying and analyzing causes of defects and other problems / issues.
 Taking specific actions to remove the causes and prevent the re-occurrence of those types of defects and
problems / issues in the future.
 <Add if required>
Quality Assurance
QA Representative will perform fortnightly Process Compliance reviews. The project also will be audited as part
of the Internal Audit process by trained auditors. Project Manager analyzes the reported deviations and initiates
corrective actions.
Configuration Management Plan

This process contains the tasks that will store, organize, track, and control all items produced by and delivered
by the project. The Configuration Management process also calls for the provision of a single location from
which all project deliverables are released.
Configuration Control
A list of Configuration items are identified by the Project Manager in consultation with Leads and team
members. Please refer to the Annexure for the list of master CI`s
<If there is need for capturing more details modify the section or create separate document for capturing the
details>
Configuration Control will be exercised as per Oracle SSI QMS guidelines and requirements specified by
customer, if any.
Configuration Management Tool: <SVN in GCDP / Beehive workspace / Customer specified tool>l
<In case multiple repositories are used please mention all repositories and what documents will be placed
within the respective repositories>
A change record will be maintained for documents and program units and base lining will be followed as per
Configuration Management guidelines under SSI QMS.
Configuration Baseline audits are planned as part of Release Verification and Internal Quality Audits.
< It would need more details if customer wants to participate in code changes at any point of time, e.g. during
release or support, customers may want to take care of some changes themselves and bug fixes by offshore,
where code configuration management becomes all the more important. Process needs to be elaborated>
Release Management
All releases will be sent to the QA for release verification prior to release to customer. Customer releases will be
created using baselined components placed in the configuration management tool.
Deliverable / task Release mechanism Remarks

Documents <File Upload / eMail>

Program Units / Release pack <File Upload / eMail>

Upgraded / Configured Environment URL shared through email.
environments
Customer/Country point of contacts will be notified about the release and such emails will be stored in the
configuration management tool as part of project documentation.

Appendix A - Engagement Types

1. Fixed Price
Fixed price contract involves a fixed total price for a well-defined scope.
Defining an exact scope in the proposal is essential to the preparation of a contract for FP services and the
successful delivery of those services. By doing this, clear expectation is set with customers.
It is assumed that greater risk is with Oracle SSI in the fixed price engagement.
Rules of the Engagement

Generic
o Project objectives must be clearly defined.
o Roles and responsibilities must be clearly defined to achieve timely decision-making.
Environment
o Set-ups must be frozen before the start of related offshore development. Any setup changes after
start of development are to be reported to Oracle SSI.
o The development instance must have appropriate volume of data, which is essential for
performing effective unit testing.
Project Planning & Management
o In order to enable effective offshore planning, ensure the following:
 Provide confirmed list of objects / clearly established scope prior to the start of offshore
work to enable effective planning.
 Prioritization of objects for development
 Provide Oracle SSI with confirmed dates for releasing the functional design / conversion
mapping documents and the business test case scenarios documents to offshore
o Provide visibility of the overall country Oracle/customer project plan to Oracle SSI
o Detailed offshore project plan should be in place to plan for onsite/offshore resources to avoid
delays in reviews/setups/clarifications/testing, etc.
o Close interaction among various groups involved with the project is key for success of a project. It is
important that all agreed timeframes with respect to decisions, approvals and clarifications are
adhered to.
o During the course of the project, for any additional scope a minimum of 4 weeks advance visibility
should be provided for resource planning.
Functional Design & Testing Documents
o Only approved/signed-off functional design documents and/or conversion mapping documents
should be used for offshore development. The functional design documents and/or the conversion
mapping documents should be detailed enough to minimize the clarification cycle.
o The functional design documents and/or the conversion mapping documents should contain clear
references to the actual setups (for e.g., name of a DFF to be explicitly mentioned). This is essential
to avoid re-work.
o The business/system test case scenarios documents should be comprehensive and reflective of all
requirements specified in the functional design/conversion mapping documents. The
business/system test case scenarios document would be used as the basis of acceptance for
offshore deliverables.
Acceptance - Time lines and criteria
o Adhere to the agreed acceptance testing time frame.
o Any setup changes to Development and testing environment should be done in a controlled
manner.
o All scenarios provided in the unit test case/business/system test case scenarios document should
be used for acceptance testing by onsite.

2. Time and Material

Full scope of the project is not defined at the contract stage. Thus the contract value grows along the course of
the project.
It is assumed that greater risk is with Oracle Country in the T & M engagement.
Rules of the Engagement

Generic
o Project objectives must be clearly defined.
o Roles and responsibilities must be clearly defined to achieve timely decision-making.
Environment
o Set-ups must be frozen before the start of related offshore development. Any setup changes
after start of development are to be reported to Oracle SSI.
o The development instance must have appropriate volume of data, which is essential for
performing effective unit testing.
Project Planning & Management
o In order to enable effective offshore planning, Oracle country to provide the following:
 Required team size and skill sets or list of objects to be developed.
 Based on the list SSI will arrange the team to start the development.
o During the course of the project, for any additional scope a minimum of 4 weeks advance visibility
should be provided for resource planning.
o Provide visibility of overall project plan to Oracle SSI
o Detailed offshore project plan should be in place to plan for onsite/offshore resources to avoid
delays in reviews/setups/clarifications/testing, etc.
o Close interaction among various groups involved with the project is key for success of a project. It is
important that all agreed timeframes with respect to decisions, approvals and clarifications are
adhered to.
Functional Design & Testing Documents
o Only approved functional design documents and/or conversion mapping documents should be
used for offshore development. The functional design documents and/or the conversion mapping
documents should be detailed enough to minimize the clarification cycle.
o The functional design documents and/or the conversion mapping documents should contain clear
references to the actual setups (for e.g., name of a DFF to be explicitly mentioned). This is essential
to avoid re-work.
o The business/system test case scenarios documents should be comprehensive and reflective of all
requirements specified in the functional design/conversion mapping documents. The
business/system test case scenarios document would be used as the basis of acceptance for
offshore deliverables.
Testing Assistance
o Offshore assistance must be planned well in advance to support System, Integration and User
acceptance testing.
The resources will be planned and allocated to the project based on the timeline given by Oracle Country and
this must be planned at least 4 weeks in advance.

Appendix B - Configurable Items list for the Project.

Please note that Delivery Manager should modify the naming convention wherever customer standards are
followed. A reference can also be provided to the applicable naming standards.
Deliverables to be maintained for development projects:
Type CI
Deliverable (doc/code) Control Description Naming Convention
Proposal Document Managed Latest Proposal ProjectPrefix_Proposal.doc
Estimation Document Managed Estimation sheet ProjectPrefix_Estimation.xslx
Inter-Company Cross
ICCPO Document Managed ProjectPrefix_ICCPO.xslx
Purchase Order
CR Document Managed Change request forms ProjectPrefix_CR_Number.doc
Project Management
PMP Document Managed ProjectPrefix_PMP_<Ver>.doc
Plan
Risk Assessment
RAW Document Managed ProjectPrefix_RAW.xslx
Workbook
Decision Analysis and
DAR Sheet Document Managed ProjectPrefix_DAR_<Scenario>.xlsx
Resolution
Causal Analysis and
CAR Sheet Document Managed ProjectPrefix_CAR_<Scenario>.xlsx
Resolution
Deviation
Document Managed Deviation tracker ProjectPrefix_Deviation tracker.xlsx
tracker
RCLs Document Managed Review Comment Log ProjectPrefix_RCL_<ObjectName>.doc
Status
Document Managed Weekly Status Reports ProjectPrefix_StatusReport_WeekEnding.doc
Reports
Metrics Document Managed Project Metrics sheet ProjectPrefix_Metrics Sheet_<Month>.xslx
QC Checklist Document Managed Quality Control Checklist ProjectPrefix_QC.xslx
Project Issue
Document Managed Project Issue Log ProjectPrefix_Issue log.xslx
Log
Minutes of Meeting
MOMs Document Managed ProjectPrefix_MOM.xslx
(internal and external)
Project Project Schedule (mspp /
Document Managed ProjectPrefix_Project Schedule.xslx / mpp
Schedule xlsx)
SQA
Document Managed SQA Checklist ProjectPrefix_SQA verification checklist.xslx
Checklist
Mandatory emails such
as ICCPO / WAR
Approval, Customer
release mails, CR
Mandatory
Document Managed Approvals (internal / ProjectPrefix_emailtype_date.msg
Emails
external), Customer
review comments,
(Communication/
Incoming/Outgoing)
<Please add any other documents/ deliverables that are being maintained under configuration management in your project>
e-Apps –Conversion
Type CI Control
Deliverable (doc/code) Description Naming Convention
Managed
and ProjectPrefix_<Object id>_<
CV.027 / CV.40 Document Controlled Conversion Data Mapping CV.027/ CV.040>.doc

Managed
CV.040 / CV.060 Document Controlled Conversion technical design CV.040/ CV.060>.doc
Managed
CV.050 / TE020 Document Controlled Test case document CV.050/ TE.020>.doc
Managed
IM.090 / MD.120 Document Controlled Installation Document IM.090/ MD.120>.doc
Managed
and
SQL / PL SQL Code Controlled Conversion Programs < >
<Please add any other project deliverables that should be maintained under configuration management and define the
naming conventions of those deliverables during the start of the project>
e-Apps - Interfaces / Customizations
Type
Deliverable CI Control Description Naming Convention
(doc/code)
Managed and Functional design ProjectPrefix_<Object id>_< AN.100/
AN.100 / MD050 Document Controlled document MD.050>.doc
Managed and Technical design ProjectPrefix_<Object id>_<DS.140 /
DS.140 / MD070 Document Controlled Document MD070>.doc
Managed and ProjectPrefix_<Object
TE.020 Document Controlled Test case document id>_<TE.020>.doc
Managed and ProjectPrefix_<Object id>_<IM.090 /
IM.090 / MD.120 Document Controlled Installation Document MD.120>.doc
Managed and
SQL / PL SQL Code Controlled Code Units < >
Managed and
Ldt Code Controlled Code Units < >
Managed and
Form Code Controlled Code Units < >
Managed and
Report files Code Controlled Code Units < >
Shell / Pearl Managed and
Scripts Code Controlled Code Units < >
Work Flow Managed and
Scripts Code Controlled Code Units < >
Customizations/ Technical Upgrade
Type
Deliverable CI Control Description Naming Convention
(doc/code)
Custom Upgrade Managed and Custom Upgrade
change doc Document Controlled change doc ProjectPrefix_Cust_upgrade.doc
Managed and ProjectPrefix_<Object id>_<IM.090 /
IM.090 / MD.120 Document Controlled Installation Document MD.120>.doc
Managed and
Form Code Controlled Code Units < >
Managed and
Shell / Pearl Scripts Code Controlled Code Units < >
Report files Code Managed and Code Units < >
Controlled
Managed and
SQL / PL SQL Code Controlled Code Units < >
Managed and ProjectPrefix_<Object id>_<Test
Test Cases Document Controlled Test Cases cases>
PeopleSoft Customization
Type CI Control
Managed and ProjectPrefix_<Object id>_<
AN.100 / FDD Document Controlled Functional design document AN.100/ FDD>.doc
DS.140 / TDD Document Controlled Technical design Document id>_<DS.140 / MD070>.doc
Managed and Technical design Overview ProjectPrefix_<Object
TDO/TDSP Document Controlled /Config Setup document id>_<TDO/TDSP>.doc
TE.020 / TDUT Document Controlled Test case document id>_<TE.020 / TDUT>.doc
Managed and
SQR Code Controlled Code Units < >
Managed and
nVision Code Controlled Code Units < >
Managed and
Crystal Reports Code Controlled Code Units < >
Managed and
COBOL Code Controlled Code Units < >
Managed and
Project dump Code Controlled Code Units < >
Retail /Siebel/ Hyperion Customization
Type CI Control
Managed and Functional design ProjectPrefix_<Object id>_< AN.100/
AN.100 / FDD Document Controlled document FDD>.doc
Managed and Technical design ProjectPrefix_<Object id>_<DS.140 /
DS.140 / TDD Document Controlled Document MD070>.doc
Managed and Technical design
TDO Document Controlled Overview ProjectPrefix_<Object id>_<TDO>.doc
Managed and
TDSP Document Controlled Setup document ProjectPrefix_<Object id>_<TDSP>.doc
Managed and ProjectPrefix_<Object id>_<TE.020 /
TE.020 / TDUT Document Controlled Test case document TDUT>.doc
Managed and
Code Code Controlled Code Units < >


Project Management Plan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Management Plan

Uploaded by

Copyright:

Available Formats

Project Management Plan Process Area: Project Management Doc ref: I3/<Project Name>/PMP/01

<CUSTOMER/PROJECT> Applicable Process Doc: PROPJM01

PROJECT MANAGEMENT PLAN

<Approver 1> Country Project Manager

<Approver 2> SSI PMO Manager/ Delivery Group Manager

File ref: <filename> Page 2

<Date> <Author> Draft 1A No previous document

Copy Name Location/Title

1 Project Management Project Repository (SVN in GCDP/Beehive Workspace)

File ref: <filename> Page 3

File ref: <filename> Page 4

Critical Success Factors

File ref: <filename> Page 5

Reference Document Name Dated Author

Objectives and Scope

List of Tasks and Deliverables

Task Deliverable Responsibility

Key Dates & Milestones

Sl. no. Milestone Deliverables / Events Month / Date

File ref: <filename> Page 6

Sl. no. Milestone Deliverables / Events Month / Date

Project Life Cycle

Dependencies and Constraints

Hardware platform/ configuration

Environment type Owned by Access requirement for Access Method

<Development> <SSI/OD/Customer> <VPN/ OCCN>

<Test> <SSI/OD/Customer> <VPN/ OCCN>

Sl Data Content and Format Privacy and Security Requirements

File ref: <filename> Page 8

Project Organization and Governance

Project Organization Chart

Project Roles & Responsibilities

Oracle Role Responsibility

Project Manager Project Planning, Monitoring and control

File ref: <filename> Page 9

Oracle Role Responsibility

Technical Lead Requirement analysis and clarifications

<Add other roles, as

Stakeholder Role Responsibility

File ref: <filename> Page 10

Name Project Role Email ID Phone Number(s)

Meeting Name Purpose Schedule Attendees

Internal Project Progress Review project progress, Project Manager, PMO /

Level 1 <Country Contact> <SSI Project Manager> <Contact no.>

File ref: <filename> Page 11

Project Monitoring, Control and Reporting

Risk and Issue Management

Risk and Issue Management Approach

Risk Risk Description Risk Category Risk Impact

File ref: <filename> Page 12

Change Control Process

Change control management

Status Monitoring and Reporting

Project Progress Reporting

File ref: <filename> Page 13

Quality Management Plan

Standards and Methodology

During this engagement, the following reviews / assessments will be conducted:

Deliverable / task Review performed by Remarks

File ref: <filename> Page 14

Unit test scripts Technical Lead / Functional Lead/Quality

Testing Testing performed by Remarks

Peer Testing Technical lead/Quality Champion