In PRINCE2 7, the Product Description is a critical management product that embodies the 'Focus on Products' principle. It acts as a blueprint, defining the purpose, composition, derivation, and quality requirements of a product before it is created. Its primary goal is to ensure that the project t…In PRINCE2 7, the Product Description is a critical management product that embodies the 'Focus on Products' principle. It acts as a blueprint, defining the purpose, composition, derivation, and quality requirements of a product before it is created. Its primary goal is to ensure that the project team and stakeholders share a unified understanding of what is to be delivered, thereby preventing scope creep and acceptance disputes.
From the perspective of Quality Practice, the Product Description is the central mechanism for quality control. It translates the customer’s high-level Quality Expectations into specific, measurable Quality Criteria. For a Practitioner, assessing a Product Description involves ensuring these criteria are objective (e.g., 'weighs less than 5kg') rather than subjective (e.g., 'lightweight'). If the criteria are ambiguous, the product cannot be effectively tested or approved.
A complete Product Description includes several key sections: the Purpose (why it is needed), Composition (its constituent parts), Derivation (source materials), Format and Presentation, and Development Skills required. Crucially, it specifies the Quality Method (how it will be checked, such as a test or inspection), Quality Skills (who will check it), and Quality Tolerance (allowable deviation ranges).
In practice, the Product Description supports Product-Based Planning. It allows the Project Manager to estimate the effort required for both creation and quality verification accurately. During the 'Managing Product Delivery' process, it serves as the definitive specification for the team building the product. Once the product is complete, the Quality Reviewers use the Product Description’s criteria to verify fitness for purpose. Without this document, quality becomes a matter of opinion rather than fact, significantly increasing project risk.
Mastering the Product Description in PRINCE2 Practitioner v7
What is a Product Description? In PRINCE2, the Product Description is a critical management product used to define the specific nature, purpose, function, and appearance of a product. It serves as the core of the 'Focus on Products' principle. It ensures that the people building the product (the suppliers/teams) and the people requiring the product (the users) have a shared, detailed understanding of what constitutes a successful delivery.
Why is it Important? Without a formal Product Description, quality is subjective. What the supplier considers 'done' might not match the user's expectation. It provides: 1. Clarity: It prevents scope creep by defining boundaries. 2. Measurability: It defines the Quality Criteria against which the product will be tested. 3. Basis for Planning: You cannot estimate time or cost accurately without understanding the detailed composition and quality requirements defined here.
Key Components of a Product Description When analyzing or creating this document, look for these fields: - Purpose: Who is the product for and why is it needed? - Composition: The components that make up the product (e.g., for a 'Chair', composition includes legs, seat, back). - Derivation: The source materials needed to create the product (e.g., designs, legal standards, prototypes). Note: This is different from composition. - Format and Presentation: The medium or appearance (e.g., A4 PDF, physical prototype). - Development Skills: The skills required to build it. - Quality Criteria: Specific, measurable metrics the product must meet (e.g., 'Must support 100kg weight'). - Quality Tolerance: The allowable range for the criteria (e.g., '100kg +/- 5kg'). - Quality Method: How the criteria will be checked (e.g., Stress test, Visual inspection). - Quality Responsibilities: Who produces, reviews, and approves the product.
How to Answer Questions Regarding Product Descriptions In the Practitioner exam, you are often asked to analyze a Product Description based on a scenario or to identify errors within one. Use the following logic:
1. The 'Vague Criteria' Trap The most common exam issue is subjective Quality Criteria. If you see terms like 'Good quality', 'User friendly', or 'Robust', these are incorrect because they cannot be proven. Correct criteria must be specific and measurable (e.g., 'Login completes in under 2 seconds' or 'Spell-checked with zero errors').
2. Composition vs. Derivation Exam questions often mix these up. Remember: - Composition = Ingredients (What is IN the product). - Derivation = Recipe/Sources (What you used to make it, but isn't inside it). If a scenario lists 'Safety Standards' under Composition, it is wrong; standards are Derivation.
3. Method Must Match Criteria Check if the Quality Method is capable of testing the Criteria. If the criterion is 'Waterproof', a 'Visual Inspection' is a poor method; an 'Immersion Test' is the correct method.
4. Project Product Description (PPD) vs. Product Description (PD) Ensure you are looking at the right document. The PPD is for the final output of the project (created in Starting a Project). A standard PD is for component/intermediate products (created during Planning). If the question asks about the final deliverable, ensure it includes Customer's Quality Expectations and Acceptance Criteria, which are specific to the PPD.