In the context of PRINCE2 7, the Product Register is a critical management product that serves as the central inventory for all products (deliverables) created during a project. Within the Quality Practice, it acts as the backbone of configuration management, ensuring that the project team maintain…In the context of PRINCE2 7, the Product Register is a critical management product that serves as the central inventory for all products (deliverables) created during a project. Within the Quality Practice, it acts as the backbone of configuration management, ensuring that the project team maintains control over product versions and their specific status throughout the project lifecycle.
Unlike the Quality Register, which tracks the schedule and results of quality activities (such as tests or reviews), the Product Register focuses on the artifacts themselves. It lists every identified product, assigns a unique identifier, and records its current state—ranging from 'Draft' to 'Quality Review,' and finally to 'Approved' or 'Handed Over.' This status tracking is essential for Quality because a product is not deemed complete in PRINCE2 until it has satisfied its defined quality criteria and has been formally baselined. This mechanism prevents unauthorized changes and ensures that the team is always working on the correct version of a deliverable.
Typically established during the 'Initiating a Project' process and maintained by Project Support, the Product Register provides the Project Manager with an objective measure of progress. Rather than relying on subjective percentage estimates, progress is measured by the number of products that have officially moved to an 'Approved' status in the register. It facilitates strict configuration control by ensuring that only approved versions are used as the basis for future work. Furthermore, it provides a necessary audit trail by referencing the specific Quality Records associated with each product version. Ultimately, the Product Register ensures that the project delivers exactly what was agreed upon, maintaining the integrity of the project's scope and quality standards.
Mastering the Product Register in PRINCE2 Practitioner v7
Introduction to the Product Register The Product Register is a vital management product within PRINCE2, sitting at the intersection of the Quality practice and the Issues (Configuration Management) practice. It acts as the central inventory for the project, ensuring that the Project Manager knows exactly what is being built, its current status, and where it is located.
What is the Product Register? Simply put, the Product Register is a list of all the products (deliverables) that the project will produce. However, it is more than just a list; it is a dynamic record that tracks the lifecycle of every product. It contains details such as the product ID, title, version number, current status (e.g., drafted, quality checked, approved), and the individuals responsible for creating or reviewing it.
Why is it Important? Without a Product Register, a project loses control over its deliverables. It is crucial because: 1. Status Tracking: It provides an up-to-date summary of progress based on product completion rather than just activity completion. 2. Version Control: It ensures everyone is working on or reviewing the correct version of a product. 3. Quality Audit Trail: It records when quality checks were planned, when they happened, and what the result was, serving as evidence for quality assurance.
How it Works The Product Register is typically established during the Initiating a Project process. As the project moves through its stages: 1. Creation: New products identified in Stage Plans are added to the register. 2. Update: As products are developed, tested, and approved, their status is updated by Project Support (or the Project Manager). 3. Baselining: Once a product is approved, the register reflects its baselined status, meaning any future changes require formal change control.
Exam Tips: Answering Questions on Product Register When facing Practitioner scenarios regarding the Product Register, keep these specific tips in mind:
1. Identify the 'Source of Truth': If a question asks how to determine the current status of a deliverable (e.g., 'Has the User Manual been tested?'), the answer is almost always the Product Register. Do not confuse it with the Quality Register, which details the specific quality activities, although they are closely linked.
2. Configuration Management: Remember that the Product Register is a tool for configuration management. If a scenario involves lost files, confusion over version numbers, or using the wrong specifications, the solution often involves checking or fixing the Product Register.
3. Roles and Responsibilities: Project Support usually maintains the register. If a question asks who updates the status after a Quality Review, look for Project Support. The Project Manager is accountable, but Support does the administration.
4. Tailoring: In a Practitioner exam context, look for evidence of how the register is tailored. Is it a spreadsheet? A tool like Jira? The format doesn't matter, but the function (tracking status and version) does.
5. Differentiating from the Issue Register: The Product Register tracks planned products. The Issue Register tracks problems or changes. If a product fails a quality check, the result is recorded in the Product Register (and potentially the Quality Register), but if fixing it requires extra time/money beyond tolerance, it becomes an Issue.