copyright © 2014 oracle and/or its affiliates. all rights reserved. | project management plan...

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

Project Management Plan<Company Name><Project Name>

Presenter’s NamePresenter’s TitleOrganization, Division or Business UnitMonth 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.


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 SURVEYSPAGE 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

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 SURVEYSPAGE 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

Instructions


Project Background

Project Scope

Project Objective/Goal

•This is from Envision, pre-sales artifacts or as agreed with customer•This is from Envision, pre-sales artifacts or as agreed with customer

• This is from the contract, Envision or other pre-project artifact • This is from the contract, Envision or other pre-project artifact

•This is from Envision, pre-sales artifacts or as agreed with customer•This is from Envision, pre-sales artifacts or as agreed with customerAssociated Documents

OD Reference: Add date and reference and location in Project Workspace

1. Add any other documents not referenced in this PMP that will be used and their location in the Project Workspace

2. Any other document

OD Reference: Add date and reference and location in Project Workspace

1. Add any other documents not referenced in this PMP that will be used and their location in the Project Workspace

2. Any other document

Planned End Date: date from contractPlanned End Date: date from contract

Fixed Price / Time & Materials / Staff AugmentationFixed Price / Time & Materials / Staff Augmentation

Project Start Date: date from contractProject Start Date: date from contract

<CUST>-ORCL-PMP-005 3003XXXXXVersion: Date: Page 1 of 6

Milestones / Payment Milestones1. Add details2. Add details3. Add Details

If this is a T&M Project, refer to the Financial Management Plan also

1. Add details2. Add details3. Add Details

If this is a T&M Project, refer to the Financial Management Plan also

Add Health Check Date if ApplicableAdd Audit Date if ApplicableAdd Health Check Date if ApplicableAdd Audit Date if Applicable

Health Checks:

Audits:

<Customer> <Project Name>


Financial Management Plan (Finance Tracking, Tools etc)

Communication Plan

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 hereInvoicing: 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

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 hereInvoicing: 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

REPORTINGStatus 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 filingTime & Expense Report: Add the date that this is due and to whom it is due / add location in project filing

REPORTINGStatus 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 filingTime & Expense Report: Add the date that this is due and to whom it is due / add location in project filing

Project Procedures – Document Locations

QUALITY PLAN: Insert document name and location link.QUALITY PLAN: Insert document name and location link.

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)

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)


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.

MEETINGScustomer Meetings: e.g. PM Weekly Meeting (Friday)Project Team Meeting: e.g. Weekly (Thursday)Steering Comm Meeting: e.g. first Monday monthlyConfiguration Review Meeting: e.g. bi-weekly TuesdaysProduct Review Meeting: e.g. bi-weekly Tuesdays

MEETINGScustomer Meetings: e.g. PM Weekly Meeting (Friday)Project Team Meeting: e.g. Weekly (Thursday)Steering Comm Meeting: e.g. first Monday monthlyConfiguration Review Meeting: e.g. bi-weekly TuesdaysProduct Review Meeting: e.g. bi-weekly Tuesdays

CHANGE CONTROL: Insert document name and location link.CHANGE CONTROL: Insert document name and location link.

RISK-ISSUES-PROBLEMS-DECISIONS: Insert document name and location link.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<customer> Change Control: If there is no customer Change Control Plan, delete this box or state Not Applicable

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

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

<Customer> <Project Name> Project Governance highlights

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |<CUST>-ORCL-PMP-005 3003XXXXXVersion: Date: Page 3 of 6

Oracle Project Team Roles & Responsibilities

PROJECT MANAGER R&R:XXXXXPROJECT MANAGER R&R:XXXXX

A N OTHER 1 R&R:XXXXXA N OTHER 1 R&R:XXXXX

Oracle ProjectOrg Chart & Escalation



PracticeDirector

OraclePM

ANOTHERROLE 1

ANOTHERROLE 2

ANOTHERROLE 3

Oracle: Name, Project Role, e-mail, phoneOracle: Name, Project Role, e-mail, phone<customer> Name, Project Role, e-mail, phone<customer> Name, Project Role, e-mail, phone

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)

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)



Project Success Factors

•This is from contract or as agreed with customer•This is from contract or as agreed with customer


Acceptance Criteria


Assumptions

Obligations•This is from contract or as agreed with customer•OCM: For this project, it is solely the Client’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.

•This is from contract or as agreed with customer•OCM: For this project, it is solely the Client’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.




Change Log


Reviewers

General AdministrationThis project will follow the Oracle OUM MethodologyProject Work area location: Add a link to the location hereTeam Calendar location: Add a link to the location hereTime Sheets: Every ThursdayExpenses: Weekly submission but no later than 21 days after incurring the expensePublic Holidays: Provide detailsVacation Requests: Provide detailsCompliance Monitoring Procedures: Add a link to the location hereActions Log Location: Add a link to the location here

Date Author Version Change Reference

Oracle PM Name 1.0 No previous document.

Name Position Date

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).

Project EscalationProject 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-Live3. At project end

Regulatory Compliance Needs

Add regulatory compliance as needed.



APPENDICES

•Appendix A – Compliance ManagementDELETE THE FOLLOWING IF NOT APPLICABLE•Methodology•Customer Org•Procurement (if project team’s responsibility) •OCM (if project team’s responsibility)

•Appendix A – Compliance ManagementDELETE THE FOLLOWING IF NOT APPLICABLE•Methodology•Customer Org•Procurement (if project team’s responsibility) •OCM (if project team’s responsibility)

PROJECT BASELINE

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

•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

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.

•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.




APPENDIX A - COMPLIANCE MANAGEMENT DETAILS

<CUST>-ORCL-PMP-005 3003XXXXXVersion: Date: APPENDIX A

1. This project will be treated as a HIPAA project (Example)

HIPAA / HITECH Compliance (Example)


copyright © 2014 oracle and/or its affiliates. all rights reserved. | project management plan...

Documents

project workspace

project finance

project expenses spreadsheet

project work location

preproject artifact

audit date

end date

tracking spreadsheet