The PRINCE2 principle 'Focus on Products' is fundamental to the methodology’s success, distinguishing it from traditional project management approaches by shifting the perspective from 'what activities we need to do' to 'what we need to deliver.' In the context of PRINCE2 7, a project is defined as…The PRINCE2 principle 'Focus on Products' is fundamental to the methodology’s success, distinguishing it from traditional project management approaches by shifting the perspective from 'what activities we need to do' to 'what we need to deliver.' In the context of PRINCE2 7, a project is defined as a temporary organization created for the purpose of delivering one or more business products according to an agreed business case. Without a clear definition of these products, a project risks scope creep, acceptance disputes, and a failure to realize business value.
Applying this principle requires that products are identified and defined before determining the activities, dependencies, and resources required to produce them. This is operationalized through Product-Based Planning. The central artifact in this process is the Product Description. A Product Description acts as a clear agreement between the Project Manager and the creator (or Team Manager), detailing the composition, derivation, format, quality criteria, and quality tolerances of the output. It ensures the team understands exactly what to build and the user understands exactly what to expect.
For a Practitioner, applying this principle means resisting the urge to jump straight into Gantt charts or activity lists. Instead, they must ensure that the User's Quality Expectations and Acceptance Criteria are captured early. This focus delineates the boundaries of the project; if a requirement cannot be mapped to a specific product, it is likely outside the scope. Ultimately, focusing on products provides a common language for the Project Board, users, and suppliers, ensuring everyone visualizes the same final result. This minimizes rework, controls costs, and ensures the final deliverables are fit for purpose and capable of generating the desired benefits.
Applying the 'Focus on Products' Principle in PRINCE2 v7
What is 'Focus on Products'? The 'Focus on Products' principle is a core philosophy of PRINCE2 stating that a successful project is output-oriented rather than activity-oriented. It asserts that you must clearly define what you are going to deliver (the products) before you determine how, when, and by whom (the activities) it will be done. In PRINCE2, a 'product' encompasses any input or output, whether tangible (e.g., a physical machine) or intangible (e.g., a culture change or a report).
Why is it Important? Applying this principle is critical to prevent the 'activity trap'—where people are busy working but not necessarily producing what is required. Its importance lies in: 1. Clarifying Scope: It ensures a common understanding between the customer and supplier regarding what will be delivered. 2. Reducing Rework: By agreeing on the Product Description and Quality Criteria upfront, the risk of delivering the wrong thing is minimized. 3. Accurate Estimates: It is easier to estimate time and resources for a clearly defined output than for a vague list of activities.
How it Works This principle is implemented primarily through the Product-Based Planning technique. The workflow generally follows these steps: - Project Product Description: Created early (Starting Up a Project) to define the final output and the customer's quality expectations. - Product Breakdown Structure (PBS): A hierarchical decomposition of the project product into major products and sub-products. - Product Descriptions: Detailed definitions for every significant product. Crucially, these must include measurable Quality Criteria so the team knows exactly what constitutes a 'finished' product. - Product Flow Diagram: Identifies dependencies and the sequence in which products must be created.
Exam Tips: Answering Questions on Focus on Products In the PRINCE2 Practitioner exam, questions often present a scenario and ask you to identify if this principle is being upheld or violated, or how to tailor it.
Key strategies for answering: 1. Look for the 'What' before the 'How': If a scenario describes a Project Manager listing tasks (activities) before identifying the deliverables, the principle is being compromised. 2. The Product Description is King: If work commences without a Product Description (or equivalent definition like a User Story), or if the description lacks Quality Criteria, the principle is not being met. 3. Check for Understanding: A common exam scenario involves a dispute over the quality of a deliverable. If the dispute arises because quality was never agreed upon in writing, the 'Focus on Products' principle was neglected. 4. Tailoring Context: In an Agile environment, look for 'User Stories' or 'Epics' as valid substitutes for formal Product Descriptions. As long as the output and acceptance criteria are defined, the principle is being applied correctly. 5. Beware of Gold Plating: If the scenario mentions the team adding extra features to 'delight' the customer that were not in the Product Description, this is a violation. PRINCE2 requires delivering exactly what was agreed—no more, no less.