This PRINCE2 template was kindly produced for OGC by PROJECT in a box. This Crown copyright material is reproduced with the permission of the Controller of HMSO and the Queen's Printer for Scotland
Lessons Learned Log
Project Name: Date:
Release:
Draft/Final
Author: Owner: Client: Document Number: Note: This document is only valid on the day it was printed The Source of this document will be found in the Project File
Revision History Date of next revision: Revision Date
Previous Revision Date
Summary of changes
Changes Marked
Approvals This Document requires the following approvals. A signed Copy should be placed in the project files. Name
Signature
Title
Date of Issue
Version
Title
Date of Issue
Version
Distribution This Document should be distributed to: Name
291550336.xls
page 1 of 3
Lessons Learned Log
insert project name
date:
Overview Purpose To be a repository of any lessons learned during the project that can be
usefully applied to this or other projects. At the close of the project it is written up formally in the Lessons Learned Report. Minimally it should be updated at the end of a stage, but sensibly a note should be made in it of any good or bad point that arises in the use of the management and specialist products and tools at the time of the experience.
Contents Page 3 contains the Lessons Learned Log Advice
Information for the records in the Lessons Learned Log is derived from observation and experiences of the processes as well as the Quality Log, Completed Work Packages, Risk Log, Highlight Report(s), Checkpoint Report(s) and Stage Plans with actuals. The following quality criteria apply: - Each management control has been considered - The reasons for all tolerance deviations and corrective actions have been recorded - Input to the log is being done, minimally at the end of each stage - Project Assurance and Project Support have been asked for their input - Statistics of the success of quality reviews and other types of test used are included
Key:
291550336.xls
Lesson Types: Good - Process went well Bad - Process went badly Lacking - Process was lacking Deviation - Abnormal event causing deviation Tool - Assessment of technical method or tool used Issue - Analysis of a Project Issue and its results Recommend - Recommendations for future enhancement or modification of the project management method
Thank you for interesting in our services. We are a non-profit group that run this website to share documents. We need your help to maintenance this website.