Product Descriptions
Product Descriptions are detailed specifications for the products to be delivered by a project. In PRINCE2, a product is anything that must be created as part of the project, whether it's tangible (like a building) or intangible (like a service or change). Each Product Description defines what the product is, its purpose, composition, derivation, format, quality criteria, and quality methods. The quality criteria within a Product Description are particularly important as they establish measurable standards against which the product will be verified, ensuring it is fit for purpose. Product Descriptions are created during planning activities and are used throughout the project to guide development and testing. They help to establish a clear understanding between stakeholders about what will be delivered, reducing the risk of misinterpretation or scope creep. Product Descriptions are living documents that may be refined as the project progresses, especially if approved changes impact the product's specifications. They play a crucial role in quality management by setting explicit acceptance criteria that must be met before a product can be approved. By defining quality expectations at the product level, PRINCE2 ensures that quality is built into the project's deliverables from the ground up, rather than being assessed only at the end. Product Descriptions also support effective risk management by helping to identify potential quality risks early in the development process. They provide a baseline for quality inspections and acceptance procedures, making it clear to all involved what constitutes a successful delivery. This level of detail in defining products contributes significantly to PRINCE2's emphasis on delivering products that meet business needs.
PRINCE2 Foundation: Product Descriptions Guide
Understanding Product Descriptions in PRINCE2
What are Product Descriptions?
Product Descriptions in PRINCE2 are documented definitions of a project's products, detailing the purpose, composition, derivation, quality criteria, and quality methods for each product. They serve as a contract between the project and stakeholders about what will be delivered.
A Product Description typically includes:
- Product title and identifier
- Purpose of the product
- Composition (what the product contains)
- Derivation (source materials or dependencies)
- Format and presentation
- Development skills required
- Quality criteria (measurable standards)
- Quality methods (how quality will be checked)
- Quality responsibilities (who checks quality)
Why are Product Descriptions important?
Product Descriptions are crucial because they:
1. Establish clear expectations - They create a shared understanding between all parties about what will be delivered
2. Enable quality planning - They define quality criteria and methods upfront
3. Support effective management - They provide a basis for planning, estimating, and resource allocation
4. Facilitate acceptance - They provide clear criteria for determining when a product is complete
5. Reduce scope creep - They clearly define boundaries of what will be delivered
How Product Descriptions work in practice
Product Descriptions are developed early in the project and refined throughout. They function as:
- Planning tools: Used during planning to estimate effort and resources
- Communication tools: Help team members understand what they're creating
- Control tools: Provide criteria for quality checks and acceptance
- Documentation: Serve as part of the project's configuration management
The Project Manager is responsible for ensuring Product Descriptions exist for all products, though specialists may help create them. They're typically created during the Initiating a Project process and reviewed during stage planning.
Exam Tips: Answering Questions on Product Descriptions
1. Remember the purpose: Product Descriptions define what a product should be and how its quality will be checked
2. Know the components: Be familiar with all elements (purpose, composition, derivation, format, quality criteria, etc.)
3. Understand the relationship to other PRINCE2 elements:
- They support the Quality Theme
- They're created during Initiating a Project
- They're referenced in Work Packages
- They guide acceptance in the Controlling a Stage process
4. Focus on quality aspects: Questions often test your understanding of how Product Descriptions support quality management
5. Identify responsibilities: Know who creates, approves, and uses Product Descriptions
6. Differentiate between Project Product Description (for the final deliverable) and Product Descriptions (for individual products)
7. Look for practical applications in scenario-based questions - how Product Descriptions should be used in given situations
8. Connect to Benefits: Understand how quality criteria in Product Descriptions relate to benefits realization
When answering exam questions, always relate Product Descriptions back to their primary purpose: defining what products should look like and establishing measurable quality criteria to ensure they meet stakeholder expectations.
Go Premium
PRINCE2 Foundation Preparation Package (2025)
- 1825 Superior-grade PRINCE2 Foundation practice questions.
- Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
- Unlock Effortless PRINCE2 Foundation preparation: 5 full exams.
- 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
- Bonus: If you upgrade now you get upgraded access to all courses
- Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!