PRINCE2™- Lessons Report

|Project Name: | |
|Date: | |Release: |Draft/Final |
|Author: | |
|Owner: | |
|Client: | |
|Document Number: | |

Note: This document is only valid on the day it was printed

Revision History Date of next revision:
|Revision Date |Previous Revision |Summary of Changes |Changes Marked|
| |Date | | |
| | | | |
| | | | |
| | | | |

Approvals

This document requires the following approvals. A signed copy should be placed in the project files.
|Name |Signature |Title |Date of Issue |Version |
| | | | | |
| | | | | |
| | | | | |

Distribution

This document has been distributed to:
|Name |Title |Date of Issue |Version |
| | | | |
| | | | |

Overview

|Purpose |The Lessons Report is used to pass on any lessons that can be usefully applied to other projects. The |
| |purpose of the report is to provoke action so that the positive lessons become embedded in the |
| |organization’s way of working, and that the organization is able to avoid any negative lessons on future |
| |projects. |
| |A Lessons Report can be created at any time in a project and should not necessarily wait to the end. |
| |Typically it should be included as part of the |
| |End Stage Report and End Project Report. It may be appropriate (and necessary) for there to be several |
| |Lessons Reports specific to the particular organization (e.g. user, supplier, corporate or programme). |
| |The data in the report should be used by the corporate group that is responsible for the quality management|
| |system, in order to refine, change and improve the standards. Statistics on how much effort was