In PRINCE2 Agile, 'Flexing What Is Delivered' is a core concept that recognizes agile projects should fix time and cost while varying the scope and quality of what is delivered. This is visualized using the Hexagon, which represents the six aspects (performance targets) of a project: Time, Cost, Qu…In PRINCE2 Agile, 'Flexing What Is Delivered' is a core concept that recognizes agile projects should fix time and cost while varying the scope and quality of what is delivered. This is visualized using the Hexagon, which represents the six aspects (performance targets) of a project: Time, Cost, Quality, Scope, Benefits, and Risk. The Hexagon illustrates which aspects are typically fixed and which are flexed in an agile environment. In traditional projects, time and cost often flex when scope is fixed. However, in PRINCE2 Agile, this is reversed: Time and Cost are fixed, and Scope and Quality (specifically the level of quality within acceptable tolerances) are flexed to ensure delivery on time and within budget. Benefits should not be flexed below an acceptable minimum, as they represent the project's justification. Risk is managed to remain within tolerance. The reason for flexing scope is based on the understanding that not all requirements are of equal importance. Using prioritization techniques like MoSCoW (Must have, Should have, Could have, Won't have this time), teams ensure the essential 'Must have' requirements are always delivered, while less critical 'Could haves' can be dropped if time or resources run short. This guarantees a viable, working product is delivered at the deadline. The five targets that should be met when applying the Hexagon are: be on time and hit deadlines, protect the level of quality, embrace change, keep teams stable (avoid adding people to a late project), and accept that the customer doesn't need everything. Flexing what is delivered allows projects to remain predictable in time and cost while adapting to changing requirements, enabling frequent delivery of value and maintaining project viability. This approach embodies the agile mindset within the structured governance of PRINCE2.
Flexing What Is Delivered: The Hexagon
Flexing What Is Delivered: The Hexagon
One of the most important concepts in PRINCE2 Agile is the idea of flexing what is delivered. This concept is visualised through the PRINCE2 Agile hexagon, which represents the six aspects (or tolerance areas) of a project and shows which ones can be flexed and which ones should be fixed when working in an agile environment.
Why It Is Important
In traditional project management, when a project runs into trouble, teams often extend deadlines, spend more money, or add more people. In an agile context, PRINCE2 Agile takes a different approach: it recommends fixing time and cost, and instead flexing the scope and quality (the level of detail or number of features delivered). This ensures that: - Deadlines are protected (delivering on time builds trust and predictability). - Budgets are controlled (fixing cost prevents overspend). - The business receives something of value by the agreed deadline, even if not every feature is delivered.
This approach supports the agile mindset of delivering a working, valuable product incrementally rather than delivering everything late or over budget.
What It Is: The Six Aspects
PRINCE2 has six aspects of project performance that must be managed. The hexagon shows all six:
1. Time – Fixed. The deadline does not move. 2. Cost – Fixed. The budget is fixed. 3. Quality – Flexed (in terms of scope of quality criteria, but acceptance criteria/customer quality expectations are protected). 4. Scope – Flexed. This is the primary aspect that is adjusted. 5. Risk – Flexed. Tolerance for risk can be adjusted. 6. Benefits – Should not be flexed beyond agreed tolerances; benefits should be protected and remain within an acceptable range.
The key idea: Time and cost are fixed, while scope and quality are flexed. Risk and benefits are also managed carefully.
How It Works
When priorities compete, PRINCE2 Agile fixes time and cost and flexes what is delivered. This is achieved through prioritisation techniques such as MoSCoW (Must have, Should have, Could have, Won't have this time). The 'Musts' represent the minimum viable product that must be delivered; the 'Coulds' and 'Shoulds' provide contingency that can be dropped if time or budget pressures arise.
Importantly, flexing does not mean lowering quality below acceptable standards. The quality of what is delivered must always meet the agreed acceptance criteria. Instead, the amount delivered (features/requirements) is flexed. A useful phrase is: never compromise on the quality of a feature, but do prioritise which features are delivered.
The concept works hand in hand with the idea of a level of tolerance being set for each aspect, and of using timeboxing to protect the deadline.
How to Answer Exam Questions
Exam questions often test whether you understand which aspects are fixed and which are flexed. Look out for scenario questions describing a team under time pressure and asking what should happen. The expected PRINCE2 Agile answer is usually to protect time and cost by flexing scope (dropping lower priority 'Coulds' or 'Shoulds' using MoSCoW).
Be careful with quality: the exam distinguishes between reducing the number of quality criteria met (acceptable) versus delivering something that fails acceptance criteria (not acceptable). PRINCE2 Agile does not allow flexing below the agreed level of quality for what is delivered.
Exam Tips: Answering Questions on Flexing What Is Delivered: The Hexagon
- Remember the rule: Fix time and cost, flex scope and quality. - The primary tool for flexing is MoSCoW prioritisation. If a question asks how to flex, MoSCoW is often the answer. - Distinguish between flexing the amount delivered (allowed) and compromising the quality of what is delivered (not allowed). - The 'Must have' requirements represent the minimum acceptable delivery and should not be dropped. - If a scenario shows a project falling behind, the correct action is usually to remove lower-priority features rather than extend the deadline or budget. - Recall that all six aspects (time, cost, quality, scope, risk, benefits) still need to be managed, but agile flexes scope most freely. - Watch for distractor answers suggesting adding more time, more money, or reducing quality below acceptance criteria—these are typically incorrect in PRINCE2 Agile. - Keep the hexagon image in mind as a memory aid to recall which aspects are fixed versus flexible.
