PRINCE2 Foundation (PRINCE2F) — Questions 1051–1125

If a problem is beyond the team's tolerance, the Team Manager should escalate it to the Project Manager via a Checkpoint Report or issue. The Team Manager cannot change the stage plan or resolve issues outside their delegated authority.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides the foundation for the project and is used throughout the project.

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager during the Managing Product Delivery process.

Team Managers produce Checkpoint Reports to inform the Project Manager of progress within a Work Package.

The three types of issue are Request for Change, Off-specification, and Problem/Concern.

When the Project Board rejects the Stage Plan during the Managing a Stage Boundary process, the project cannot proceed as intended. PRINCE2 requires the Project Manager to issue an Exception Report to the Project Board, recommending project closure if the plan is not approved, because the project has no authorized plan to continue and the board must decide whether to close or take alternative action.

The Managing a Stage Boundary process produces the End Stage Report, updated Project Plan, and the next Stage Plan (or Exception Plan).

Highlight Reports are from PM to Project Board; Checkpoint Reports are from Team Manager to PM.

Expected benefits and major risks are key components of a Business Case in PRINCE2.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, as it defines the project and serves as the foundation for its management.

In the Directing a Project process, the Project Board is responsible for reviewing the Stage End Report and deciding whether to authorize the next Stage Plan. This is the formal activity that occurs when a stage is complete, ensuring that the project remains viable and aligned with business justification before proceeding. The correct answer is A because the board must approve the plan for the next stage to continue.

The correct answer is D because the PRINCE2 communication management strategy defines how, when, and to whom information should be communicated. The project manager should have agreed on this strategy with the board upfront, ensuring that critical risks are reported in a format and frequency that meets the board's needs. Without this agreement, the board was not properly informed despite the detailed risk report being presented.

The Project Manager is responsible for maintaining the Business Case on a day-to-day basis, while the Executive (Senior Responsible Owner) owns it and is accountable for its viability.

The Senior Supplier role on the Project Board is responsible for ensuring that the supplier's products meet the agreed quality requirements. This includes providing the necessary resources and expertise to deliver the project's products, and contributing to the Business Case from a supplier perspective, particularly regarding the feasibility and cost of the supplier's work.

Managing a Stage Boundary process includes the Project Board reviewing the End Stage Report and deciding whether to approve the next Stage Plan. Directing a Project is the process where the Board makes high-level decisions, but the formal review and approval of the next stage occurs during Managing a Stage Boundary.

The Managing a Stage Boundary process produces the End Stage Report and the next Stage Plan, which the Project Board uses to decide whether to continue.

A Request for Change proposes a modification; an Off-specification is a product that does not meet its specification.

Option A is correct because the PRINCE2 methodology defines Project Assurance as an independent check on the project's progress, performed on behalf of the Project Board. It is separate from the Project Manager's day-to-day management and ensures that the project remains viable, compliant with standards, and aligned with business objectives. This independence is critical for objective oversight and is a core principle of PRINCE2's governance model.

PRINCE2 has seven principles including 'Manage by Stages' and 'Focus on Products'. 'Manage by Exception' is a principle, not 'Management by Exception'? Actually 'Manage by Exception' is a principle. 'Product-based Planning' is a technique, not a principle. 'Risk-based Planning' is not a principle.

An RFC proposes a modification to an approved baseline, while an Off-specification indicates that something should have been provided but was not, or is not working as expected.

The Senior User is responsible for specifying the benefits and ensuring that the project delivers them, as defined in the PRINCE2 Business Case theme. This role represents the interests of those who will use the project's outputs and is accountable for realizing the expected benefits after the project is completed.

In PRINCE2, the Project Board is responsible for overall project governance and can delegate its change control authority to a Change Authority. This delegation is formalized in the Project Initiation Documentation (PID) and allows the Change Authority to approve or reject change requests within predefined limits, such as cost or time thresholds, without needing to escalate every decision back to the Board.

Managing a Stage Boundary includes producing an End Stage Report and preparing a Stage Plan for the next stage.

Option D is correct because PRINCE2 mandates that when a stage's forecast exceeds its tolerance (here, 10% above $200,000 = $220,000, and the new cost is $230,000), the project manager must raise an Exception Report to the project board. The board, comprising the executive, senior user, and senior supplier, then decides on corrective actions—such as approving additional budget, renegotiating scope, or stopping the project. The project manager cannot unilaterally approve the overrun or bypass the board.

The Change Control Approach defines how changes to baselined products are managed, including the change control procedure.

The procedure steps are: Identify, Assess, Plan, Implement, Communicate. 'Plan' comes after 'Assess'.

The Team Manager is the role responsible for the day-to-day management of a Work Package within a PRINCE2 project. They report to the Project Manager and ensure that the work is completed according to the agreed tolerances, quality criteria, and schedule. This is defined in the PRINCE2 manual under the 'Organizing' theme, where the Team Manager is specifically tasked with coordinating the team's work and reporting progress.

'Reduce' is a standard threat response. 'Enhance' is for opportunities.

In PRINCE2, the Team Manager is responsible for delivering the Work Package and reports progress directly to the Project Manager, who is the single point of accountability for the project. The Project Manager uses this information to update the Project Plan and report to the Project Board. This ensures a clear line of control and avoids bypassing the management layer.

The PM must first record the issue in the Issue Register and then decide on the appropriate response. If the issue could breach tolerances, an Exception Report is needed, but the immediate step is to log it.

DP is the process by which the Project Board authorizes key decisions and provides overall direction, but does not manage day-to-day activities.

The 'Focus on Products' principle requires that a project defines and agrees on product descriptions (including quality criteria) before development begins, ensuring that all stakeholders have a shared understanding of what will be delivered. Creating product descriptions after development violates this principle because it undermines the definition of scope, quality expectations, and acceptance criteria upfront, leading to potential rework and misalignment.

Option B is correct because the Change Authority role is optional in PRINCE2. It is only established if the Project Board decides to delegate authority for making change decisions within defined limits, rather than handling all change requests themselves.

Checkpoint Reports are from Team Managers to the Project Manager, while Highlight Reports are from the Project Manager to the Project Board.

Checkpoint Reports are produced by the Team Manager in Managing Product Delivery and reviewed by the Project Manager in Controlling a Stage.

SU is a pre-project process to determine if the project is viable; IP formally establishes the project by creating the PID.

Tailoring adapts PRINCE2 to the project's environment; embedding is integrating it into the organization's culture.

According to PRINCE2's management by exception principle, if a stage tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot exceed tolerance without authorization.

The PID includes the Project Plan, Business Case, and Risk Management Approach. The Daily Log is an ongoing log, and the Lessons Report is produced in Closing a Project.

The Project Manager produces the End Project Report as part of the Closing a Project process.

Starting Up a Project produces the Project Brief, Initiation Stage Plan, and Daily Log. The PID is from IP, and the End Stage Report is from SB.

Directing a Project includes the activity 'Authorize Initiation' and later 'Authorize the Project' to formally start the project.

The PID is the single most important output of IP, providing the foundation for the project.

Authorizing Work Packages is a key activity of the Controlling a Stage process, where the Project Manager authorizes work, monitors progress, and manages issues.

Option C is correct because in PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product, its specification, or the project's baseline, while an Off-Specification (Off-spec) is a product that has been completed but does not meet its agreed specification. The key distinction is that an RFC seeks to change what is required, whereas an Off-spec identifies a deviation from what was required.

SU is a pre-project process to decide if the project is viable; IP formally establishes the project and produces the PID.

Project Assurance is responsible for independent oversight of the project, separate from management and delivery.

Option A is correct because the Customer's quality expectations are a key input to the PRINCE2 Quality practice, defining the criteria that the project's products must meet from the customer's perspective. These expectations are documented in the Project Product Description and used to derive acceptance criteria and quality control activities.

Managing Product Delivery is the process of accepting, executing, and delivering Work Packages. It ensures that products are created to the required quality standards.

The Team Manager is responsible for the delivery of one or more Work Packages and reports progress to the Project Manager.

The PRINCE2 project management team structure includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optionally the Change Authority. The Project Sponsor is not a defined role in PRINCE2; instead, the Executive role fulfills the sponsorship responsibilities. Therefore, option A is correct as the role that does NOT exist in the PRINCE2 framework.

D is correct because the Business Case must be refined to reflect the market uncertainty before the Project Plan is created. In PRINCE2, the Business Case is a living document that drives decision-making, and the Project Plan is based on it. Including a risk assessment of the market uncertainty ensures the project board can make an informed decision about whether the project remains viable, given the NPV and IRR are based on assumptions that may no longer hold.

The risk actionee is responsible for implementing the risk response, while the risk owner is accountable for managing the risk.

PRINCE2 integrates principles, themes (practices), and processes. Tailoring is also an element but is applied across these.

In PRINCE2, the Project Manager maintains the Business Case on behalf of the Executive, who owns it. The Project Manager updates the document as needed.

The Project Board provides direction, approves plans, and makes key decisions.

Project Assurance is ongoing and independent; a quality review is a specific technique to review products.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is management by exception.

The PID includes the Project Plan and the Business Case. The Risk Register and Issue Register are separate documents. The Lessons Log is created during Starting Up a Project.

Directing a Project includes the activity 'Authorise Initiation' where the Project Board reviews the Project Brief and decides whether to allow initiation. Starting Up a Project prepares the Project Brief but does not authorise initiation.

Project Assurance is independent of the Project Manager and provides assurance to the Project Board that the project is being managed correctly and remains viable.

Option C is correct because the quality register is the PRINCE2 management product used to record all planned and completed quality activities, including quality inspections and test results. It provides a log of quality events throughout the project lifecycle, enabling traceability and auditability of quality efforts.

The PRINCE2 project management team includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optional Project Support and Project Assurance. The Customer is not a role; the Senior User represents the customer. The Business Case is a practice, not a role.

A Product Description includes quality criteria that define what 'fit for purpose' means for that product.

PRINCE2 is product-based to ensure clarity about what the project will deliver, reducing ambiguity and focusing on outputs rather than activities.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot ignore the issue or update the plan without authorisation. Closing the project is premature.

The purpose of Closing a Project is to provide a fixed point to verify that the project has achieved its objectives, hand over products, confirm benefits review arrangements, and release resources. Starting Up a Project is to ensure basic conditions exist; Initiating a Project establishes the project; Managing a Stage Boundary plans the next stage.

Project Assurance is independent oversight of the project's direction and controls, while Project Support provides administrative and advisory services to the Project Manager.

The Project Plan is produced during Initiating a Project and provides the overall plan for the project.

Threat responses include Avoid, Reduce, Fallback, Transfer, Accept, and Share. Exploit, Enhance, and Reject are for opportunities.