This page has been archived.
Information identified as archived on the Web is for reference, research or recordkeeping purposes. It has not been altered or updated after the date of archiving. Web pages that are archived on the Web are not subject to the Government of Canada Web Standards. As per the Communications Policy of the Government of Canada, you can request alternate formats on the "Contact Us" page.
PPTO-PS-002 Project Planning Process
January 2000
Chief Information Officer Branch
Treasury Board of Canada Secretariat
The purpose of this document is to describe the process to be followed by a project manager to plan a project.
This document is applicable to any IM/IT project.
The scope covers the processes necessary to support IM/IT delivery commitments at the portfolio level. These processes include organisation-wide processes at the portfolio level, and project-based processes at the project level.
Project Level Processes | Portfolio Level Processes |
Requirements Management Process | Commitment Control Process |
Project Planning Process | Project Management Review Process |
Estimation Process | Software Quality Assurance Process |
Project Tracking Process | Project Management Processes Overview |
Everyone in the organisation has a role to perform in these processes.
Role | Description/Responsibilities |
Project Leader (PL) | This is the person appointed by the sponsoring department to be accountable for all external and internal aspects of a capital project. http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp |
Project Manager (PM) | This is a person formally appointed to manage a project with specific accountability for achieving defined project objectives within allocated resources. A project manager has access to, and a formally defined relationship with, the project leader to which the specific project has been assigned. http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp |
Project Team Member (PTM) |
Software engineer or writer assigned to a project
Responsible for completing project tasks, providing input to plans, and providing status |
Project Management Office (PMO) | This is a distinct and temporary organisational unit led by the project manager tasked to administer a project. It consists of assigned full or part-time members of the sponsoring department and, when appropriate, representatives of participating departments working together in accordance with any interdepartmental agreements or memorandums of
understanding. http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp |
Quality Assurance (QA ) | Responsible for support of quality assurance activities. |
Configuration Management (CM) | Responsible for support of configuration management activities. |
Refer to Enhanced Management Framework Lexicon.
Refer to Enhanced Management Framework Acronyms.
Refer to Enhanced Management Framework Web Links
This process was designed to satisfy the SEI Software Capability Maturity Model goals for Level 2 Key Practice: Software Project Planning.
Treasury Board Secretariat Policies:
The policies above are located at the following URL:
http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/siglist-eng.asp
Annex A – Flowcharting Symbols
PPTO-PS-001 Project Management Process
PPTO-PS-003 Project Tracking and Oversight Process
PEER-PS-001 Peer Review Process
PPTO-PD-001 Estimate Software Product Size Basic Procedure
PPTO-PD-002 Estimate Project Resources/Schedule Basic Procedure
EMF Business Case Guidelines
PPTO-TM-001 Process/Procedure Template
PPTO-TM-002 Project Plan Template
PPTO-TM-003 Project Estimates Template
EMF Project Charter Template
PPTO-CK-001 Project Management Checklist
The following entry criteria describes the input's state, an event, or an expired amount of time, which is required before this process can begin.
Details of Entry Criteria |
|
The overall process flow given below shows the interaction and flow among the activities. More details about the activities can be found in 2.4 Activities.
The following inputs are used in this process. Where they don't exist, identify any associated risks.
Input | Detail of Inputs and remarks | Ref. |
Business Case | The identification and justification of an IM/IT project that relates the IM/IT project to program priorities and the measurable improvements in program performance.
|
EMF Business Case Guideline |
Project Charter | An agreement between technical and business groups defining:
|
EMF Project Charter Template |
Enterprise Database |
|
|
IM/IT Methodology Deliverables |
|
The following activities are performed in this process. Document all assumptions, risks, constraints etc. in the Project Plan.
No. | Activities | Action by | Detail of Activities and Remarks | Ref. |
1 | Requirements Management | PM |
|
PPTO-PS-001 |
2 | Negotiate Commitment | PM |
|
|
3 | Decompose Requirements | PM |
|
PPTO-TM-002 |
4 | Estimate Product Size | PM PTM |
|
PPTO-PD-001
PPTO-TM-002 |
5 | Estimate Project Resources | PM
PTM |
|
PPTO-PD-002
PPTO-TM-002 |
6 | Develop Schedule | PM
PTM |
|
PPTO-PD-002
PPTO-TM-002 |
7 | Obtain Commitment and Approval | PL
PM |
|
|
8 | Project Tracking | ALL |
|
PPTO-PS-001 PPTO-PS-003 |
The following outputs are produced or modified by the activities in this process.
Output | Detail of Outputs and Remarks | Ref. |
Project Charter |
|
EMF Project Charter Template |
Project Plan |
|
PPTO-TM-002 |
Project Deliverables |
|
|
IM/IT Methodology Deliverables |
|
|
Enterprise Database |
|
Output Validation | To determine if the outputs are within specification,
|
Details of Exit Criteria |
|
Refer to Enhanced Management Framework, Exposure Draft Executive Toolkit, November 22, 1999 for the Project Health Check Dashboard.
Not applicable at this time. Populate table if seeking ISO certification. For more information, refer to (PPTO-TM-001) Process/Procedure Template.
Description (no. and name) |
Storage Location | Filing / Index | Minimum Storage Period |
Not applicable at this time. Populate if seeking ISO certification. For more information, refer to (PPTO-TM-001) Process/Procedure Template.
Number | Name | Revision Date (or version) |
Owner |
Refer to the Enhanced Management Framework Lexicon or insert a reference to your organisation's Lexicon.
Refer to the Enhanced Management Framework Acronyms or insert a reference to your organisation's Acronyms.
Parallelograms represent inputs and outputs to or from a process/procedure. | |
Rectangles represent individual process/procedure activities. | Diamonds represent important decision points in the process/procedure. |
Lines with arrowheads connect symbols to show the progression or direction of the activities. | Circles represent connectors when a process/procedure flowchart continues on the next page. |
Humphrey, Watts, Managing the Software Process, Addison Wesley, Reading Massachusetts, 1990.
Refer to Enhanced Management Framework Web Links.
Revision Number | Date of Issue | Author(s) | Brief Description of Change |
0.1 | 1999-06-15 | EMF/PPTO | Initial Draft |
0.2 | 1999-08-30 | EMF/PPTO | Initial review from the PPTO WG meeting 1999-08-24. |
0.3 | 1999-09-07 | EMF/PPTO | Included additional comments from PPTO members based on a second review. |
0.4 | 1999-09-13 | EMF/PPTO | Included additional comments from PPTO members based on a third review. |
1.0 | 1999-11-09 | EMF/PPTO | First Draft |
1.0 | 2000-01-21 | EMF/PPTO | Second Draft |