1.2 Seven Performance Aspects & Delivery Approaches

1.2 Seven Performance Aspects & Delivery Approaches

Introduction to Performance Control

To ensure a project remains viable and delivers its intended strategic value, project managers must continuously monitor and control performance metrics. While traditional project management frameworks focused on the classic 'triple constraint' (Time, Cost, Quality), PRINCE2 7 expands performance control to seven distinct performance aspects (adding Sustainability to the classic six).

By establishing quantitative targets and formal variance thresholds (tolerances) across all seven aspects, PRINCE2 creates an effective governance environment that empowers project managers while safeguarding executive authority and corporate capital.

---

The Seven Performance Aspects

Every PRINCE2 7 project must define, measure, and control performance against the following seven aspects throughout its lifecycle:

                      +-----------------------+
                      |   SEVEN PERFORMANCE   |
                      |        ASPECTS        |
                      +-----------+-----------+
                                  |
       +------------+------------+------------+------------+------------+
       |            |            |            |            |            |
   +---+---+    +---+---+    +---+---+    +---+---+    +---+---+    +---+---+
   | TIME  |    | COST  |    |QUALITY|    | SCOPE |    | RISK  |    |BENEFITS|
   +-------+    +-------+    +-------+    +-------+    +-------+    +-------+

1. Time

• Key Question: When will the project and its management stages complete?
• Control Focus: Delivery schedules, milestone target dates, stage boundary completion deadlines.
• Example Target & Tolerance: Project completion target of 31 December, with an approved stage tolerance of +/- 2 weeks.

2. Cost

• Key Question: What financial investment is required to deliver the project outputs?
• Control Focus: Capital expenditure (CapEx), operational expenditure budgets, resource costs, contingency funds.
• Example Target & Tolerance: Approved stage budget of $250,000, with a cost tolerance of +5% / -$15,000.

3. Quality

• Key Question: How fit for purpose must the project deliverables be to satisfy customer expectations?
• Control Focus: Product Descriptions, quality criteria, acceptance criteria, inspection specifications.
• Example Target & Tolerance: System API response time target of 1.5 seconds, with an acceptable quality tolerance range of 1.0 to 2.0 seconds.

4. Scope

• Key Question: What deliverables and features are explicitly included or excluded from the project?
• Control Focus: Product Breakdown Structure, product requirements, scope statements, boundaries.
• Example Target & Tolerance: Delivery of 10 core software modules, with 2 secondary modules marked optional and flexed based on timeline availability.

5. Risk

• Key Question: How much risk exposure is acceptable to the organization?
• Control Focus: Risk appetite, risk capacity, single risk financial impact thresholds, risk budget limits.
• Example Target & Tolerance: No single risk event exceeding $50,000 in potential exposure without mandatory Project Board review.

6. Benefits

• Key Question: Why are we undertaking this project, and what measurable value must be realized?
• Control Focus: Return on investment (ROI), operational cost reductions, revenue growth, strategic alignment.
• Example Target & Tolerance: Business Case target of $600,000 annual operational savings, with a minimum benefit tolerance threshold of $500,000.

7. Sustainability

• Key Question: What environmental, social, and governance (ESG) performance must the project and its products achieve?
• Control Focus: Carbon and waste targets, social impact commitments, regulatory ESG compliance, product lifecycle impact.
• Example Target & Tolerance: Project carbon budget of 120 tonnes CO2e, with a sustainability tolerance of +10 tonnes / − unlimited improvement.
• PRINCE2 7 Note: Sustainability is a full performance target with tolerances—not an optional add-on. The Sustainability Management Approach (part of the PID) defines how targets are planned, reviewed, and controlled.

---

Tolerances and Management by Exception

PRINCE2 enforces operational control through the principle of Manage by Exception.

Multi-Level Tolerance Delegation

Governance in PRINCE2 is delegated across three management tiers using explicit tolerance limits:

1. Corporate / Programme Management Level (Project Tolerances): Corporate sets overall project tolerances for the Project Board in the Project Charter or mandate.
2. Project Board Level (Stage Tolerances): The Project Board approves stage plans and sets stage tolerances for the Project Manager. As long as stage performance forecasts remain within agreed tolerances, the Project Manager manages day-to-day stage operations autonomously without needing Project Board approval.
3. Project Manager Level (Work Package Tolerances): The Project Manager sets Work Package tolerances for Team Managers. If a Team Manager forecasts breaching Work Package tolerance, they escalate an Issue to the Project Manager.

+-----------------------------------------------------------------+
| Corporate / Programme Management / Customer                     |
| Sets Project-Level Tolerances for the Project Board             |
+-----------------------------------------------------------------+
                                | (Escalation via Exception Report)
                                v
+-----------------------------------------------------------------+
| Project Board (Directing)                                       |
| Sets Stage-Level Tolerances for the Project Manager             |
+-----------------------------------------------------------------+
                                | (Escalation via Exception Report)
                                v
+-----------------------------------------------------------------+
| Project Manager (Managing)                                      |
| Sets Work Package Tolerances for the Team Manager               |
+-----------------------------------------------------------------+
                                | (Escalation via Issue / Notification)
                                v
+-----------------------------------------------------------------+
| Team Manager (Delivering)                                       |
| Executes Work Packages within agreed tolerances                 |
+-----------------------------------------------------------------+

Escalation via Exception Reports

If performance metrics or current forecasts indicate that any of the seven performance aspects will exceed approved stage tolerances, an Exception has occurred. The Project Manager MUST NOT attempt to mask the deviation or unilaterally alter baseline scope or budget. Instead, the Project Manager must immediately create an Exception Report detailing the breach, analyzing options, and submitting it to the Project Board for decision.

---

Delivery Approaches in PRINCE2 7

PRINCE2 7 separates project management governance from product delivery techniques. The official syllabus defines three delivery approaches: linear-sequential, iterative-incremental, and hybrid. This delivery-agnostic architecture enables PRINCE2 governance to overlay any technical delivery methodology:

---

Adapting Performance Control Across Delivery Approaches

In a traditional linear-sequential environment:

• Scope and Quality specifications are typically fixed upfront.
• Time and Cost tolerances are monitored closely to protect baseline deliverables.

In an iterative-incremental environment (such as PRINCE2 Agile contexts):

• Time and Cost are frequently fixed (fixed sprint duration, fixed team capacity/cost).
• Scope and Quality tolerances are flexed dynamically. Features are prioritized using techniques such as MoSCoW (Must have, Should have, Could have, Won't have this time) to ensure high-value outputs are delivered on schedule without exceeding agreed stage tolerances or degrading core quality standards.