1 / 11

Lessons Learned for Project [insert name]

This document outlines the key lessons learned from the [Insert Name] project, managed by [Insert Name] and led by [Insert Name] on [Insert Date]. It provides an overview of the project scope and background, performance indicators, and business outcomes. We assess whether the project met its objectives, highlighting aspects that went well and those that did not, categorized by different stakeholders and NPMS knowledge areas. Additionally, we suggest recommendations for improvements across various domains, including funding processes and project approval, to enhance future project performance.

chen
Download Presentation

Lessons Learned for Project [insert name]

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons Learned for Project [insert name] Project Manager: [insert name] Project Leader: [insert name] Date: [insert date]

  2. Tombstone Information

  3. Background Information • Project scope, background, etc…

  4. Performance Indicators (Space)

  5. Performance Indicators (Space)

  6. Performance Indicators (Asset)

  7. Performance Indicators (Asset)

  8. Business Outcomes • What were the project objectives? • Did the project meet its business objectives?

  9. Lessons Learned – What went well? • Can be broken down into different aspects such as: PWGSC, Client, Contractor, Consultant, Contractor AND/OR • Can be broken down into NPMS knowledge areas: Scope, HR, Cost, Time, Environment, Quality, Communications, Risk, Procurement, Safety, Financial, Claims Management

  10. What didn’t go well? • Can be broken down into different aspects such as: PWGSC, Client, Contractor, Consultant, Contractor AND/OR • Can be broken down into NPMS knowledge areas: Scope, HR, Cost, Time, Environment, Quality, Communications, Risk, Procurement, Safety, Financial, Claims Management

  11. Recommendations for Improvements Can be broken down into the following: • NPMS • Project Approval Process • Funding • Other

More Related