PRINCE2: This is the full PRINCE2 Configuration Item Record Template. Here you can also download this template in MS Word format and other relevant documents: Link
- PRINCE2 Configuration Item Record Template
- PRINCE2 Sample Project from MPLAZA
- PRINCE2 Configuration Item Record Video
- PRINCE2.Wiki Configuration Item Record
- PRINCE2 Sample Project from PRINCE2.site
- PRINCE2 Templates
|Purpose||To provide a record of such information as the history, status, version and variant of each configuration item, and any details of important relationships between them.|
|Contents||The PRINCE2 Configuration Item Record Template should cover the following topics.
|Advice||The PRINCE2 Configuration Item Record Template is derived from the: Configuration Management Strategy; Product breakdown structure; Stage Plan and Work Package; Quality Register, Issue Register and Risk Register.
The set of Configuration Item Records for a project is often referred to as a configuration library.The PRINCE2 Configuration Item Record Template can take a number of formats, including: Document, spreadsheet or database; Entry in a project management tool.The following quality criteria should be observed:
Note: Here follows a suggested list of components for each CPRINCE2 Configuration Item Record Template. The composition of a PRINCE2 Configuration Item Record Template will be defined in the project’s Configuration Management Strategy so please check to see if the default list recommended here has been altered.
|Item Title||(The description of the item (for a product this should be as it appears in the product breakdown structure))|
 The person or group who will take ownership of the product when it is handed over.
 Where the item is stored
 (if relevant), who currently has the product?
 Component, product, release (see section 9.2.2 of the manual)
 As defined by the Configuration Management Strategy. These are used to specify a subset of products when producing a Product Status Account, such as the management stage in which the product is created, the type of product (e.g. hardware/ software), product destination etc.
 When the product will be developed
 The person or group who will use the item
 As defined by the Configuration Management Strategy, e.g. pending development, in development, in review, approved or handed over
 (if used) As defined by the Product Description, e.g. dismantled machinery, moved machinery, reassembled machinery (see section 126.96.36.199 of the manual)
 (if used) for example, language variants
 The person or team responsible for creating or obtaining the item
 For example, in house, or purchased from a third-party company
 Those items that: Would be affected if this item changed; or if changed, would affect this item
 Issues and risks; or documentation that defines requirements, design, build, production and verification for the item (specifically this will include the Product Description)