D8

Tool

University of Prosperity PPM Selection Project

PPM Selection Project

University of Prosperity

Lessons Learned | Page 9

Table of Contents

Introduction to the Lessons Learned Tool

The Lessons Learned deliverable serves as a continuous improvement mechanism in which successes and mistakes are documented. Lessons Leaned are fundamental for organizations and their journey to improve future performance. Furthermore, formally identifies, acknowledges, analyzes, and documents the lessons learned. Finally, collecting lessons learned over time adds to the organization’s body of knowledge related to project management and provides a rich source of information for current and future work. Lessons learned are produced at the end of a project, or they may take place between project phases to make the lessons learned available for later phases.

The lessons learned tool would assist the project team to identify and document lessons learned. The tool provides guidelines and questions to consider about what worked well, what did not work well, and what needs to be done differently. The goal of documenting lessons learned is to identify both the positive and negative lessons learned from the project, as well as to recommend corrective actions based on negative lessons learned remarks

The lessons learned tool provides general guidelines for accurately documenting the project lessons learned. Additional examples and suggestions are provided to help you produce your lessons-learned project deliverable.

Template style conventions are as follows:

As you us this tool, please remember to delete all instructional text (including this section) and update the following items, as applicable:

· title page

· version history

· table of contents

· headers

· footers

Lessons learned allow a project team to retrospectively contemplate and document the failures and successes experienced on a project to facilitate the knowledge transfer from one team to the next. Capturing this information in a formal fashion creates an artifact that can be utilized during future endeavors to reduce the risk of repeating a mistake. This lessons-learned document includes input from the project team as to what went well, what did not go well, why, and what could have been done differently.

Lessons Learned to identify and delineate considerations taking into consideration the following categories:

· Cost

· Communication

· Documentation

· Processes

· Procurements/Contracts

· Quality

· Resources/Staffing

· Schedule/Time

· Scope/Requirements

· Tools

To encourage the thought process, you are encouraged to answer the following questions.

· What worked well for this project?

· What did not work well for this project?

· What could have been done over or differently?

· What surprises did you deal with?

· What project circumstances were not anticipated?

· Were the project goals attained? If not, what changes need to be made to meet goals in the future?

All lessons learned are documented in the table below.

The lessons learned table provided below serves as an example only. Feel free to inform this table as you feel necessary.

Tool

University of Prosperity PPM Selection Project

PPM Selection Project

University of Prosperity

Lessons Learned | Page 9

Table of Contents

Introduction to the Lessons Learned Tool

The Lessons Learned deliverable serves as a continuous improvement mechanism in which successes and mistakes are documented. Lessons Leaned are fundamental for organizations and their journey to improve future performance. Furthermore, formally identifies, acknowledges, analyzes, and documents the lessons learned. Finally, collecting lessons learned over time adds to the organization’s body of knowledge related to project management and provides a rich source of information for current and future work. Lessons learned are produced at the end of a project, or they may take place between project phases to make the lessons learned available for later phases.

The lessons learned tool would assist the project team to identify and document lessons learned. The tool provides guidelines and questions to consider about what worked well, what did not work well, and what needs to be done differently. The goal of documenting lessons learned is to identify both the positive and negative lessons learned from the project, as well as to recommend corrective actions based on negative lessons learned remarks

The lessons learned tool provides general guidelines for accurately documenting the project lessons learned. Additional examples and suggestions are provided to help you produce your lessons-learned project deliverable.

Template style conventions are as follows:

As you us this tool, please remember to delete all instructional text (including this section) and update the following items, as applicable:

· title page

· version history

· table of contents

· headers

· footers

Lessons learned allow a project team to retrospectively contemplate and document the failures and successes experienced on a project to facilitate the knowledge transfer from one team to the next. Capturing this information in a formal fashion creates an artifact that can be utilized during future endeavors to reduce the risk of repeating a mistake. This lessons-learned document includes input from the project team as to what went well, what did not go well, why, and what could have been done differently.

Lessons Learned to identify and delineate considerations taking into consideration the following categories:

· Cost

· Communication

· Documentation

· Processes

· Procurements/Contracts

· Quality

· Resources/Staffing

· Schedule/Time

· Scope/Requirements

· Tools

To encourage the thought process, you are encouraged to answer the following questions.

· What worked well for this project?

· What did not work well for this project?

· What could have been done over or differently?

· What surprises did you deal with?

· What project circumstances were not anticipated?

· Were the project goals attained? If not, what changes need to be made to meet goals in the future?

All lessons learned are documented in the table below.

The lessons learned table provided below serves as an example only. Feel free to inform this table as you feel necessary.