PRINCE2 Foundation (PRINCE2F) — Questions 676–750

The Exception Plan is prepared by the Project Manager in the Managing a Stage Boundary process when a stage is forecast to exceed its tolerances. This process allows the Project Manager to present options to the Project Board, including an Exception Plan to replace the current stage plan, ensuring continued control within agreed tolerances.

The Quality Review Technique is a structured method for assessing whether a product meets its quality criteria, involving a presenter, reviewers, and a chair.

The Team Manager should report the issue to the Project Manager via a Checkpoint Report or exception process, as they are accountable for delivery within tolerances.

The Senior User is accountable for ensuring that the project's products will deliver the expected benefits. This role represents the user community and is responsible for specifying their needs, confirming that the solution meets those needs, and realizing the benefits. While the Executive is ultimately accountable for the business case, the Senior User provides the user perspective and confirms benefits realization.

Evaluating the project and documenting lessons learned is a key activity in the Closing a Project process, as it captures knowledge for future projects. Option D is correct because preparing the End Project Report is also a mandatory activity in this process, providing a final assessment of project performance against the business case and plans.

In the PRINCE2 risk management procedure, after assessing a risk (which includes evaluating its probability and impact), the immediate next step is to plan risk responses. This step involves identifying and selecting appropriate responses to address the risk, such as avoid, reduce, transfer, or accept. Option A is correct because planning directly follows assessment to determine how to manage the risk before any implementation or communication occurs.

The Directing a Project process is responsible for authorizing the initiation of a project. It is performed by the Project Board, which makes key decisions including authorizing the project initiation, stage boundaries, and project closure. The Project Board authorizes the Project Manager to proceed with Initiating a Project.

In PRINCE2, the Checkpoint Report is produced by the Team Manager and sent to the Project Manager at a frequency defined in the Work Package. The Project Manager uses it to review progress of the work package, and this information feeds into the Highlight Report, which the Project Manager produces for the Project Board. Therefore, the Project Manager should use the Checkpoint Report to review progress and produce the Highlight Report.

Manage by stages is the PRINCE2 principle that requires a project to be planned, monitored and controlled on a stage-by-stage basis. Dividing the project into management stages provides the Project Board with key decision points to review progress and authorize the next stage. The other principles address business justification, lessons, roles, products, tolerances and tailoring, none of which specifically require the project to be broken into management stages.

Enhance, because PRINCE2 defines Enhance as the specific risk response for increasing the probability and/or impact of an opportunity. Unlike threats, opportunities require proactive responses to maximize potential benefits, and Enhance is the direct counterpart to Reduce for threats.

When a stage is forecast to exceed its tolerances, the project manager must escalate the issue by producing an Exception Report. The project board then decides on the appropriate action, which may include approving an Exception Plan, changing tolerances, or stopping the project. Updating the Business Case alone is not enough; the formal escalation is required to maintain management by exception.

In PRINCE2, the Checkpoint Report is produced by the Team Manager and sent to the Project Manager at the frequency defined in the Work Package. The Team Manager is responsible for managing the work package and reporting progress, issues, and next steps via the Checkpoint Report. This is a fundamental role-responsibility mapping in the PRINCE2 method.

The Project Board is responsible for overall direction and control of the project, including authorizing deviations from tolerances and approving Stage Plans. These duties ensure the project remains aligned with business objectives and governance requirements.

The 'Expected benefits' component of the Business Case in PRINCE2 specifically quantifies the measurable improvements that the project will deliver, such as increased revenue, reduced costs, or improved efficiency. These benefits must be defined in measurable terms to enable post-project evaluation against the Business Case. The other options describe different aspects: Reasons justify the project, Major risks identify uncertainties, and Dis-benefits document negative outcomes.

PRINCE2 defines a project as a temporary organization created to deliver one or more business products according to an agreed business case. The uniqueness of the product is a core characteristic, meaning the output is not a routine or repetitive item but something new or different, which distinguishes a project from ongoing operations.

The Product Description defines the quality criteria for a product and is used during quality inspection to verify that the product meets its requirements. It is a PRINCE2 document that specifies the product's purpose, composition, derivation, and quality criteria. The Project Product Description is for the overall project product, not individual products.

The Team Manager is responsible for managing the delivery of a Work Package within a PRINCE2 project. This role coordinates the team members, ensures the work is completed according to the agreed specifications, and reports progress back to the Project Manager. The Team Manager acts as the direct interface between the project management team and the team members executing the work.

In PRINCE2, the Team Manager works within the Work Package tolerances agreed with the Project Manager. If a defect means the product will breach its agreed quality criteria, that's a deviation from the Work Package's quality tolerance, so the Team Manager must raise an Issue to the Project Manager rather than unilaterally fixing or ignoring it. The Project Manager then decides whether to authorize a change, adjust the plan, or escalate.

At every stage boundary the Business Case must be re-examined and updated so the Executive can decide whether the project still offers value for money. Costs, risks, and forecast benefits are reassessed against actual progress, and the updated Business Case is the formal basis for authorizing the next stage.

The Executive is accountable for the Business Case, including ensuring that it remains aligned with corporate strategy and that the project continues to be viable. During Managing a Stage Boundary, the Executive reviews the End Stage Report and next Stage Plan to make this confirmation, which is essential for authorizing the next stage.

Manage by exception means that the Project Board only needs to be involved when tolerances are forecast to be exceeded. This frees them to focus on strategic decisions.

PRINCE2 projects frequently sit within a programme, and programmes and standalone projects sit within a portfolio. The portfolio provides strategic investment direction and prioritisation, the programme coordinates related projects to deliver beneficial change, and the project delivers its products within that context. Recognising this nesting helps the project manager align governance and reporting appropriately.

Authorizing a Work Package is an activity performed by the Project Manager in the Controlling a Stage process.

The Highlight Report is produced during the Controlling a Stage process to provide the Project Board with a summary of progress against the stage plan. The Project Manager creates this report at a frequency defined in the Communication Management Approach, typically to report on achievements, planned activities, and any issues or risks.

PRINCE2 clearly distinguishes Project Assurance as an independent, objective check on the project's adherence to management controls and standards, while Project Support provides administrative and clerical services such as planning tools, filing, and information management. This separation ensures that assurance remains unbiased and not influenced by the day-to-day support activities.

In PRINCE2, the Team Manager produces a Checkpoint Report to inform the Project Manager about the status of a Work Package, including progress, issues, and next steps. This report is provided at frequency defined in the Work Package and feeds into the Highlight Report. The Checkpoint Report is specifically designed for progress monitoring within a stage.

The PRINCE2 principle 'Defined roles and responsibilities' requires that roles are clearly defined and that assurance roles are independent from management roles. Assigning the Project Manager also as Project Assurance violates this principle because Project Assurance must be independent of the Project Manager to provide objective oversight.

The Team Manager is responsible for delivering Work Packages and reporting progress to the Project Manager. In PRINCE2, the Team Manager coordinates the work of the team, ensures the Work Package is completed to specification, and provides regular progress reports to the Project Manager, who manages the overall project.

In PRINCE2, Project Assurance is a separate role from the Project Manager to ensure objective oversight of the project's adherence to standards, plans, and business justification. The Project Manager is responsible for day-to-day management and delivery, so allowing them to also perform Project Assurance would create a conflict of interest, as they would be reviewing their own work. This independence is critical for the integrity of the assurance function, which must provide unbiased checks on the Project Manager's decisions and outputs.

An Off-specification is something that should be provided but is not (or is provided but does not meet the specification).

In PRINCE2, the Managing Product Delivery process is responsible for accepting, executing, and delivering work packages. When a Team Manager completes a work package, they deliver the completed products back to the Project Manager through this process, which includes reporting completion and handing over the products.

Project Assurance is the correct answer because in PRINCE2, Project Assurance is a distinct role responsible for monitoring and reporting on the project's adherence to the management and technical standards, independent of the Project Manager. It ensures that the project remains aligned with the business case, quality requirements, and stakeholder expectations, acting as the 'eyes and ears' of the Project Board.

The 'tailor to suit the project environment' principle requires adapting PRINCE2 to the project's scale, complexity, risk, and organizational context. Reducing management stages and simplifying documentation for a small, low-risk intranet update is a proportionate application that keeps essential controls while avoiding unnecessary overhead. Removing principles or compromising role separation does not constitute valid tailoring.

Authorizing a Work Package is a key activity in the Controlling a Stage process, where the Project Manager assigns work to the Team Manager.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports on a frequency defined in the Work Package. These reports provide the Project Manager with progress updates on the team's work, including actual vs. planned achievements, quality activities, and any issues or risks. The Team Manager is the role that directly manages the team's day-to-day work and thus is best positioned to compile this detailed progress information.

The Defined roles and responsibilities principle ensures that a PRINCE2 project has a clear organizational structure with defined roles for the project board, project manager, team manager, and other stakeholders. The project board's agreement to have accountable roles directly demonstrates this principle. It provides the foundation for effective decision-making and accountability throughout the project.

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

The Executive is accountable for the business case and ensures that the project aligns with corporate strategy. During Starting up a Project, the Executive provides the outline business case, which is then documented in the Project Brief by the Project Manager. This outline is later expanded into the full Business Case during Initiating a Project.

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.

A programme is a group of related projects managed in a coordinated way to achieve benefits that would not be available from managing them individually. A PRINCE2 project can sit within such a programme, and its business case and governance should align with the programme's objectives. The other options either reverse the definitions or incorrectly claim that programmes are always managed using PRINCE2.

The Managing a Stage Boundary process is triggered at the end of each stage. Its purpose is to provide the Project Board with the information it needs to review the current stage's performance, approve the next Stage Plan, and confirm continued business justification. This process produces the End Stage Report and Next Stage Plan, which are the key inputs for the Project Board's 'authorize a stage' decision.

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.

The Communication Management Approach and the Risk Management Approach are both components of the PID, created during Initiating a Project to define how communication and risk will be managed. The Stage Plan for the Initiation Stage, the End Stage Report for the previous stage, and the Project Brief are not PID components; they belong to other processes or are inputs to initiation.

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.

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 PRINCE2 risk management procedure consists of five steps: Identify, Assess, Plan, Implement, and Communicate. The 'Assess' step involves evaluating the probability and impact of identified risks. The step that follows 'Assess' is 'Plan', where responses to the risks are planned.

The Business Case must contain a benefits profile that describes each benefit, its owner, and the expected timing of realization. Aligning this profile with the project board's requirement ensures that the Business Case demonstrates the project's viability and that benefits will be delivered within the specified timeframe. This supports the continued business justification principle.

The Project Brief is the input to the Initiation Stage and provides the basis for developing the Project Initiation Documentation. It contains the initial project definition and outline Business Case, which are refined during initiation.

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.

The Business Case is the PID component that provides the justification for the project, including expected benefits, costs, risks, and timescales. The project board requested a summary of the project's justification, which is exactly what the Business Case contains. Other components like the Project Plan, Risk Management Strategy, and Project Controls do not serve this purpose.

The 'Senior Supplier' represents the supplier interests on the Project Board, ensuring that the supplier's resources are committed and that the products are technically feasible. This role is distinct from the Executive, who owns the business case, and the Senior User, who represents user requirements. The Senior Supplier does not manage the Project Manager or control the budget; those are responsibilities of the Executive and the Project Board collectively.

In PRINCE2 risk management, a threat response is an action taken to address a risk that could have a negative impact on project objectives. 'Reduce' is a threat response that involves implementing actions to lower the probability and/or impact of a threat to an acceptable level, such as adding extra testing to reduce the risk of software defects.

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.

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.

The Project Product Description is the correct PID component because it specifies the final product's quality criteria, acceptance criteria, and acceptance methods. It directly confirms what will be delivered and how acceptance will be verified. The Quality Management Approach, Benefits Review Plan, and Risk Management Approach serve other purposes and do not contain the specific acceptance criteria for the project's products.

Checkpoint Reports flow from the Team Manager to the Project Manager at the frequency defined in the Work Package, covering progress, issues, and next steps. Highlight Reports flow from the Project Manager to the Project Board at the frequency defined in the Communication Management Strategy, summarising stage status, risks, and exceptions.

The Checkpoint Report is a progress report produced by the Team Manager and sent to the Project Manager at a frequency defined in the Work Package. It is used by the Project Manager to monitor progress and take corrective action within the 'Controlling a Stage' process. Therefore, the correct answer is '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.

Managing a Stage Boundary includes producing the End Stage Report, updating the Project Plan, producing the Next Stage Plan, and updating the Business Case. These activities provide the Project Board with the information needed to assess the current stage's performance and decide whether to authorise the next stage.

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

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

The Project Manager is performing the 'Controlling a Stage' process because this process handles day-to-day management of the stage, including authorizing Work Packages that are part of the current Stage Plan. The request from the Team Manager to authorize a Work Package is a typical activity within this process, which ensures work is assigned, monitored, and controlled.

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.

In PRINCE2, Starting Up a Project (SU) is the pre-project process that produces the Project Brief and the Project Product Description, ensuring the project is worth initiating. Initiating a Project (IP) then builds on the Project Brief to produce the Project Initiation Documentation (PID), which includes the Business Case, plans, controls, and risk approach. The PID is the baseline against which the project is managed.

While tolerances are not forecast to be breached, the Project Manager manages the stage by keeping plans current and reporting through Highlight Reports. Updating the Stage Plan captures the revised forecast, and the Highlight Report gives the Project Board the visibility it needs. Exception reporting is reserved for anticipated tolerance breaches.

In PRINCE2, any new requirement or change that was not in the original scope is treated as an issue (specifically a change issue) and must be captured in the Issue Register and assessed for impact before any decision is made. The Project Manager's first action is to log the issue and evaluate its effect on the project's business case, plans, risks, and scope. Only after impact assessment should the Change Authority decide whether to approve, reject, or defer the change.

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