PRINCE2 Glossary of Terms
U - W - user acceptance to Work Package
This is an A-Z glossary of terms, from the 2009 edition. PRINCE2® is a registered trade mark of AXELOS Limited.
- accept to avoid
- baseline to Business Case
- centre of excellence to customer's quality expectations
- Daily Log to DSDM Atern
- embedding (PRINCE2) to exploit
| F - H
- fallback to host site
- impact to Issue Report
| L - 0
- Lesson Log to output
- performance targets to Project Support
- quality to quality tolerance
- records to role description
- schedule to supplier
- tailoring to trigger
| U - W
- user acceptance to Work Package
A specific type of acceptance by the person or group who will use the product once it is handed over into the operational environment.
The person or group who will use one or more of the project’s products.
A variation on a baselined product. For example, an operations manual may have an English variant and a Spanish variant.
A specific baseline of a product. Versions typically use naming conventions that enable the sequence or date of the baseline to be identified. For example, Project Plan
version 2 is the baseline after Project Plan version 1.
A development approach that is linear and sequential with distinct goals for each phase of development. Once a phase of development is completed, the development proceeds to the next phase and earlier phases are not revisited (hence the analogy that water flowing down a mountain cannot go back).
The set of information relevant to the creation of one or more products. It will contain a description of the work, the Product Description
(s), details of any constraints on production, and confirmation of the agreement between the Project Manager and the person or Team Manager who is to implement the Work Package that the work can be done within the constraints.
Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS