This is an A-Z glossary of terms, from the 2009 edition. PRINCE2® is a registered trade mark of AXELOS Limited. <
centre of excellence
A corporate coordinating function for portfolios, programme
s and projects providing standards, consistency of methods and processes, knowledge management, assurance and training.
A person or group to which the Project Board may delegate responsibility for the consideration of requests for change or off-specifications. The Change Authority may be given a change budget and can approve changes within that budget.
The money allocated to the Change Authority available to be spent on authorized requests for change.
The procedure that ensures that all changes that may affect the project’s agreed objectives are identified, assessed and either approved, rejected or deferred.
A team-level, time-driven review of progress.
A progress report of the information gathered at a checkpoint, which is given by a team to the Project Manager
and which provides reporting data as defined in the Work Package
Advice from the Project Board to inform all stakeholders and the host sites that the project resources can be disbanded and support services, such as space, equipment and access, demobilized. It should indicate a closure date for costs to be charged to the project.
A recommendation prepared by the Project Manager
for the Project Board to send as a project closure notification when the board is satisfied that the project can be closed.
Communication Management Strategy
A description of the means and frequency of communication between the project and the project’s stakeholders.
An off-specification that is accepted by the Project Board without corrective action.
An entity that is subject to configuration management. The entity may be a component of a product, a product, or a set of products in a release.
Configuration Item Record
A record that describes the status, version and variant
of a configuration item, and any details of important relationships between them.
Technical and administrative activities concerned with the creation, maintenance and controlled change of configuration throughout the life of a product.
Configuration Management Strategy
A description of how and by whom the project’s products will be controlled and protected.
configuration management system
The set of processes, tools and databases that are used to manage configuration data. Typically, a project will use the configuration management system of either the customer or supplier organization.
The restrictions or limitations that the project is bound by.
Something that is held in reserve typically to handle time and cost variances, or risks. PRINCE2
does not advocate the use of contingency because estimating variances are managed by setting tolerances
, and risks are managed through appropriate risk responses
(including the fallback response that is contingent on the risk occurring). See also Contingency Plan
and Contingency Planning
corporate or programme standards
A set of actions to resolve a threat to a plan’s tolerances or a defect in a product.
The permissible deviation in a plan’s cost
that is allowed before the deviation needs to be escalated to the next level of management. Cost tolerance is documented in the respective plan. See also ‘tolerance’.
The person or group who commissioned the work and will benefit from the end results.
customer’s quality expectations
Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS