Appendix A: Product Description outlines | Entry in a project management tool Part of an integrated project register for all 249 risks, actions, decisions, assumptions, issues, lessons etc. A.14.5 Quality criteria The status indicates whether action has been taken Lessons are uniquely identified, including to which product they refer A process is defined by which the Lessons Log is to be updated Access to the Lessons Log is controlled The Lessons Log is kept in a safe place. A.15 lessons RePoRt A.15.1 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 needed for products can help improve future estimating. Any specialist methods used Project strategies (risk management, quality management, communications management and configuration management) Project controls (and the effectiveness of any tailoring) Abnormal events causing deviations A review of useful measurements 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 (for example, how many errors were found after products had passed quality inspections?) Statistics on issues and risks For significant lessons it may be useful to provide additional details on: Event Effect (e.g. positive/negative financial impact) Causes/trigger Whether there were any early-warning indicators Recommendations Whether the triggered event was previously identified as a risk (threat or opportunity). A.15.3 Derivation 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) Communication Management Strategy (for the distribution list). A.15.4 format and presentation A Lessons Report can take a number of formats, including: Oral report to the Project Board (could be in A.15.2 Composition Executive summary Scope of the report (e.g. stage or project) A review of what went well, what went badly person or over the phone) Presentation at a progress review (physical and any recommendations for corporate or programme management consideration. In particular: Project management method (including the tailoring of PRINCE2) meeting or conference call) Document or email issued to the Project Board Entry in a project management tool.