PRINCE2 (TM) Lessons Report

To get an editable copy of this template to use on your project go to http://www.stakeholdermap.com/project-templates/prince-2-templates.html

Get Started. It's Free
or sign up with your email address
Rocket clouds
PRINCE2 (TM) Lessons Report by Mind Map: PRINCE2 (TM) Lessons  Report

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History

1.8.1.1. Revision # [....]

1.8.1.1.1. Revision Date

1.8.1.1.2. Previous Revision Date

1.8.1.1.3. Summary of Changes

1.8.1.1.4. Changes Marked

1.8.1.2. Revision # [....]

1.8.1.2.1. Revision Date

1.8.1.2.2. Previous Revision Date

1.8.1.2.3. Summary of Changes

1.8.1.2.4. Changes Marked

1.8.1.3. Revision # [....]

1.8.1.3.1. Revision Date

1.8.1.3.2. Previous Revision Date

1.8.1.3.3. Summary of Changes

1.8.1.3.4. Changes Marked

1.8.1.4. Date of next revision:

1.8.1.4.1. [....]

1.8.2. Approvals

1.8.2.1. Approval # [....]

1.8.2.1.1. Name

1.8.2.1.2. Signature

1.8.2.1.3. Title

1.8.2.1.4. Date of Issue

1.8.2.1.5. Version

1.8.2.2. Approval # [....]

1.8.2.2.1. Name

1.8.2.2.2. Signature

1.8.2.2.3. Title

1.8.2.2.4. Date of Issue

1.8.2.2.5. Version

1.8.2.3. Approval # [....]

1.8.2.3.1. Name

1.8.2.3.2. Signature

1.8.2.3.3. Title

1.8.2.3.4. Date of Issue

1.8.2.3.5. Version

1.8.3. Distribution

1.8.3.1. Distribution # [....]

1.8.3.1.1. Name

1.8.3.1.2. Title

1.8.3.1.3. Date of issue

1.8.3.1.4. Version

1.8.3.2. Distribution # [....]

1.8.3.2.1. Name

1.8.3.2.2. Title

1.8.3.2.3. Date of issue

1.8.3.2.4. Version

2. Overview

2.1. Purpose

2.1.1. 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.

2.1.2. 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).

2.1.3. 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 needed for products can help improve future estimating.

2.2. Contents

2.2.1. The Lessons Report should cover the following topics.

2.2.2. Executive Summary

2.2.3. Overall Review

2.2.4. Review of Useful Measures

2.2.5. Significant Lessons

2.3. Advice

2.3.1. The Lessons Report is derived from the following documents: Project Initiation Documentation (for the baseline position); Lessons Log (for identification of lessons); Quality Register, Issue Register and Risk Register (for statistical analysis); Quality records (for statistical analysis) and Communication Management Strategy (for the distribution list).

2.3.2. The Lessons Report can take a number of formats, including: Oral report to the Project Board (could be in person or over the phone); Presentation at a progress meeting (physical meeting or conference call); Document or email to the Project Board; Entry in a project management tool.

2.3.3. The following quality criteria should be observed:

2.3.3.1. Every management control has been examined

2.3.3.2. Statistics of estimates versus actuals are provided

2.3.3.3. Statistics of the success of quality controls used are included

2.3.3.4. Any appointed Project Assurance roles agree with the report

2.3.3.5. Unexpected risks are reviewed to determine whether they could have been anticipated

2.3.3.6. Recommended actions are provided for each lesson (note that lessons are not ‘learned’ until action is taken).

3. How to use this template

3.1. How to share this template with your team

3.1.1. Send an email

3.1.1.1. 1. Click Share this map

3.1.1.2. 2. Select Invite People

3.1.1.3. 3. Write a message

3.1.1.4. 4. Click Invite

3.1.2. Send a link

3.1.2.1. 1. Click Share this map

3.1.2.2. 2. Tick Link to share

3.1.2.3. 3. Copy the link to share it

3.1.3. Export

3.1.3.1. 1. Click down arrow, bottom right

3.1.3.2. 2. Select the export option you want

3.2. How to complete this template

3.2.1. Complete the sections in square brackets

3.2.1.1. [....]

3.2.2. Read these sections for help on this template

3.2.2.1. Purpose

3.2.2.2. Advice

3.2.3. Navigate using the links in Contents

3.2.3.1. Contents

3.3. Attribution

3.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

3.4. Get this template here

4. Significant Lessons

4.1. Event

4.1.1. [...]

4.2. Effect

4.2.1. [State the positive or negative effect of the event]

4.3. Causes/Trigger

4.3.1. [...]

4.4. Early Warnings?

4.4.1. [State whether there where any early-warning indicators]

4.5. Identified as a Risk?

4.5.1. [State whether the triggered event was previously identified as a risk (threat or opportunity)]

4.6. Recommendations

4.6.1. [...]

5. Executive Summary

5.1. [Specify the scope of the report e.g. Stage or Project]

6. Overall Review

6.1. [Review what went well, what went badly and any recommendations for corporate or programme management consideration. In particular: Project management method; Any specialist methods used; Project strategies; Project controls and Abnormal events causing deviations]

7. Review of Useful Measures

7.1. [Review useful measures such as: How much effort was required to create the products; How effective was the Quality Management Strategy in designing, developing and delivering fit-for-purpose products and Statistics on issues and risks]