PRINCE2 Foundation (PRINCE2F) — Questions 676–750

The Business Case in PRINCE2 captures the justification for the project, including the expected benefits (tangible and intangible) that the project aims to deliver. Benefits are a core component because they define the value that the project must provide to justify the investment. Without expected benefits, the Business Case cannot demonstrate whether the project is worthwhile.

Authorizing Work Packages is an activity in the Controlling a Stage process, where the PM assigns work to Team Managers.

The purpose is to provide the Project Board with sufficient information to review the current stage, approve the next stage plan, and confirm continued business justification.

The Project Manager is responsible for producing the Project Initiation Documentation (PID) in PRINCE2. The PID is a key deliverable that consolidates the project's scope, business justification, plans, and controls, and the Project Manager compiles it based on input from the Project Board and other stakeholders. This responsibility is explicitly defined in the PRINCE2 Project Manager role description.

In PRINCE2, the risk register is the central repository for recording all identified risks, and the risk management approach defines how risks will be managed throughout the project. During the Initiating a Project process, the project manager must formally document the supplier delay risk and plan appropriate responses (e.g., mitigation, contingency) within the risk management approach. This ensures the risk is actively managed rather than ignored or deferred, aligning with PRINCE2's principle of continued business justification.

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

An Exception Plan is produced when a stage is forecast to exceed its tolerances, as an alternative to the current Stage Plan, for approval by the Project Board.

The Team Manager is responsible for delivering the Work Package within agreed tolerances and reporting progress via Checkpoint Reports.

The Initiating a Project process produces the Project Initiation Documentation (PID), which is the key output that consolidates all baselines for the project. The Benefits Management Approach is also an output of this process, as it defines how the project's benefits will be measured, managed, and realized throughout the project lifecycle.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a foundation for the project.

Highlight Reports are produced by the Project Manager during the Controlling a Stage process and sent to the Project Board to provide a summary of progress.

Project Assurance and quality reviews serve distinct purposes in PRINCE2. Project Assurance is an independent oversight function that ensures the project remains viable, compliant, and on track against the business case and plans. A quality review, on the other hand, is a structured technique used to assess whether a specific product meets its defined quality criteria and is fit for purpose.

Exploit and Enhance are opportunity responses. Avoid and Transfer are threat responses. Accept can be used for both.

SB produces the End Stage Report and the next Stage Plan (or Exception Plan).

SU is a pre-project process that ensures the prerequisites for initiating a project are in place, including the appointment of the Executive and Project Manager and the creation of the Project Brief.

The Project Brief is produced during Starting Up a Project and provides the baseline for the Initiation Stage. It contains the project definition, outline business case, and other preliminary information.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process because it consolidates all essential information—such as the Business Case, project scope, risks, and controls—into a single baseline document that authorizes the project to proceed. PRINCE2 mandates that the PID is created during this process to provide a firm foundation for the project and to enable senior management to make an informed decision about project continuation.

In PRINCE2, the 'Controlling a Stage' process is used by the Project Manager to assign work to Team Managers and authorize Work Packages. This process includes the 'Authorize a Work Package' activity, which formally delegates the delivery of one or more products to a Team Manager. The other processes either occur before the stage is underway or are performed at the management level above the Project Manager.

The Executive is the single accountable role for the project and owns the business case, making it a mandatory member of the project board. The project board's three primary roles are Executive, Senior User, and Senior Supplier, as defined by PRINCE2's organizational structure.

The Executive (Senior Responsible Owner) is the role accountable for the Business Case and its ongoing justification throughout the project. PRINCE2 requires the Business Case to be maintained and reviewed at every stage boundary to ensure continued viability, and this responsibility rests with the Executive, not the Project Manager or Team Manager.

The five threat responses are: avoid, reduce, transfer, accept, share. Fallback is not a separate response; it is part of a plan.

After the PID is approved, the project board authorizes the work for the first stage via the Directing a Project process, specifically the 'Authorize the project' activity. This process provides the necessary authorization for the project manager to start the first stage. Initiating a Project produces the PID, but authorization to proceed is given by the project board through Directing a Project.

If a tolerance is forecast to be exceeded during a stage, the PM should have already escalated via an Exception Report in Controlling a Stage. However, if this is identified during Managing a Stage Boundary, the PM should still produce an Exception Plan for the Board's approval.

The Business Case is a core component of the Project Initiation Documentation (PID) because it provides the justification for the project, including costs, benefits, and risks. The Project Plan is also a component of the PID as it defines how and when the project objectives will be achieved, including timescales and resource requirements. Both are mandatory elements that form the foundation of the PID in PRINCE2.

Checkpoint Reports are produced by Team Managers to inform the PM of progress on Work Packages.

Project Assurance is independent of the Project Manager and provides assurance to the Project Board.

PRINCE2's Controlling a Stage process requires the Project Manager to escalate any forecast deviation beyond the agreed stage tolerance to the Project Board via an Exception Report. The Project Manager cannot proceed without the Board's direction, as the tolerance is a delegated authority limit set by the Board.

The Highlight Report is produced by the Project Manager at intervals defined in the Communication Management Approach to update the Project Board on progress.

The Executive (Senior Responsible Owner) is the owner of the Business Case and is accountable for its development and maintenance. The Project Manager may assist in its creation but does not own it.

Project Assurance provides an independent view of the project's progress, ensuring that the project remains viable and adheres to the business case. It reports directly to the Project Board, not the Project Manager, to maintain objectivity. This independence is critical for the Board to make informed decisions about project continuation.

The Project Manager is responsible for maintaining the Business Case throughout the project because they manage day-to-day activities, track progress against the Business Case, and escalate any deviations to the Executive. PRINCE2 assigns this operational responsibility to the Project Manager to ensure continuous alignment with the project's justification.

In PRINCE2, when a project is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board by raising an Exception Report. This is because tolerances are delegated authority limits, and exceeding them requires the Project Board to decide on corrective action, such as approving a revised plan or adjusting tolerances. Option C is correct as it directly follows the PRINCE2 principle of management by exception.

The Managing a Stage Boundary process produces the End Stage Report to summarize the current stage's performance against its Stage Plan, and the Stage Plan for the next stage to define the work for the upcoming stage. These are mandatory outputs because the process prepares the project for the next stage or closure decision by the Project Board.

The Starting Up a Project process ensures that the prerequisites for initiating a project are in place by answering whether the project is viable and worthwhile, and whether the necessary people are available to proceed.

Starting Up a Project (SU) is the pre-project process that produces the Project Brief and initiation Stage Plan, enabling the Project Board to decide whether to proceed with initiation.

Management by exception dictates that when a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. Continuing without escalation is not allowed.

Managing Product Delivery focuses on the team delivering products according to the Work Package requirements. It ensures that work is accepted, executed, and delivered to the required quality.

The Organising practice defines the project management team structure, roles, and responsibilities, including the four levels of management (corporate/programme management, project board, project manager, and team manager) and the three project interests (business, user, supplier). It establishes clear accountability and authority within the PRINCE2 project management team.

The Directing a Project process is designed to enable the Project Board to make key decisions and exercise overall control over the project. It covers the board's responsibilities from project initiation through closure, including authorizing stages, reviewing progress, and providing strategic direction.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product, baseline, or plan before it is completed, while an Off-specification is a formal notification that a product has deviated from its specification after it has been produced. The key distinction is timing and intent: RFCs are proactive modifications, whereas Off-specifications are reactive deviations that have already occurred.

The Initiating a Project process is responsible for establishing a solid foundation for the project, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—including the Project Plan, Business Case, and Project Brief—into a single, approved document that defines the project's scope, objectives, and controls. This document is the baseline against which project progress is measured and is formally approved by the Project Board before the project proceeds.

In PRINCE2, opportunity responses are specific actions to address opportunities (positive risks). 'Share' (Option A) is correct because it involves partnering with another party to exploit an opportunity, sharing the potential benefits. 'Enhance' (Option D) is correct because it means proactively increasing the probability and/or impact of an opportunity to maximize its potential benefits.

In PRINCE2, the Project Board sets stage tolerances for the Project Manager as part of the 'Manage by Stages' principle. This allows the Project Manager to manage the stage within defined tolerances without needing to escalate every minor deviation, ensuring delegated authority is clear and controlled.

The Project Manager is responsible for maintaining the Business Case throughout the project because PRINCE2 assigns the day-to-day management of the Business Case to the Project Manager, who must ensure it remains viable and aligned with project 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 process, where the Project Manager owns the document's maintenance, not its approval.

In PRINCE2, the Project Initiation Documentation (PID) provides a comprehensive baseline for the project, including defined roles and responsibilities. When team members are unclear about their roles, the PID is the management product that formally documents these assignments, ensuring everyone understands their accountabilities. This aligns with the PRINCE2 principle of 'defined roles and responsibilities' and the 'People' domain focus on organizational clarity.

PRINCE2 provides a standardized framework with defined roles, processes, and terminology, enabling all stakeholders to communicate effectively using a common project management language. This reduces misunderstandings and improves collaboration across teams, regardless of the organization or industry.

PRINCE2 requires that any change to the business case, especially one that significantly reduces NPV and extends payback period, must be escalated to the project board for a decision. As project manager, you cannot unilaterally update the business case or change scope; you must request an extraordinary meeting to present the revised business case and seek approval to continue. This aligns with the 'continued business justification' principle and the 'manage by stages' theme.

The PID and the Benefits Management Approach are key outputs of IP. The Project Brief is from SU, and the Work Package is from CS or MP.

Management by exception is a core PRINCE2 principle where the Project Board only gets involved when forecasts indicate that tolerances (e.g., time, cost, quality) will be exceeded. This allows the Project Manager to manage day-to-day within agreed tolerances, escalating only exceptions. Option B correctly captures this delegation of authority.

DP enables the Project Board to make key decisions and provide overall direction throughout the project.

The Executive is the single individual accountable for the project's success and chairs the Project Board in PRINCE2. This role provides the business justification, secures funding, and makes key strategic decisions, ensuring the project remains viable and aligned with organizational objectives.

The purpose is to provide the Project Board with information to approve the next stage and review the current stage's performance.

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 produces an End Stage Report summarizing the current stage's results and a Stage Plan for the next stage, enabling informed governance decisions.

The Project Initiation Documentation (PID) is the key document produced as an output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single source of information that defines the project's scope, objectives, and controls, and is used to obtain authorization to proceed.

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 seeks to change the specification itself, whereas an Off-spec reports a failure to conform to the existing specification. Option B correctly captures this fundamental difference.

The Project Brief is created in SU and provides the basis for the initiation stage.

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

PRINCE2 provides a controlled start, organization, and end, and ensures focus on business justification.

The Plans practice defines the means of delivering the products by establishing a structured approach to planning, including the creation of project and stage plans. This facilitates communication and control by providing a clear roadmap for stakeholders and enabling progress tracking against baselines. It is not about defining quality criteria, managing changes, or assigning roles, which are covered by other PRINCE2 practices.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two defined types of issue are a Request for Change (RFC), which is a proposal for a change to a product's specification or baseline, and an Off-specification, which is something that should be provided by the project but is not (e.g., a missing feature or a product that does not meet its specification). Both are formally captured and managed through the Issue and Change Control practice.

The Executive (Senior Responsible Owner) owns the Business Case and ensures its ongoing viability.

C is correct because when a project forecasts exceeding its cost tolerance, the Project Manager must escalate the issue to the Project Board via an Exception Report. This is a PRINCE2 management by exception principle: tolerances are delegated limits, and exceeding them requires board-level decision-making, not unilateral action by the Project Manager.

Planning steps: design the plan, define products, identify activities, estimate, and schedule/document.

Project Assurance is a continuous role monitoring compliance and governance, while a quality review is a specific event to examine a product. Assurance is independent; quality reviews involve peers.

The PID includes the Project Plan, Business Case, and Risk Management Approach. The Daily Log is a project log used throughout, not part of PID. The Checkpoint Report is a product of Managing Product Delivery.

In PRINCE2, the 'Controlling a Stage' process is responsible for authorizing work packages to be executed by the team. This process ensures that each work package is formally assigned, with clear acceptance criteria, reporting arrangements, and any constraints, before the team proceeds with delivery.

The Quality Review technique is used to assess whether a product meets its quality criteria and to identify errors.

A Request for Change is a proposal for a change to the project's baselines, while an Off-specification is something that should be provided but is not (or is forecast not to be).

Accountability means ultimate ownership and final decision-making authority, while responsibility means performing the work. Option D is correct.

Project Assurance is independent from the Project Manager and reports to the Project Board.

The Highlight Report is the correct choice because it is the PRINCE2 management product used to provide the Project Board with a summary of progress at regular intervals during a stage. Since the stage is on track and no issues or deviations require escalation, the Project Manager should send a Highlight Report to keep the Board informed, not an Exception or End Stage Report.