PRINCE2 Foundation (PRINCE2F) — Questions 751–825

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

A Request for Change is a proposal for a modification to a product that has been approved, while an Off-specification is a product that does not meet its specification.

The Highlight Report is a progress report that provides the Project Board with a summary of the project's status at a frequency defined in the Communication Management Approach. It is specifically designed to keep the Project Board informed of progress, achievements, and any issues or risks that require their attention. The Project Board is the sole recipient of the Highlight Report, as they are responsible for overall project governance and decision-making.

Exploit is the correct risk response for an opportunity the project wants to make more likely to happen. In PRINCE2, the Exploit response is specifically used when the project actively seeks to ensure that an opportunity is realized, often by allocating resources or taking direct actions to increase the probability of the positive event occurring. This contrasts with Enhance, which only increases the probability or impact without guaranteeing the outcome.

Project Assurance is independent and cannot be delegated to the Project Manager.

Closing a Project includes producing the End Project Report, Lessons Report, and confirming benefits review arrangements.

Project Assurance is an ongoing, independent oversight role that ensures the project remains aligned with its business justification and adheres to standards throughout the project lifecycle. In contrast, a quality review is a specific, time-boxed event (e.g., a PRINCE2 quality review technique) used to evaluate a completed product against its quality criteria. The key difference is that Project Assurance is a continuous role, while a quality review is a discrete event.

The Starting Up a Project (SU) process produces the Project Brief, which outlines the project's scope and feasibility, while the Initiating a Project (IP) process produces the Project Initiation Documentation (PID), which provides a detailed plan and baseline for execution. This distinction is fundamental in PRINCE2 as SU focuses on pre-project preparation and IP on detailed planning and governance.

An off-specification (Off-spec) is the correct type of issue when a product has been delivered but does not meet its agreed specification. In PRINCE2, an off-specification is defined as a situation where a product should be produced according to its specification but is not, or where a product is delivered that does not meet its specification. This directly matches the scenario described.

The Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes monitoring progress, managing the team, and ensuring that work packages are delivered on time and within budget. The Project Manager must operate within these tolerances and only escalate to the Project Board when forecasts deviate beyond them.

The 'management by exception' principle in PRINCE2 means that the Project Board sets tolerances for time, cost, quality, scope, risk, and benefits, and only requires the Project Manager to escalate if those tolerances are forecast to be exceeded. This allows the Project Manager to manage within tolerances without constant board involvement, empowering them to make day-to-day decisions while the Board focuses on strategic issues.

Authorizing Work Packages, reviewing progress, and managing risks and issues are key activities of Controlling a Stage. Producing the End Stage Report is done in Managing a Stage Boundary, and producing the Project Plan is done in Initiating a Project.

Continued business justification is a core PRINCE2 principle that requires the business case to remain viable throughout the project lifecycle. This principle ensures that the project is not started without a clear justification and that this justification is reviewed and updated at key decision points, such as stage boundaries. It directly supports the PRINCE2 focus on ongoing viability rather than a one-time approval.

In PRINCE2, the Project Manager is responsible for preparing the Project Initiation Documentation (PID) during the Initiating a Project process. The PID is a key management product that defines the project's scope, objectives, and controls, and the Project Manager must compile it based on input from the project board and other stakeholders.

According to PRINCE2, when a Team Manager reports a work package as complete, the Project Manager must first accept the completed work package and then update the stage plan to reflect the actual progress. This ensures the stage plan remains accurate and provides a basis for assessing the impact on the project plan and any necessary corrective actions.

The Project Initiation Documentation (PID) is the definitive document produced during the Initiating a Project process. It consolidates the project's scope, objectives, approach, and controls, serving as the baseline against which project execution, monitoring, and control are measured throughout the PRINCE2 project lifecycle.

The Project Manager should contact the Team Manager to understand the situation and take corrective action. This is part of the 'Review Work Package Status' activity in Controlling a Stage.

The Benefits Management Approach is produced during the Initiating a Project process because it defines how the project's benefits will be measured, managed, and realized. This document is created as part of the detailed planning and governance setup that occurs in this process, ensuring alignment with the business case.

A project is defined as a temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case. This temporary nature is the key characteristic that distinguishes a project from business-as-usual (BAU), which involves ongoing, repetitive operations with a permanent team structure. PRINCE2 explicitly states that a project has a defined start and end, and once the objectives are achieved, the project is disbanded.

In PRINCE2, the Highlight Report is a management product that is prepared by the Project Manager and sent to the Project Board. The purpose of the Highlight Report is to provide the Project Board with a summary of the project's progress at intervals defined in the Communication Management Strategy. Therefore, the statement that the Project Manager receives a Highlight Report from the Project Board is incorrect; the flow is from the Project Manager to the Project Board.

The Quality Management Approach defines how quality will be managed, including quality criteria and acceptance methods.

Management by exception is a key principle where tolerances are set and escalation occurs only when tolerances are forecast to be exceeded.

Project Assurance is a role within the PRINCE2 framework, responsible for ensuring that the project remains viable and compliant with its business case, while quality review is a technique used to assess the quality of products. The correct relationship is that Project Assurance is a role, and quality review is a technique, making option C correct. They are distinct concepts: one is a governance role, the other is a specific method for evaluating deliverables.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two types of issue are 'Off-specification' (something that should be provided but is not) and 'Request for Change' (a proposal for a change to a baseline). Options B and E are correct because they directly match these defined types.

The Starting Up a Project (SU) process is designed to ensure that the project has a viable business justification and is worthwhile before committing significant resources. It answers the question 'Do we have a viable and worthwhile project?' by creating the Project Brief and selecting the Project Manager, not by producing detailed plans or the PID.

Separation ensures independent oversight. Project Assurance provides an objective check on the project's health, free from the PM's day-to-day pressures.

The PID is the key output of Initiating a Project, which establishes solid foundations for the project.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next Stage Plan, and decide whether to continue the project. It ensures that the project remains viable by assessing progress against the Business Case and updating plans accordingly.

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

Preparing the Project Plan is a key activity in the Initiating a Project process, where the detailed plan for the project is developed based on the Project Brief and the chosen strategy. This plan covers time, cost, quality, and scope, and is a core component of the Project Initiation Documentation (PID).

Risks are managed by the Project Manager. The risk should be added to the Risk Register and monitored. The Highlight Report is for reporting current stage progress; the risk can be mentioned but the immediate action is to record it.

A Product Flow Diagram shows the order in which products will be developed and the dependencies between them. It is a key input to the activity network.

The lack of experience with the chosen technology is a risk to the project, not an immediate issue. During the Initiation Stage, the project manager should formally record this risk in the Risk Register and plan an appropriate response, such as training or mentoring, to manage the uncertainty. This aligns with PRINCE2's principle of managing by stages and the requirement to identify and respond to risks proactively.

In PRINCE2, when a work package is in danger of exceeding tolerance, the Project Manager must forecast the deviation and escalate to the Project Board via an Exception Report. The Team Manager does not produce Exception Reports; that is the Project Manager's responsibility. Updating the Project Plan or issuing a Change Request are not the correct immediate actions for tolerance exceedance.

PRINCE2 defines five threat responses (Avoid, Transfer, Mitigate, Accept, Contingent) and five opportunity responses (Exploit, Share, Enhance, Accept, Contingent). 'Exploit' is a specific opportunity response that seeks to make the opportunity happen. 'Accept' is also an opportunity response, meaning the opportunity is accepted without proactive action, but with a contingency plan. Therefore, both A and B are correct opportunity responses.

The Managing a Stage Boundary process is where the Project Manager reviews the current stage, produces an End Stage Report, and creates the next Stage Plan (or Exception Plan) for the Project Board's approval.

In PRINCE2, the first formal recording of lessons occurs during the 'Starting Up a Project' process. This process includes the activity 'Capture Previous Lessons' (from the 'Learn from Experience' principle), where the project manager reviews lessons from similar previous projects and records them in the Lessons Log before the project is even initiated. This ensures that the project starts with the benefit of past experience.

Managing a Stage Boundary (SB) is designed to provide the Project Board with information to review the current stage's performance, approve the next stage plan, and update the Business Case and project plan.

The Team Manager produces the Checkpoint Report for the Project Manager to report progress of a Work Package.

Project Assurance provides independent oversight to ensure that the project is managed correctly. If the Project Manager also performed assurance, it would compromise objectivity and independence.

According to PRINCE2, the Executive appoints the project manager during SU. The Executive is the key decision-maker for this appointment.

The risk owner is responsible for managing the risk, while the risk actionee performs specific actions.

An RFC is a proposal for a change to a product that has been baselined, while an Off-spec is a description of a product that does not meet its specification.

An RFC proposes a modification to a product that has been approved or baselined; an Off-spec is something that should be provided but is not (or will not be) as specified.

In PRINCE2, the Executive (Senior Responsible Owner) is the single point of accountability for the project's business justification. This role owns the business case, ensures the project remains viable, and has ultimate authority over its initiation, continuation, and closure. The Project Manager is accountable for day-to-day management, not the business justification.

The PID and Benefits Management Approach are both produced in IP. The Project Brief is from SU, and the End Stage Report is from SB.

An Off-specification is something that should be provided but is not (or is wrong). A Request for Change is a proposed modification to a baselined product.

The Business Case components include reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. A product description is part of product-based planning, not the Business Case.

In PRINCE2, the Project Board requests a detailed plan for the next stage, which is the Stage Plan. The Stage Plan is produced at the end of the current stage (or during Initiation for the first stage) and provides the detailed management and technical steps for the upcoming stage, aligning with the 'Managing a Stage Boundary' process. This plan is essential for the Project Board to approve the continuation of the project into the next stage.

The Starting Up a Project process is the first process in PRINCE2, executed before project initiation. Its key output is the Project Brief, which provides a high-level overview of the project's justification, scope, and approach, enabling the project board to decide whether to proceed to the Initiation Stage. The Project Brief is derived from the project mandate and is used to create the Project Initiation Documentation later.

The Project Manager is responsible for maintaining the Business Case throughout the project because PRINCE2 assigns day-to-day management of the Business Case to the Project Manager, who must ensure it remains viable and aligned with the project's progress. The Project Manager updates the Business Case with actual costs, benefits, and risks, and presents it to the Project Board for approval at key decision points. This is defined in PRINCE2's Business Case management approach, where the Project Manager acts as the custodian of the document.

The Business Case includes reasons, options, benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The Risk Register is separate.

The Starting Up a Project process is the pre-project phase where the project board is appointed, the project brief is created, and the initiation stage plan is produced. The Initiation Stage Plan (A) is a direct output because it details the activities, resources, and controls needed for the initiation stage itself, enabling the project board to authorize the next process. The Project Brief (B) is also an output as it captures the initial business justification, scope, and approach, forming the basis for the project mandate and subsequent detailed planning.

The Highlight Report is produced by the Project Manager and sent to the Project Board at regular intervals to provide a summary of progress during a stage.

The Executive is ultimately accountable for the project's business justification, including ensuring value for money. Concerns about cost versus benefits must be escalated to the Executive, who owns the Business Case and has the authority to approve changes or stop the project if value is not being delivered.

The Business Case in PRINCE2 is the key document that justifies the project's initiation and continued viability. It must include an investment appraisal to evaluate the financial viability of the project, and it must define the expected benefits that the project aims to deliver. These two components are essential for decision-making and are explicitly required by the PRINCE2 methodology.

The Team Manager should raise an issue (or off-specification) to the Project Manager via the MP process. The Project Manager will then decide on corrective action or escalation.

'Major risks' are a formal component of the PRINCE2 Business Case. The Business Case must document the key risks that could affect the project's viability, ensuring that decision-makers understand the uncertainties before committing resources.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a baselined product, while an Off-specification (Off-spec) is a notification that a product does not meet its agreed specification. The key distinction is that an RFC addresses a change to a product that has already been approved, whereas an Off-spec identifies a failure to meet the original requirements. This aligns with PRINCE2's change control approach, where both are captured in the Issue Register but serve different purposes.

In PRINCE2, the Project Manager is responsible for maintaining the Business Case throughout the project. This includes monitoring the project's viability against the Business Case, updating it with actual costs and benefits, and escalating any deviations to the Project Board. The Project Manager ensures the Business Case remains a living document that reflects the current justification for the project.

The Checkpoint Report is produced by the Team Manager and sent to the Project Manager to report progress on a Work Package.

SU produces the Project Brief and the Initiation Stage Plan. The PID and End Project Report are produced later.

In PRINCE2, when a project manager forecasts that a stage will exceed its cost tolerance, they must escalate the issue to the Project Board by raising an Exception Report. This is because tolerances are delegated limits, and exceeding them requires board-level decision-making, not just reporting or self-authorization. The Exception Report triggers an Exception Plan to recover or adjust the project.

The Initiating a Project process is where the project's baselines are established, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—such as the Business Case, project plan, risk register, and project controls—into a single, approved document that defines what the project will deliver and how it will be managed. This document is the foundation for decision-making and is used throughout the project.

In PRINCE2, the Project Manager is responsible for maintaining the Business Case on a day-to-day basis. This includes monitoring actual benefits against the expected benefits, updating the Business Case with any changes, and reporting to the Project Board. The Executive is accountable for the Business Case and makes decisions based on its viability, but the Project Manager handles the maintenance activities.

The Progress practice is used to monitor and compare actual achievements against planned performance, and to assess the impact of deviations. When a work package takes longer than expected, the project manager uses Progress to evaluate the effect on the schedule and decide whether to escalate to the project board. This aligns with PRINCE2's principle of managing by stages and using tolerances to control deviations.

Project Assurance provides an independent check on the project's progress and compliance, reporting to the Project Board.

The Project Plan is a core component of the Project Initiation Documentation (PID) in PRINCE2. The PID is the foundation document that defines the project's scope, objectives, and approach, and the Project Plan details the schedule, resources, and costs for the entire project, providing the baseline for progress control.