PRINCE2 Principles

The correct answer is Tolerance.

In PRINCE2 7, tolerance is defined as the permissible deviation above and below a plan's target for time and cost without escalating the deviation to the next level of management. It establishes the boundaries of delegated authority and defines the limits within which a Project Manager can operate without needing to refer back to the Project Board.

Tolerance is a fundamental concept in PRINCE2's 'managing by exception' principle. It allows for efficient delegation by:
- Setting clear boundaries for decision-making authority
- Defining when escalation is required
- Enabling management by exception rather than constant oversight
- Being applicable to all six performance targets (time, cost, quality, scope, benefits, and risk)

When performance is forecast to exceed tolerance levels, this triggers an exception, and the Project Manager must escalate to the Project Board through an Exception Report.

The other options are not standard PRINCE2 terminology:

Exception threshold - While this sounds plausible, it is not the official PRINCE2 term. An exception occurs when tolerance is exceeded, but the boundaries themselves are called tolerances, not exception thresholds.

Baseline variance parameter - This is not PRINCE2 terminology. While variances from baselines are monitored in project management, this specific term is not used in PRINCE2 to describe delegated authority boundaries.

Delegated authority range - Although this describes the concept accurately in plain English, it is not the specific PRINCE2 term. PRINCE2 uses precise terminology, and the correct term is tolerance.

The correct answer is: The Business Case

The Business Case is the fundamental document in PRINCE2 that provides the justification for undertaking a project. It contains the estimated costs, risks, and benefits that demonstrate why the project is worthwhile and should be pursued. The Business Case is developed at the start of the project and is continuously maintained and reviewed throughout the project lifecycle to ensure the project remains viable and justified.

Why the other answers are incorrect:

The Project Brief combined with the Benefits Management Approach - While the Project Brief does contain an outline Business Case and the Benefits Management Approach describes how benefits will be managed, neither individually nor together serve as the primary justification document. The Project Brief is a high-level document used early in the project, and the Benefits Management Approach is a supporting document that defines the management approach rather than providing the justification itself.

The Project Initiation Documentation - This is a comprehensive document that brings together all the key information needed to start the project, including the Business Case. However, it is not specifically the document that provides justification; rather, it contains the Business Case as one of its components along with other project information.

The Project Product Description - This document describes the final product or output of the project, including its purpose, composition, quality criteria, and acceptance criteria. It does not provide justification for undertaking the project based on costs, risks, and benefits.

The correct answer is that tolerances establish boundaries within which decisions can be made at the delegated level.

In PRINCE2 7, tolerances are a fundamental principle of the 'Manage by Exception' principle. They define the permissible deviation from plans in terms of time, cost, quality, scope, benefit, and risk. The primary mechanism through which tolerances enable delegated authority is by establishing clear boundaries within which the Project Manager can make decisions and manage the project autonomously without needing to escalate to the Project Board.

When the Project Board sets tolerances for the Project Manager, they are essentially creating a 'safe operating space' within which the Project Manager has the authority to make decisions, take corrective actions, and manage variations. As long as the project remains within these tolerance boundaries, the Project Manager can proceed independently. Only when forecasts indicate that tolerances may be exceeded does the Project Manager need to escalate to the Project Board through an Exception Report.

This approach enables efficient management by exception - senior management (the Project Board) doesn't need to be involved in day-to-day decisions, but maintains control through the tolerance boundaries they set.

The other answers are incorrect because:

The option about creating reporting requirements for senior management review of all significant decisions misrepresents the purpose of tolerances. Tolerances actually reduce the need for constant senior management involvement by allowing the Project Manager to operate independently within the boundaries.

The option about establishing boundaries where escalation procedures must be followed for all decisions contradicts the fundamental purpose of tolerances. Escalation is only required when tolerances are forecast to be exceeded, not for all decisions within tolerance.

The option about defining precise parameters where approval must be sought before any action also contradicts the delegation concept. Tolerances enable autonomous decision-making within boundaries, rather than requiring pre-approval for actions.