Konfigurationselement Protokollvorlage

Aus PRINCE2 wiki Deutsche
Wechseln zu: Navigation, Suche

Download Configuration Item Record Template

Click here to download


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.

Advice The Configuration Item Record 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 Configuration Item Records can take a number of formats, including: Document, spreadsheet or database; Entry in a project management tool.

The following quality criteria should be observed:

  • The records reflect the status of the products accurately
  • The records are kept together in a secure location
  • Version numbers match the actual products
  • Configuration Item Records show products’ version histories
  • A process exists by which the Configuration Item Records are defined and updated.

Note: Here follows a suggested list of components for each Configuration Item Record. The composition of a Configuration Item Record will be defined in the project’s Configuration Management Strategy so please check to see if the default list recommended here has been altered.

Unique Identifier
Project identifier[1] Item identifier[2] Current version[3]

Item Title

(The description of the item (for a product this should be as it appears in the product breakdown structure))

Item Details
Date of last Status Change  
Copy Holders [6]  
Item Type[7]  
Item Attributes[8]  
Product State[12]  
Date Allocated to the producer  
Relationship with other items[16]  
Cross References[17]  
  1. A unique reference
  2. It will typically be a numeric or alpha-numeric value
  3. Typically an alpha-numeric value
  4. The person or group who will take ownership of the product when it is handed over.
  5. Where the item is stored
  6. (if relevant), who currently has the product?
  7. Component, product, release (see section 9.2.2 of the manual)
  8. 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.
  9. When the product will be developed
  10. The person or group who will use the item
  11. As defined by the Configuration Management Strategy, e.g. pending development, in development, in review, approved or handed over
  12. (if used) As defined by the Product Description, e.g. dismantled machinery, moved machinery, reassembled machinery (see section of the manual)
  13. (if used) for example, language variants
  14. The person or team responsible for creating or obtaining the item
  15. For example, in house, or purchased from a third-party company
  16. Those items that: Would be affected if this item changed; or if changed, would affect this item
  17. Issues and risks; or documentation that defines requirements, design, build, production and verification for the item (specifically this will include the Product Description)