PRINCE2 Glossary of Terms - C

C - centre of excellence to customer's quality expectations

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.

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

centre of excellence

A corporate coordinating function for portfolios, programmes and projects providing standards, consistency of methods and processes, knowledge management, assurance and training.

Change Authority

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.

change budget

The money allocated to the Change Authority available to be spent on authorized requests for change.

change control

The procedure that ensures that all changes that may affect the project’s agreed objectives are identified, assessed and either approved, rejected or deferred.

checkpoint

A team-level, time-driven review of progress.

Checkpoint Report

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.

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

closure notification

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.

closure recommendation

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.

Download a Communication Management Strategy - template in Mind map, Word or PDF format

concession

An off-specification that is accepted by the Project Board without corrective action.

configuration item

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.

Download a Configuration Item Record - Template in Mind map, Word or PDF format

configuration management

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.

Download a Configuration Management Strategy - Template in Mind map, Word or PDF format

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.

constraints

The restrictions or limitations that the project is bound by.

contingency

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

These are over-arching standards that the project must adhere to. They will influence the four project strategies (Communication Management Strategy, Configuration Management Strategy, Quality Management Strategy and Risk Management Strategy) and the project controls.

corrective action

A set of actions to resolve a threat to a plan’s tolerances or a defect in a product.

cost tolerance

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’.

customer

The person or group who commissioned the work and will benefit from the end results.

customer’s quality expectations

A statement about the quality expected from the project product, captured in the Project Product Description.


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!