Product register

The product register describes how a project will record, track, and control the status of all products required by a plan. It sets out the techniques, standards, responsibilities, and resources needed to ensure that every planned product is monitored from definition to acceptance.

This approach ensures that:

• All products are identified, recorded, and tracked consistently.
• Progress against planned products can be monitored and controlled.
• Variances from expected product status are visible and addressed promptly.
• Product information remains accurate and up to date throughout the project lifecycle.

It covers areas such as:

• Product identification and listing
• Status tracking and updates
• Monitoring progress against plans
• Roles and responsibilities for maintaining the register

Life cycle

The product register is used and updated throughout the project, aligning with PRINCE2’s processes:

1. Starting up a project (SU) – No formal activity takes place, but any early ideas about required products may be noted for use in initiation.
2. Initiating a project (IP) – The project manager creates the product register, based on the agreed product breakdown structure and product descriptions. It is baselined as part of the project initiation documentation.
3. Directing a project (DP) – The project board does not update the register directly but may review it when approving the project initiation documentation or stage plans.
4. Controlling a stage (CS) – The project manager ensures the register is kept up to date as products are developed, reviewed, approved, or rejected. Any variances in product status are logged and, where necessary, escalated.
5. Managing product delivery (MP) – Team managers provide regular product status updates via checkpoint reports. These updates are recorded in the register to reflect progress and highlight any issues with delivery.
6. Managing a stage boundary (SB) – The register is reviewed to confirm that all planned products for the stage have been completed or, if not, are carried forward to the next stage. The updated register forms part of the end stage report.
7. Closing a project (CP) – The final product register confirms acceptance of all required products and records any incomplete or cancelled items, providing a definitive record for project closure.

Contents

A product register will normally include:

• Product identifier: A unique code or reference for each product.
• Dates: Approval date for the product description and acceptance date for the completed product.
• Status: Current state (e.g., in development, under review, accepted) and version number.
• References: Links to related product descriptions or supporting documentation.

Tips

The following tips help you have a better product register:

• Keep it current – Update the product register regularly to reflect the latest product status.
• Link to product descriptions – Make sure every product entry points to its approved product description for reference.
• Track versions – Record version numbers to avoid confusion over which iteration is being reviewed or accepted.
• Integrate with work packages – Ensure the register aligns with assigned work packages so progress reporting is consistent.
• Use it for stage reviews – The register is a key tool during stage boundary assessments to confirm product completion.

—o—

Written by Frank Turley.

If you have questions or doubts after using this wiki, you can ask for help on the Facebook or LinkedIn study groups.