PRINCE2 Glossary of Terms - L to O

L - O - Lesson Log to output

This is an A-Z glossary of terms, from the 2009 edition. PRINCE2® is a registered trade mark of AXELOS Limited. View the Agile Dictionary. Full ITIL glossary of terms. See also Risk Management Dictionary.

A - accept to avoid | B - baseline to Business Case | C - centre of excellence to customer's quality expectations | D - Daily Log to DSDM Atern | E - embedding (PRINCE2) to exploit | F - H - fallback to host site | I - impact to Issue Report | L - 0 - Lesson Log to output | P - performance targets to Project Support | Q - quality to quality tolerance | R - records to role description | S - schedule to supplier | T - tailoring to trigger | U - W - user acceptance to Work Package

Lessons Log

An informal repository for lessons that apply to this project or future projects.

Download a Lessons Log - Template in Mind map, Word or PDF format

Lessons Report

A report that documents any lessons that can be usefully applied to other projects. The purpose of the report is to provoke action so that the positive lessons from a project become embedded in the organization’s way of working and that the organization is able to avoid the negative lessons on future projects.

Download a Lessons Report - Template in Mind map, Word or PDF format

logs

Informal repositories managed by the Project Manager that do not require any agreement by the Project Board on their format and composition. PRINCE2 has two logs: the Daily Log and the Lessons Log.

management product

A product that will be required as part of managing the project, and establishing and maintaining quality (for example, Highlight Report, End Stage Report etc.). The management products stay constant, whatever the type of project, and can be used as described, or with any relevant modifications, for all projects. There are three types of management product: baselines, records and reports.

management stage

The section of a project that the Project Manager is managing on behalf of the Project Board at any one time, at the end of which the Project Board will wish to review progress to date, the state of the Project Plan, the Business Case and risks, and the next Stage Plan in order to decide whether to continue with the project.
A significant event in a plan’s schedule, such as completion of key Work Packages, a technical stage, or a management stage. Read more on project milestones.

off-specification

Something that should be provided by the project, but currently is not (or is forecast not to be) provided. This might be a missing product or a product not meeting its specifications. It is one type of issue.

operational and maintenance acceptance

A specific type of acceptance by the person or group who will support the product once it is handed over into the operational environment.

outcome

The result of change, normally affecting real-world behaviour and/or circumstances. Outcomes are desired when a change is conceived. They are achieved as a result of the activities undertaken to effect the change.

output

A specialist product that is handed over to a user(s). Note that management products are not outputs but are created solely for the purpose of managing the project.


Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS
 
 
Microsoft Project Templates


Support stakeholdermap.com
If you liked this page, feel free to recommend us!