2. Project Management Plan
<Company Name>
<Project Name>
This is a Title Slide with Picture slide ideal for including a picture with a brief title, subtitle and presenter information.
To customize this slide with your own picture:
Right-click the slide area and choose Format Background from the pop-up menu. From the Fill menu, click Picture and texture fill. Under Insert from: click File. Locate your new picture and click Insert.
Presenter’s Name
Presenter’s Title
Organization, Division or Business Unit
Month 00, 2014
Note: The speaker notes for this slide include detailed instructions on how to customize this Title Slide with your own picture.
Tip! Remember to remove this text box.

3. Instructions DELETE THIS SLIDE (PAGE) AFTER USE:
HOW TO USE THIS ABBREVIATED PMP TEMPLATE, SUITABLE FOR SMALLER (<500 DAY PROJECTS) AND/OR AGILE PROJECTS.
THIS PMP IS A TEMPLATE AND SHOULD BE REVISED TO FIT THE NEEDS OF YOUR PROJECT. ONCE COMPLETED, THE PRESENTATION MAY BE USED DURINGTHE PROJECT KICK-OFF FOR CUSTOMER/PROJECT TEAM ORIENTATION AND WITH THE USE OF VERSIONING, IT PROVIDES A PROJECT OVERVIEW FOR CHANGES FOLLOWING STAFFING AND/OR CONTRACT REVISIONS, ETC.
PAGE ONE – PROJECT OVERVIEW: Add detail as directed in italics, and remove any text that exists that is not applicable for your project.
PAGE TWO – PROJECT MANAGEMENT & CONTROL: Add detail as directed in italics, and remove any text that exists that is not applicable for your project.
PAGE THREE – PEOPLE MANAGEMENT: Add detail as directed – for the org chart, move cells around to fit the design of your project.
PAGE FOUR – PROJECT SUCCESS FACTORS, ASSUMPTIONS, OBLIGATIONS AND ACCEPTANCE:
PAGE FIVE – DOCUMENT CONTROL, GENERAL ADMINISTRATION, PROJECT ESCALATION/PROJECT SURVEYS
PAGE SIX – PROJECT BASELINE, APPENDICES : The baseline project plan is needed (print screen) to provide detail of timelines and deliverables. This is to confirm project expectations for the team early on in the project, prior to the detailed Project Plan (Workplan) being available.
ADD MORE SLIDES IF THERE IS FURTHER INFORMATION NEEDED AND/OR IF ADDITIONAL DETAIL IS REQUIRED ON ANY OF THE PAGES THAT ARE CURRENTLY IN PLACE (e.g. , if any section is not big enough, within the section, refer to an Appendix and add a new slide at the end of PMP)
SAVE THE DOCUMENT AS V1.0 DRAFT / ISSUE & UPDATE THE FOOTERS ON PAGES 1-6 AND REPLACE <CUSTOMER>
IMPORTANT: This is a living document that will be shared with the customer as well as the Project Team. Any project process changes in the future need to be documented in the PMP and the Change Log / Reviewers Details need to be updated on Page 5 for Version Control Purposes

4. <Customer> <Project Name>
Project Background
Milestones / Payment Milestones
This is from Envision, pre-sales artifacts or as agreed with customer
Add details
Add Details
If this is a T&M Project, refer to the Financial Management Plan also
Health Checks: Audits:
Add Health Check Date if Applicable
Add Audit Date if Applicable
Project Objective/Goal
This is from Envision, pre-sales artifacts or as agreed with customer
Associated Documents
OD Reference: Add date and reference and location in Project Workspace
Add any other documents not referenced in this PMP that will be used and their location in the Project Workspace
Any other document
Project Scope
This is from the contract, Envision or other pre-project artifact
Project Start Date: date from contract
Planned End Date: date from contract
Fixed Price / Time & Materials / Staff Augmentation
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 1 of 6

5. <Customer> <Project Name> Project Governance highlights
Communication Plan
Project Procedures – Document Locations
REPORTING
Status Reporting: Provide details of how this will be done (e.g. / Tracking Spreadsheet, System)
Weekly customer Report: Add the date that this is due and to whom it is due / add location in project filing
Time & Expense Report: Add the date that this is due and to whom it is due / add location in project filing
MEETINGS
customer Meetings: e.g. PM Weekly Meeting (Friday)
Project Team Meeting: e.g. Weekly (Thursday)
Steering Comm Meeting: e.g. first Monday monthly
Configuration Review Meeting: e.g. bi-weekly Tuesdays
Product Review Meeting: e.g. bi-weekly Tuesdays
RISK-ISSUES-PROBLEMS-DECISIONS: Insert document name and location link.
<customer> Change Control: If there is no customer Change Control Plan, delete this box or state Not Applicable
CHANGE CONTROL: Insert document name and location link.
Financial Management Plan (Finance Tracking, Tools etc)
QUALITY PLAN: Insert document name and location link.
Internal Tracking System OR Project Expenses Spreadsheet (add project work location for the spreadsheet)
Expense Non billable expenses – per PM authority / Billable – per contract (OD): provide details from contract / Timesheet Codes: Set these up with Project Finance and detail them here
Invoicing: Provide details on how invoicing will be managed
NOTE: T&M Projects only: External Tracking is usually via the weekly Budget statements that are reconciled with the Monthly Invoice prior to the invoice being sent to the customer for payment
This slide presents the initial project governance. On a larger project these are items that are expected to be contained in the work products that make up the Project Management Plan.
INFRASTRUCTURE AND CONFIGURATION MANAGEMENT: Provide location or use
Provide details on anything that is not mentioned separately within this PMP (e.g. work environments, document naming conventions, project library location and structure, back-up plans, project environment (s) access etc)
WORK MANAGEMENT PLAN: The work breakdown for this project, including tasks, work products and milestones is available in a detailed Workplan Gantt chart (MS Project 2010, updated weekly). For version control, the Gantt chart will be base-lined each week by saving it to a file with a new version number. Each version of the workplan will be stored in the Oracle Beehive workspace under the name (INSERT NAME AND DOCUMENT LINK) every Friday. A pdf snapshot of the most current plan will also be stored in the workspace since not all project team members have the MS Project software. A copy of the baseline Gantt chart agreed after planning and preparation is provided on Slide 6
Quality Plan Disclaimer: The Project Quality Plan document is a deliverable under the Statement of Work and does not modify the terms of the statement of Work, including the scope of the work that Oracle will perform. The Project Quality Plan document describes the work, to be performed by Oracle as set forth in the Statement of Work, in greater detail. The terms of the Statement of Work will control over any conflicting terms in this Project Quality Plan.
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 2 of 6

6. <Customer> <Project Name>
Project Stakeholders
Project Team On-Boarding: add details about anything that needs to happen when starting work on the project (e.g. customer equipment / system access / access to project documents / training / Compliance etc)
Project Team Off-Boarding: add details about anything that needs to happen at project end (e.g. handing back equipment / system access cessation / archiving of project documents etc)
Oracle: Name, Project Role, , phone
Oracle: Name, Project Role, , phone
<customer> Name, Project Role, , phone
<customer> Name, Project Role, , phone
Oracle Project Team Roles & Responsibilities
PROJECT MANAGER R&R:
XXXXX
This is the initial Stakeholder Analysis, additional Stakeholders are likely to be identified as the project work begins. Remember missing stakeholders could mean missing requirements. Make sure that you investigate any “potential” stakeholders rather than rule them out without any investigation.
A N OTHER 1 R&R:
XXXXX
Oracle Project
Org Chart & Escalation
Practice
Director
A N OTHER 2 R&R:
XXXXX
A N OTHER 3 R&R:
XXXXX
Oracle PM
A N OTHER 4 R&R:
XXXXX
ANOTHER
ROLE 1
ANOTHER
ROLE 2
ANOTHER
ROLE 3
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 3 of 6

7. <Customer> <Project Name>
Project Success Factors
This is from contract or as agreed with customer
Assumptions
This is from contract or as agreed with customer
Obligations
This is from contract or as agreed with customer
OCM: For this project, it is solely the customer’s responsibility to define and execute OCM plans. If this is the project team’s responsibility, remove this bullet and add an appendix to cover the process that has been agreed in the contract.
Acceptance Criteria
This is from contract or as agreed with customer
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 4 of 6

8. <Customer> <Project Name>
Regulatory Compliance Needs
Change Log
Add regulatory compliance as needed.
Date
Author
Version
Change Reference
Oracle PM Name
1.0
No previous document.
General Administration
This project will follow the Oracle OUM Methodology
Project Work area location: Add a link to the location here
Team Calendar location: Add a link to the location here
Time Sheets: Every Thursday
Expenses: Weekly submission but no later than 21 days after incurring the expense
Public Holidays: Provide details
Vacation Requests: Provide details
Compliance Monitoring Procedures: Add a link to the location here
Actions Log Location: Add a link to the location here
Reviewers
If there is something that you feel is missing, or something that needs to be here for your specific project needs, insert it as appropriate. Likewise, if there are slides that don’t make sense the way they are in this presentation, do what is right for your project.
Name
Position
Date
Project Escalation
Project Escalation will take place within the structure of the Organizational Chart provided within the People Management Section. As well as timely project reviews as detailed in the Communications Plan on page 2, Project Specific <customer> feedback will be sought via Survey at the following stages:
1. At Project Start (approx one month after project start date)
2. Just prior to Go-Live
3. At project end
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).
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 5 of 6

9. <Customer> <Project Name>
APPENDICES
PROJECT BASELINE
Appendix A – Compliance Management
DELETE THE FOLLOWING IF NOT APPLICABLE
Methodology
Customer Org
Procurement (if project team’s responsibility)
OCM (if project team’s responsibility)
BASE LINE RISKS
If there are not many, list the baseline risks here or use an Appendix for numerous entries. Also add Base-Line Risks to the Risks-Issues-Decisions Log .
Add <customer> OCM activities to Risk Log if they may impact on timelines and/or deliverables
For small projects you may be able to insert an image of your project plan on this slide.
OUT OF SCOPE
If this is detailed in the OD, add information here. Add anything else that may need to be discussed in a Change Order in the future to clarify what will not be covered in the project now.
<CUST>-ORCL-PMP XXXXX
Version: Date: Page 6 of 6

10. <Customer> <Project Name>
APPENDIX A - COMPLIANCE MANAGEMENT DETAILS
1. This project will be treated as a HIPAA project (Example)
HIPAA / HITECH Compliance (Example)
Insert additional Appendix slides as needed.
<CUST>-ORCL-PMP XXXXX
Version: Date: APPENDIX A