PRINCE2 Foundation (PRINCE2F) — Questions 751–825

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. Option B is correct.

The Controlling a Stage process includes the activity of authorizing Work Packages. The Project Manager assigns work to Team Managers via Work Packages in this process.

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 PBS is a hierarchical diagram that identifies all products to be produced, decomposing the project product into its constituent parts.

Option C is correct because in PRINCE2, the Team Plan is produced by the Project Manager (or sometimes the Team Manager) to provide the Team Manager with detailed information about the work to be done at the team level. It is derived from the Stage Plan and focuses on the specific activities, resources, and timelines for a team's work package, ensuring alignment with the overall project objectives.

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

The Managing Product Delivery process is used to control the link between the project manager and the team managers, authorizing work on the first stage's products. Since the project initiation documentation (PID) is approved, the project board has authorized the project, and the project manager uses Managing Product Delivery to assign work packages to the team for execution.

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 PID includes the Business Case, Project Plan, Project Approach, and other baselines. The Project Brief is an input to the PID, and the Project Product Description is a supporting document but not a core component of the PID itself. Correct: Business Case and Project Plan.

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.

Option D is correct because 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 maintains the Business Case on behalf of the Executive. While the Executive owns it, the Project Manager is responsible for its day-to-day maintenance.

When a stage-level tolerance is forecast to be exceeded, the Project Manager must escalate via an Exception Report. This is 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.

The Highlight Report is a periodic report from the Project Manager to the Project Board summarising progress within a stage.

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 and assigns roles and responsibilities. It includes the Project Board, Project Manager, Team Managers, and other roles.

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.

A Request for Change is a proposal for a change to a product that has been approved, while an Off-specification is an actual deviation from the specification (something that was supposed to be done but wasn't done correctly).

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

PRINCE2 defines opportunity responses: exploit, enhance, share, and reject. Avoid and transfer are threat responses.

Tolerances are set for each management level; the Project Board sets stage tolerances. The Project Manager can reallocate tolerance within a stage if the total is not exceeded.

The Executive is the single person ultimately accountable for the project's Business Case and its continued viability. PRINCE2 assigns responsibility for maintaining the Business Case to the Executive because they own the project's justification and must ensure it remains aligned with organizational objectives throughout the project lifecycle.

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 improves project control and ensures continued business justification. It does not eliminate all risks or guarantee success.

The correct answer is A because 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.

Managing a Stage Boundary provides the Project Board with information needed to review the current stage and decide whether to authorise the next stage.

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 means that the Project Manager is allowed to manage within agreed tolerances; if a tolerance is forecast to be exceeded, the matter is escalated to the Project Board.

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.

A Request for Change is a proposal for a change to a product that has been agreed or baselined. An Off-specification is something that should be provided but is not (or is forecast not to be) provided.

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.

Request for Change and Off-specification are two types of issue. The third is Problem/Concern. All three are valid; the question asks for two of them.

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.

Option A is correct because the Project Manager is responsible for reporting Highlights to the Project Board during the Controlling a Stage process. This is a mandatory management product defined in PRINCE2, providing a summary of progress, achievements, and exceptions at intervals specified in the Stage Plan.

The Project Board consists of Executive, Senior User, and Senior Supplier.

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 Controlling a Stage, the Project Manager authorizes work packages to Team Managers. The Project Board authorizes stages, not work packages directly.

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 A 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.

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 produced by the Project Manager and sent to the Project Board and stakeholders to provide a summary of progress.

To increase the probability and/or impact of an opportunity, use the 'exploit' response.

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 independent, ongoing role to ensure the project remains aligned with the Business Case and standards. A quality review is a specific technique to assess the quality of a product. Assurance is a role; quality review is a process.

SU is a pre-project process to determine if the project is viable before committing resources to full initiation; IP formally establishes the project's foundations and produces the PID.