Treasury Board of Canada Secretariat
Symbol of the Government of Canada

ARCHIVED - Project Management 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

2.2   Process Map

The overall process flow given below shows the interaction and flow among the processes. More details about the processes can be found in 2.4 Activities. (click on thumbnail below for full view)

Project Management Process - Process Map

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 - Definition
- Analysis
PM - Define and analyse requirements to create a requirements specification that is input to project planning.  
2 - Initial Project Planning PM - Initiate project planning.
- Divide the requirements if the requirements specification is to be addressed by more than one project and initiate multi-project development plans and individual project plans.
- Initiate risk management, if not started already, to identify and manage obstacles that could prevent the organisation from meeting the acceptance criteria.
3 - Create Estimates
- Review Estimates
PM - Create estimates using the business case, project charter, and requirements specification.
- Review the estimates with the affected groups and individuals.
4 - Obtain Commitment and Approval
- Establish Baseline
PM - Obtain the commitment and approval of all affected groups and individuals
- Review and discuss the plans.
- Sign the approval form when agreements and commitment is reached. This is the commitment point.
- Establish/revise the baseline in the project and enterprise databases.
5 - Compare Actuals to Plans
- Evaluate Status and Performance
- Monitor Risks
PM - Compare actuals against the plan and identify deviations.
- Evaluate deviations to determine if corrective action is required.
- Monitor status of existing risks and corrective actions.
- Identify new risks that could prevent the organisation from meeting the acceptance criteria.
6 - Requirements Status Tracking PM - Track the requirements to ensure existing requirements are addressed and traceable throughout the development life cycle. PPTO-PS-003
7 - Quality Assurance Plan
- Conduct Audits
PM - Develop the Quality Plan with input from the Quality Plans from the individual projects.
- After approval, perform the Quality Assurance activities.
8 - Status Meetings
- Project Review
- Commitment Reviews
PM - Review project status and performance at 2 levels.
- Conduct status meetings at the project level.
- Conduct project reviews at the portfolio level.
- Conduct commitment reviews.
- If replanning is required, perform steps 9-12, else continue project tracking, risk management, and project management review.
- If the project is complete , go to the delivery point and step 13.


9 - Replanning PM - Update project plans using requirement changes and revised estimates.
- Prepare a revised plan for approval and commitment negotiation.
10 - Requirements Change Control PM - Perform requirements change control if revisions involve a change in the requirements. PPTO-PS-001
11 - Additional Estimates PM - Create additional estimates as required for project planning.
- Revise estimates as a result of requirement changes or deviations in the plan.
- Refine estimates for next phase of project
12 - New Commitment Negotiation
- Revise Baseline
PM - Obtain the commitment and approval of all affected groups and individuals for the updated plans and estimates.
- Go to step 4
13 - Post-mortem PM - Conduct a post-mortem to capture information and lessons learned from the project. PPTO-PS-002
14 - Update Enterprise Database PM - Collect project data, compare against the estimates and store historical data for future use in project planning, audits, process improvement, benchmarking, etc. PPTO-PS-002

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  
Project Postmortem - Conduct a postmortem to capture lessons learned  
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
- Client approves, revises or terminates the project, product or services.

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.

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