The Project Product Description is a fundamental component within the PRINCE2 7 Plans practice that defines what the project must deliver. It serves as the cornerstone document that describes the principal output or final deliverable that the project aims to create.
This document is created during…The Project Product Description is a fundamental component within the PRINCE2 7 Plans practice that defines what the project must deliver. It serves as the cornerstone document that describes the principal output or final deliverable that the project aims to create.
This document is created during the Starting Up a Project process and refined during the Initiating a Project process. It provides essential clarity about what the project will produce, ensuring all stakeholders share a common understanding of the expected outcome.
Key elements typically included in a Project Product Description are:
1. Title - A clear name identifying the product
2. Purpose - Why the product is needed and what problem it solves
3. Composition - What elements or components make up the product
4. Derivation - Source materials, information, or existing products from which the final product will be developed
5. Development skills required - The expertise and competencies needed to create the product
6. Customer quality expectations - What the customer anticipates in terms of quality standards and performance
7. Acceptance criteria - Measurable definitions that must be satisfied for the product to be accepted by the customer
8. Project-level quality tolerances - Permitted deviations from quality specifications
9. Acceptance method - How the finished product will be verified and approved
10. Acceptance responsibilities - Who has authority to confirm the product meets requirements
The Project Product Description links closely to the Business Case, as it defines what will be delivered to achieve the expected benefits. It also forms the basis for creating the product breakdown structure and subsequent Product Descriptions for individual products within the project.
By establishing clear acceptance criteria early, the Project Product Description helps prevent scope creep and provides a definitive reference point for determining when the project has successfully completed its objectives.
Project Product Description - PRINCE2 Foundation V7 Guide
What is a Project Product Description?
The Project Product Description (PPD) is a critical management product within PRINCE2 that defines the overall project output - what the project will deliver as its final product. It describes the main deliverable that the project exists to create, including its purpose, composition, quality expectations, and acceptance criteria.
Why is it Important?
The Project Product Description is essential for several reasons:
• Clarity of Purpose: It ensures everyone understands exactly what the project must deliver • Quality Foundation: It establishes the quality expectations and acceptance criteria from the start • Scope Management: It helps prevent scope creep by clearly defining what is included • Customer Alignment: It confirms that the project output will meet the customer's needs • Acceptance Basis: It provides the foundation for project closure and acceptance
How Does it Work?
The Project Product Description is created during the Starting up a Project process and refined during Initiating a Project. It contains:
• Title: The name of the project's final product • Purpose: Why the product is needed and what it will achieve • Composition: What major components make up the product • Derivation: Sources from which the product is derived • Development Skills Required: Skills needed to create the product • Customer's Quality Expectations: What quality standards the customer expects • Acceptance Criteria: Measurable definitions of what constitutes acceptable delivery • Acceptance Method: How acceptance will be confirmed • Acceptance Responsibilities: Who is responsible for accepting the product
The PPD is owned by the Executive and is used throughout the project to maintain focus on the ultimate deliverable.
Exam Tips: Answering Questions on Project Product Description
1. Remember the Timing: The PPD is created in Starting up a Project and refined in Initiating a Project - this is frequently tested
2. Know the Difference: Do not confuse the Project Product Description with individual Product Descriptions. The PPD describes the overall project output, while Product Descriptions describe individual products within the product breakdown structure
3. Customer Quality Expectations vs Acceptance Criteria: Quality expectations are general statements from the customer; acceptance criteria are specific, measurable definitions derived from those expectations
4. Link to Plans Practice: The PPD is part of the Plans practice because it defines the ultimate product that all planning activities work towards
5. Executive Ownership: Remember that the Executive is responsible for the PPD as it relates to the business justification
6. Look for Keywords: Questions may use terms like 'final deliverable', 'project output', 'acceptance criteria', or 'quality expectations' as clues pointing to the PPD
7. Purpose Questions: If asked about documenting what the customer expects to receive, the answer involves the Project Product Description
8. Acceptance Focus: Questions about how project completion is determined or what basis acceptance uses often relate to the PPD's acceptance criteria