Business Projects-IT-Enabled « Full » version (and those requiring TB Submission) - Introduction

• NPMS Interactive Model
• Step-by-Step Guide to NPMS
• NPMS Deliverables Templates
• NPMS Tools, Logs and Forms
• NPMS Roadmap
• Project Management Knowledge Areas
• Project Management Handbook

« Full » Definition

NPMS « Full » applies to a project that requires TB approvals, a new solution project with an estimated cost over $1 Million, or a maintenance project with an estimated cost over $2 Million.

Step-by-Step Guide to NPMS

(Due to the size of the image, it may not display properly.)

A larger image and long description of Project Steps, Deliverables, Templates and control points, is available on a separate page.

1. Inception Stage

The purpose of this stage is to present a proposal to an authority, stating a business problem or an opportunity and seeking funding. The deliverable is a signed and approved statement of requirements document.

• Step 1: For IT-Enabled projects with a planned value of $1 Million or more, complete the Project complexity and risk assessment Tool.
• Step 2: Complete the SoR Template.
• Step 3: Obtain Statement of Requirement Approval (SoRA) from respective Business Line Director General (DG).
• Step 4: Proceed to next step: Initiation phase.

2. Identification Stage: initiation phase

The purpose of this stage is to complete a preliminary project plan which describes 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. The deliverable is a signed and approved preliminary project plan.

• Step 1: Complete the Preliminary project plan (PPP) Template.
• Step 2:
  • If the project requires a Treasury Board (TB) submission, conduct a review of the project's concept using TB's project review methodology.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct an independent review of the project concept.
• Step 3: Consult with ITSB Client Engagement sector.
• Step 4: Present PPP to the IM/IT Architecture Review Board.
• Step 5: Obtain Preliminary project plan approval (PPPA) from respective Business Line Director.
• Step 6: Proceed to next step: Feasibility Phase.

3. Identification Stage: Feasibility Phase

The Feasibility report is a document that assesses potential solutions to the business problem or opportunity and determines which of these are viable for further analysis. The deliverable is a signed and approved Feasibility report.

• Step 1:
  • If your project requires a Treasury Board (TB) submission, conduct an independent review of the project's approach then proceed to Step 2.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct an independent review of the project's approach.
• Step 2: Complete the Feasibility report Template.
• Step 3: Obtain Feasibility report approval (FRA) from respective Business Line Director.
• Step 4: Consult with ITSB Client Engagement sector.
• Step 5: Proceed to next step: Analysis Phase.

4. Identification Stage: Analysis Phase

The purpose of this stage is to complete a Business Case and Project charter. A business case is typically a proposal seeking additional funding and the Project Plan approval for the project. A Project charter formally authorizes the existence of a project and provides details.

• Step 1: Complete the Business Case Template.
• Step 2: Complete the Project charter Template.
• Step 3: Update the Project complexity and risk assessment Tool as required for projects tracked by TB through the PSPC's Investment Project Plan (IPP).
• Step 4:
  • If your project requires a Treasury Board (TB) submission, submit proposal to Business Operations Committee (BOC).
  • If your project does not require a TB submission it is at the discretion of senior management to conduct a Business Case independent review.
• Step 5: Present to Enterprise change advisory board (Gate 1).
• Step 6: Obtain Preliminary project approval (PPA) from Project Authority delegation.
• Step 7: Proceed to next step: Identification close out phase.

5. Identification Stage: Identification Close-Out Phase

The purpose of this stage is to complete the Identification close out document (ICOD) that is a checklist recording the completion of core deliverables and the status of the key close out activities.

• Step 1: Complete the ICOD checklist template.
• Step 2: ICOD approved by Project Manager.
• Step 3: Proceed to next step: Planning Phase.

6. Delivery Stage: Planning Phase

The purpose of the Planning Phase is to prepare a complete project instruction for the project team. The deliverable is a signed and approved project management plan.

• Step 1: Complete the Project management plan (PMP) Template. Use contents from the Preliminary project plan (PPP) Template as a base.
• Step 2:
  • If the project requires a Treasury Board (TB) submission, conduct a Project charter independent review using TB's project review methodology.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct a Project charter independent review.
• Step 3: Obtain Project management plan approval (PMPA) from the Project Lead and Project Manager.
• Step 4: Proceed to next step: Design Phase.

7. Delivery Stage: Design Phase

The purpose of this stage is to establish the design team and develop Design Specifications complying with the project objectives and requirements. The deliverable consists of updates to the Business Case, Project charter and PCRA which will become the approval documents.

• Step 1: Update the Business Case, project charter and the PCRA.
• Step 2:
  • If the project requires a Treasury Board (TB) submission, conduct a Detailed Plan independent review using TB's project review methodology.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct a Pre-Construction independent review using TB's project review methodology.
• Step 3: Present to Enterprise change advisory board (Gate 2).
• Step 4: Obtain Effective project approval from the Project Authority delegation.
• Step 5: Proceed to next step: Implementation Phase.

8. Delivery Stage: Implementation Phase

The purpose of this stage is to produce the project's product, with an acceptable level of quality to meet client and stakeholder requirements and to deliver that product back to the client. The deliverable is to complete the product turn-over template.

• Step 1:
  • If the project requires a Treasury Board (TB) submission, conduct a Construction/Deployment independent review using TB's project review methodology.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct a Pre-Deployment independent review.
• Step 2: Present to Enterprise change advisory board (Gate 3).
• Step 3: Complete the Product turn-over template.
• Step 4: Obtain turn-over Approval from the Business Line Director General or Functional Director.
• Step 5: Proceed to next step: Delivery Close Out Phase.

9. Delivery Stage: Delivery Close Out Phase

The purpose of this stage is to provide an assessment of the project's performance against its objectives and requirements. It includes the completion of all contract administration activities, final evaluation of project teams including consultants and contractors and preparation of lessons learned. The deliverable consists of producing a close out document.

• Step 1:
  • If the project requires a Treasury Board (TB) submission, conduct a Post Implementation independent review using TB's project review methodology.
  • If your project does not require a TB submission it is at the discretion of senior management to conduct a Post Implementation independent review.
• Step 2: Complete the Close out document template.
• Step 3: Obtain Close out document document approval from the Business Line Director or Project Leader.

NPMS Tools, Logs and Forms

• Project complexity and risk assessment Manual
• Project complexity and risk assessment Tool
• Change Request Form Template
• Change Log
• Information Management (IM) Plan template
• Issue Log
• Lessons learned log
• Naming, Numbering and Metadata Standard
• IM/IT ARB Presentation Template
• Performance Monitoring and Reporting Standard
• Project Schedule
• Risk Register
• Project Status Report
• Enterprise change advisory board « Full » version
• Related Links
• Communications Management