preliminary project plan—« Lite » Version Template
Project Name
Branch
National Project Management System
Business Projects-information Technology-Enabled
initiation phase
Instructions
This document is your template to producing a preliminary project plan (PPP), a key requirement for the implementation of any project.
Document Purpose
The PPP is the document that defines the plan that will be used to meet the project objectives during the Identification Stage. It will include why the project is being initiated, what is to be done, who will be involved in its development, when it will be done and how it will be done. Once the Identification Stage is completed, and the project is approved at preliminary project Aproval, the project plan will be used to transition the project for delivery by the Project Delivery Team. If the project is not approved, or if it is put on hold, the PPP becomes the key record of the project's project management processes during the Identification Stage.
To create a preliminary project plan from this template, simply:
- Replace the title on the cover page with the name of your project and the organization information
- Replace the <italicized text> in the document header with your project name and information
- Save your document with a filename that is in accordance with current branch document naming standards
- Update the filename in the document footer by right-clicking and selecting "edit footer"
- Complete the entire template. Each section contains abbreviated instructions, shown in italics, which can be removed once your document is finalized. Tables are also provided as a suggested layout for some of the information required
- Update the table of contents by right-clicking and selecting Update Field, then update entire table
- Note: Replace all the text between the less than/greater than symbols "<…>" with project specific statements
- Delete this page when the PPP is complete
Revision History
Note: This table is only for example and contains no data.
| Version Number | Description | Date Modified | Author |
|---|---|---|---|
| 1.0 | |||
Authority Signatures
The Sponsor/Project Leader and the Project Manager agree to deliver the Identification Stage of this project in accordance with this PPP.
Prepared by:
(PSPC) / Signature
Please print:
Name:
Position:
Date:
Prepared by:
(PSPC) / Signature
Please print:
Name:
Project Analyst:
Date:
Recommended by:
(PSPC) / Signature
Please print:
Name:
Title:
Date:
Approved by:
(See NPMS procedures for approval Body)
(PSPC) / Signature
Please print:
Name:
Title:
Date:
On this page
- 1. Scope Definition
- 2. Milestone Schedule
- 3. Cost Management
- 4. Change Management
- 5. Quality Management
- 6. Human Resources Management/Staffing Management
- 7. Risk Management
- 8. Information Management
- 9. Procurement Management
- 10. Identification Stage Closure
1. Scope Definition
Describe how attaining the major project objectives can meet the problem/opportunity requirements. The preliminary content for this section should closely resemble the "problem/opportunity" section of the Statement of Requirement (SoR). Include a high level scope statement.
2. Milestone Schedule
Note: This table is only for example and contains no data.
| Milestone | Responsibility (Name and Title) |
Date | (F)orecast or (A)ctual |
|---|---|---|---|
3. Cost Management
Copy the spending breakdown provided in the Statement of Requirement approval document and provide an estimate/timeline of how the funds for those cost items/activities will be disbursed.
4. Change Management
Minor changes to the project that do not affect scope, time or cost will be approved by the Project Leader up to the end of the project identification stage. Major changes that affect scope, time and cost will be approved in accordance with the governance, escalation and approval process determined in NPMS Business Projects-IT-Enabled Procedures.
5. Quality Management
Specify all processes and governance that will be implemented to ensure quality of processes and products.
6. Human Resources Management/Staffing Management
Insert the roles and responsibilities of the key team members and decision makers of the Identification Stage.
7. Risk Management
Project risks will be managed in accordance with the Departmental Risk Management process, policies and procedures. <Enter high priority risks.>
Note: This table is only for example and contains no data.
| No. | Risk | Risk Management Strategy |
|---|---|---|
| 1 | ||
| 2 |
8. Information Management
The project will manage all information and documentation produced in accordance with the PSPC DP 102 Information Management Policy (page available on Government of Canada network only), using a project information management plan based on the Information Management Plan Template.
Indicate where Project Documents will be stored if not in E-DRM.
9. Procurement Management
Include any consultants required to supplement the project team; this would include, for example, those assisting in the definition/analysis process or producing feasibility studies or other supporting documentation for the Identification Stage only.
Delete this section if it is not required.
10. Identification Stage Closure
The project will conduct administrative closure activities for the Identification Stage. "Contract closure activities will be required for those service providers not participating in project delivery activities. The goal is to ensure a smooth transition to the Project Delivery Team that will lead the implementation effort."
- Date modified: