'Focus on Products' is one of the seven PRINCE2 principles, and in an Agile context it takes on particular significance. This principle emphasises that a project should concentrate on defining and delivering products (outputs) rather than merely focusing on activities or tasks. In PRINCE2 Agile, un…'Focus on Products' is one of the seven PRINCE2 principles, and in an Agile context it takes on particular significance. This principle emphasises that a project should concentrate on defining and delivering products (outputs) rather than merely focusing on activities or tasks. In PRINCE2 Agile, understanding what needs to be delivered—the products—is fundamental to successful collaboration between traditional project management and agile delivery approaches. In Agile, this principle aligns naturally because agile frameworks like Scrum and Kanban are inherently product-centric, focusing on delivering working increments of value to customers frequently. The key connection is that PRINCE2 uses Product Descriptions to define quality criteria, purpose, and acceptance conditions, while agile teams break these products down into features and user stories managed within backlogs. A critical aspect in the Agile context is the concept of 'fixing' and 'flexing'. PRINCE2 Agile encourages fixing time and cost while flexing scope and features. Focusing on products supports this by clearly identifying which product features are essential (must-haves) versus those that can be adjusted, often using prioritisation techniques such as MoSCoW (Must have, Should have, Could have, Won't have). This ensures the most valuable products are delivered first. By focusing on products, teams maintain clarity on what 'done' means, agree on quality criteria upfront, and enable effective progress measurement through delivered, working increments rather than documentation or effort expended. This reduces misunderstandings and supports collaborative working. Furthermore, this principle helps bridge the gap between the directing and managing layers (PRINCE2) and the delivering layer (agile teams), ensuring everyone understands the outcomes required. Ultimately, 'Focus on Products' in an Agile context ensures that value delivery remains central, quality expectations are clear, prioritisation is effective, and the project consistently delivers usable products that meet customer needs while embracing agile flexibility and iterative development.
Focus on Products in an Agile Context
Focus on Products in an Agile Context
The PRINCE2 principle Focus on Products is one of the seven principles that remain fully applicable when PRINCE2 is tailored for an agile environment. Understanding how this principle blends with agile ways of working is essential for the PRINCE2 Agile Foundation exam.
Why It Is Important
Focusing on products keeps everyone aligned on what needs to be delivered and to what quality, rather than getting lost in the activity of doing work. In an agile context this is critical because agile teams work iteratively and incrementally, and without clear product definitions there is a risk of building the wrong thing or delivering something that does not meet the customer's needs.
This principle underpins one of the most important ideas in PRINCE2 Agile: fixing time and cost, and flexing what is delivered (scope and quality tolerances). To flex scope sensibly, you must first understand your products and their priorities. Focusing on products enables you to protect the essential features (the 'must haves') while allowing lower-priority features (the 'won't haves for now') to flex.
What It Is
The Focus on Products principle states that a PRINCE2 project focuses on the definition and delivery of products, in particular their quality requirements. A product is any input or output, whether tangible or intangible, that can be described in advance, created and tested.
In an agile context, products are defined through techniques such as: • Product descriptions that set out purpose, composition and quality criteria. • User stories that capture requirements from the user's perspective (e.g. 'As a... I want... so that...'). • Epics that group larger requirements. • Definition of Done which clarifies quality expectations for increments. • Prioritisation techniques such as MoSCoW (Must have, Should have, Could have, Won't have this time).
How It Works
1. Product-based planning is used to identify the products required and their quality criteria. This provides the framework within which agile delivery takes place.
2. Prioritisation ensures the team knows which products or features are most valuable, enabling scope to flex without compromising the core deliverable.
3. Iterative and incremental delivery means products are built and reviewed in small increments (through sprints/timeboxes), with frequent feedback to confirm they meet quality criteria.
4. Acceptance criteria and Definition of Done confirm that each product is fit for purpose before being accepted.
5. Focusing on outcomes and benefits, not just outputs, ensures that delivered products actually deliver value to the customer.
By combining product focus with agile techniques, PRINCE2 Agile ensures teams deliver working, high-quality products frequently while still maintaining control over scope, time and cost.
Exam Tips: Answering Questions on Focus on Products in an Agile Context
• Remember that all seven PRINCE2 principles, including Focus on Products, remain unchanged and must not be tailored away in an agile context.
• Link this principle to flexing what is delivered - you can only flex scope safely if products are clearly defined and prioritised.
• Associate product focus with quality criteria and the Definition of Done; questions may test whether you understand that quality expectations must be clear.
• Know that agile techniques such as user stories, epics, MoSCoW prioritisation, and product backlogs support (not replace) product-based planning.
• Watch for distractors suggesting agile means 'no documentation' or 'no product definition' - PRINCE2 Agile still requires products to be defined.
• Emphasise outcomes and benefits, not just delivering features, when a question asks about the purpose of focusing on products.
• For scenario questions, identify whether the issue stems from unclear or unprioritised products, and select answers that restore product focus.
• Keep answers grounded in the definition: a product is something that can be described in advance, created and tested.
