Skip to content Skip to institutional links

Common menu bar links

Breadcrumb Trail

Institutional links

Chief Information Officer Branch

IT Project Review and Oversight

Enhanced Management Framework

Versions

ARCHIVED - Project Planning Process

Warning This page has been archived.

Archived Content

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.

2. Process

2.1 Entry Criteria

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

Approved Business Case
Approved Project Charter
Approved Set of Requirements, as required by your IM/IT methodologies

2.2 Process Map

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.

2.3 Inputs

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. Identifies the opportunity Describes the added value Describes the IM/IT solution Identifies the indicators to measure improvements in program performance	EMF Business Case Guideline
Project Charter	An agreement between technical and business groups defining: Partners & external stakeholders Project management framework Roles, responsibilities, accountabilities and activities Management commitments Empowerment framework	EMF Project Charter Template
Enterprise Database	Actuals from previous IM/IT Projects for comparison and verification of the planning process.
IM/IT Methodology Deliverables	Architectures, processes, templates, etc…

2.4 Activities

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	Requirements management in the context of overall project management is documented in PPTO-PS-001 Project Management Process.	PPTO-PS-001
2	Negotiate Commitment	PM	Negotiations have begun. Estimates (activities 3-6) must be done in parallel with other planning activities before final commitment.
3	Decompose Requirements	PM	Create a Work Breakdown Structure (WBS). Identify the processes and deliverables for the project and map the requirements to processes and deliverables. The WBS should reflect organisational System Development Life Cycle (SDLC). Review WBS with affected groups and individuals. If requirements are divided into interdependent individual projects a multi project plan will be required to cover interdependencies and integration.	PPTO-TM-002
4	Estimate Product Size	PM PTM	Estimate Product Size for each product element using your organisation's estimation methods, tools and techniques. In the absence of the above use the referenced procedure for estimating software product size. Project tracking in the context of overall project management is documented in the referenced documents.	PPTO-PD-001 PPTO-TM-002
5	Estimate Project Resources	PM PTM	Estimate Project Resources using your organisation's estimation methods, tools and techniques. In the absence of the above use the referenced procedure for estimating project resources.	PPTO-PD-002 PPTO-TM-002
6	Develop Schedule	PM PTM	Develop Schedule using your organisation's estimation tools and techniques. In the absence of the above use the referenced procedure for developing schedule. Does Plan meet need? [YES] results in obtaining approval of the project plan. Go to activity 7. [NO] results in re-negotiating requirements (i.e. De-Scope or more effort, schedule, or funds). Then re-plan. Go to activity 2.	PPTO-PD-002 PPTO-TM-002
7	Obtain Commitment and Approval	PL PM PTM	Approval is received from all affected groups and individuals.
8	Project Tracking	ALL	Project tracking in the context of overall project management is documented in the referenced documents.	PPTO-PS-001 PPTO-PS-003

2.5 Outputs

The following outputs are produced or modified by the activities in this process.

Output	Detail of Outputs and Remarks	Ref.
Project Charter	Possible modifications	EMF Project Charter Template
Project Plan	Project estimates are included in the Project Plan	PPTO-TM-002
Project Deliverables	Deliverables the customer will receive
IM/IT Methodology Deliverables	Deliverables the IM/IT organisation requires to produce the solution
Enterprise Database	Compare original estimates to actuals Update historical data for use in future projects

2.6 Verification and Validation

Output Validation

To determine if the outputs are within specification,

Use the (PEER-PS-001) Peer Review Process and any techniques described in your IM/IT methodology.
Use validation techniques referred to in your IM/IT methodology such as testing, demonstration, analysis and inspection.

2.7 Exit Criteria

Details of Exit Criteria

Approved Project Plan.

2.8 Metrics

Refer to Enhanced Management Framework, Exposure Draft Executive Toolkit, November 22, 1999 for the Project Health Check Dashboard.

2.9 Records Control Table

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

2.10 Controlled Documents Table

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