The Product-based Planning technique is a distinctive framework within the PRINCE2 7 Plans practice that prioritizes deliverables over activities. The core philosophy is that a project team cannot effectively plan the work (activities) until they clearly define exactly what must be produced. This a…The Product-based Planning technique is a distinctive framework within the PRINCE2 7 Plans practice that prioritizes deliverables over activities. The core philosophy is that a project team cannot effectively plan the work (activities) until they clearly define exactly what must be produced. This approach minimizes the risk of scope creep and ensures a shared understanding of quality requirements from the outset.
The technique comprises four sequential steps:
1. Write the Project Product Description: This defines the final output of the project. It establishes the customer's quality expectations and acceptance criteria, acting as the ultimate target.
2. Create the Product Breakdown Structure (PBS): This is a hierarchical diagram that decomposes the project product into its constituent parts. It breaks down the scope into major products and sub-products, identifying all necessary management, specialist, and quality products required for success.
3. Write Product Descriptions: For the component products identified in the PBS, detailed descriptions are drafted. These specify the composition, format, quality criteria, and tolerances for each item, providing the team with precise instructions on what 'finished' looks like.
4. Create the Product Flow Diagram (PFD): This diagram maps the sequence in which products must be developed. It highlights dependencies, showing which products must exist before others can be created, and identifies any external products required.
Only after these four steps are complete does the Project Manager move to activity-based planning (identifying activities, estimating resources, and scheduling). By enforcing this sequence, PRINCE2 7 ensures that plans are realistic, complete, and aligned with the principle of 'Focus on Products'.
Guide to Product-based Planning Technique (PRINCE2 Practitioner v7)
Introduction The Product-based Planning Technique is a defining characteristic of PRINCE2. Unlike traditional methods that focus immediately on activities (what we do), PRINCE2 focuses on products (what we deliver). You cannot successfully plan how to do the work until you clearly define what the work is.
Why is it Important? 1. Scope Definition: It prevents scope creep by strictly defining the project deliverables. 2. Communication: It provides a clear visual representation of the project scope (via the Product Breakdown Structure) which is easier for stakeholders to understand than a Gantt chart. 3. Quality: It forces the project team to agree on acceptance criteria and quality specifications before work begins.
How it Works: The 4 Steps The technique is iterative, but generally follows this flow:
1. Write the Project Product Description (PPD): Defines the final output of the project. It includes the customer's quality expectations and acceptance criteria.
2. Create the Product Breakdown Structure (PBS): A hierarchical tree diagram. The main project product is at the top, decomposed into major products, and further into component products. It organizes the project into manageable components.
3. Write Product Descriptions: For the required component products, a detailed description is created. This includes the composition, quality criteria, and quality methods.
4. Create the Product Flow Diagram (PFD): This defines the sequence of development. It shows which products must be completed before others can begin (dependencies). This diagram is essential for calculating the Critical Path later.
Exam Tips: Answering Questions on Product-based Planning Technique In the PRINCE2 Practitioner exam, you will likely face 'Additional Information' scenarios where you must critique a PBS, a PFD, or a Product Description.
Top Strategies for Success:
1. The Noun vs. Verb Rule (Crucial): A Product Breakdown Structure (PBS) must contain Products (Nouns), not Activities (Verbs). Incorrect: 'Installing the Server' Correct: 'Installed Server' If an exam question asks you to identify an error in a PBS, look immediately for activity-based language (words ending in -ing).
2. External Products: In a Product Flow Diagram (PFD), look for External Products. These are inputs required for the project but created outside the project's scope (e.g., 'Standard Operating Procedures' provided by HR). If the project team does not create it, it should be marked as external (often an ellipse shape). An error often involves listing an external product as a deliverable to be created.
3. The 'Is-a-part-of' Check: For the PBS, use the 'is-a-part-of' test. If product B is below product A, B must be physically part of A. If you are building a 'House', a 'Kitchen' is a correct sub-product. However, 'Architect' is incorrect, because the Architect is a resource, not a component of the house.
4. Quality Criteria Specificity: When critiquing Product Descriptions, ensure Quality Criteria are specific and measurable. Criteria like 'Good quality' or 'User friendly' are poor because they are subjective. Criteria like 'Load time under 0.5 seconds' are good.
5. Completeness: Check if the PBS is complete based on the Scenario. If the scenario mentions a Training Manual is required, but it is missing from the PBS, that is a reportable error.