PRINCE2 Foundation (PRINCE2F) — Questions 226–300

The purpose of the Managing a Stage Boundary process is to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and confirm continued business justification.

Starting Up a Project produces the Project Brief and the Initiation Stage Plan. The PID is produced in Initiating a Project, and the End Project Report is produced in Closing a Project.

The Business Case is developed in pre-project, approved at initiation, and reviewed at each stage boundary.

The PID is the key output that defines the project and forms the basis for management decisions.

Directing a Project enables the Project Board to make key decisions and provide overall direction without managing day-to-day activities.

The Project Manager is responsible for maintaining the Business Case, ensuring it remains viable and up to date. The Executive (SRO) owns the Business Case and is accountable for it, but the PM does the day-to-day maintenance.

In PRINCE2, Project Support is an optional role that provides administrative services to the project, such as maintaining files, collecting progress data, and managing project documentation. The role is not mandatory because the project manager can perform these tasks or they can be delegated to a separate support function. This distinguishes it from the other roles, which have specific governance or delivery responsibilities.

The Quality Management Approach (A) is the PRINCE2 document that defines the specific quality methods, standards, and responsibilities to be used during the project. It describes how quality will be managed, including the quality expectations, quality criteria, and the quality control and assurance activities that will be applied. This is distinct from the higher-level strategy or the product-focused descriptions.

Options A, D, and E are correct. The PM produces the End Stage Report, updates the Business Case, and creates the next Stage Plan. The PM does not approve the Stage Plan (Project Board does) and does not produce the Project Plan (done in Initiating a Project).

In PRINCE2, the Executive (Senior Responsible Owner) owns the Business Case, but the Project Manager is responsible for maintaining it on a day-to-day basis. The Project Board reviews and approves it at key decision points.

In PRINCE2, the Project Support role is optional and is only required when the project is large or complex enough to need administrative or specialist support. The PRINCE2 manual explicitly lists Project Support as a role that may be filled, whereas the Executive, Senior User, and Project Manager are mandatory roles on every project.

The Change Authority is an optional role that can make decisions on change requests within delegated limits, relieving the Project Board.

The Change Authority is an optional role that can make decisions on change requests within agreed limits, and it can be a person or group.

When project-level tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

The PID is created during the Initiating a Project process, which formalizes the project's start.

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

PRINCE2 separates the Project Manager from Project Assurance to ensure independent oversight of the project's ongoing viability, compliance, and quality. The Project Manager is responsible for day-to-day management and delivery, while Project Assurance provides an objective check that the project remains aligned with business justifications, standards, and controls. This separation prevents the Project Manager from being both the doer and the sole judge of their own work, avoiding conflicts of interest that could compromise governance.

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

Checkpoint Reports are prepared by the Team Manager and sent to the Project Manager.

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

The Change practice includes configuration management, which handles product version control and baselines.

The quality review technique is a structured review of a product against its quality criteria. It involves a chair, presenter, and reviewers. It is not used for all products (some may use other methods) and is not the same as quality assurance (which is broader).

An RFC proposes a change that has not been previously specified, while an Off-spec is something that should be provided but is not or is wrong.

Project Assurance is an independent oversight role that reports to the Project Board. The SRO can assign technical assurance to an individual with appropriate skills, separate from the Project Manager.

Project Assurance provides independent oversight to the Project Board, ensuring the project is managed correctly from business, user, and supplier perspectives. The Executive is accountable but Project Assurance performs the checks.

Option B is correct because Project Assurance is a PRINCE2 role that verifies the project is being conducted correctly, meaning it checks that the project remains viable, adheres to its business case, and follows the defined management stages. It is not about doing the work but about ensuring compliance with the project's plans, controls, and standards. This aligns with PRINCE2's principle of continued business justification and the need for independent oversight.

In the Controlling a Stage process, the Project Manager's immediate responsibility upon receiving a Checkpoint Report is to review it for progress against the Stage Plan, update the Stage Plan and any relevant logs (e.g., Issue Register, Risk Register) with new information, and then compile the next Highlight Report for the Project Board. This ensures accurate monitoring and control of the stage, aligning with PRINCE2's management by exception principle.

These are recommended techniques in PRINCE2.

The Directing a Project process includes the activity of authorizing an Exception Plan when a stage tolerance is forecast to be breached. The Project Board decides on the exception plan.

Option A is correct because the 'Focus on Products' principle is one of the seven PRINCE2 principles. It emphasizes defining and delivering products (outputs) that meet quality criteria and business expectations, rather than just managing activities. This principle ensures that all project work is directed toward tangible, agreed-upon deliverables.

The Project Initiation Documentation (PID) is assembled during Initiating a Project and provides a firm foundation for the project.

Checkpoint Reports are produced by the Team Manager in MP to inform the Project Manager of progress on Work Package activities.

In PRINCE2, the closing stage requires the project manager to formally confirm that all planned benefits have been realized. Updating the Business Case with actual benefits and producing the End Project Report is the correct action because it provides a formal record of benefit realization and lessons learned, which is essential for organizational learning and project closure. This aligns with the PRINCE2 principle of 'continued business justification' and the 'Closing a Project' process.

The Project Manager maintains the Business Case day-to-day, but the Executive (SRO) owns it and is ultimately accountable for the business justification.

Option A is correct because the project board provides unified direction to the project, ensuring that the business, user, and supplier interests are represented and aligned. This is a core PRINCE2 principle: the board makes key decisions and approves stage plans, but does not get involved in day-to-day management.

Management by exception means delegating authority within tolerances and escalating when tolerances are forecast to be exceeded.

Option D is correct. The risk actionee is responsible for implementing the agreed response. The risk owner owns the risk and manages the response, but the actionee actually carries out the actions.

The Executive (Senior Responsible Owner) is the single point of accountability for the Business Case and ensuring value for money. The Project Manager manages the project but is not accountable. The Senior User and Senior Supplier are part of the Project Board but not accountable for the Business Case.

Separation ensures independent oversight of the Project Manager's work, preventing conflicts of interest and providing objective assurance to the Project Board.

Managing a Stage Boundary is used to produce an Exception Plan and request authorization from the Project Board.

The principle requires that there is a justifiable reason to start and continue a project, and the justification must be documented and approved.

PRINCE2 defines quality as 'fit for purpose' — the product should satisfy the user's needs.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and ensuring the project remains viable. The Project Manager maintains the Business Case on a day-to-day basis but the SRO holds ultimate responsibility.

Checkpoint Reports provide the PM with progress information on work packages, including actuals, forecasts, and issues, to support day-to-day management.

SB includes reporting on current stage performance, planning the next stage, and updating the project plan. Authorizing Work Packages is done in CS; directing the project is done in DP.

The Checkpoint Report is the progress report produced by the Team Manager and sent to the Project Manager during the Managing Product Delivery process.

The Product Flow Diagram shows the order in which products are developed and their dependencies, including external dependencies.

Directing a Project (DP) is the process by which the Project Board authorizes initiation, stage plans, and project closure. Starting Up a Project (SU) prepares for initiation but does not authorize it.

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

The Starting Up a Project process is designed to ensure that the prerequisites for initiating a project are in place before any significant work begins. It focuses on verifying that the project has a viable business justification, a clear project mandate, and that necessary resources and personnel are available, thereby preventing wasted effort on projects that lack a solid foundation.

An RFC requests a desired change not in the original specification; an Off-specification is a deliverable that does not meet agreed specifications.

The Team Manager should raise the issue to the Project Manager, who will handle it in CS. The Team Manager cannot escalate directly to the Board.

The Project Board, through the Directing a Project process, authorizes the initiation of a project.

PRINCE2 defines quality as 'fit for purpose'—the product must be suitable for its intended use.

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

Option D is correct. SU is pre-project to decide if initiation is worthwhile; IP formally establishes the project foundation.

Project Assurance is independent of the Project Manager and provides objective oversight. It is not administrative support, nor is it the same as quality control.

Configuration management includes identification of configuration items, baseline management, version control, and change control. Risk management and quality control are separate disciplines.

SB is performed near the end of each stage (except the final) to produce an End Stage Report, plan the next stage, and update the Project Plan. It also captures lessons and can produce an Exception Plan if needed.

PRINCE2 requires separation of project management (Project Manager) from independent assurance (Project Assurance) to avoid conflicts of interest.

The Directing a Project process is where the Project Board authorizes the work for each stage, including the initiation stage and subsequent stages.

The Benefits Management Approach is created during the Initiating a Project process to define how and when the expected benefits from the project will be measured, realized, and reviewed. It ensures that the project's outputs translate into measurable outcomes aligned with the business case, and it is a key component of the PRINCE2 principle of continued business justification.

In PRINCE2, the Project Board is responsible for overall project governance, including delegating change control decisions to a Change Authority. This delegation allows the Change Authority to approve or reject change requests within predefined limits, freeing the Board from day-to-day change management while retaining strategic oversight.

Directing a Project enables the Project Board to make key decisions and exercise overall control, without managing day-to-day activities.

Project Assurance is the role responsible for providing independent assurance that the project remains on track, as defined by PRINCE2. It ensures that the project is being conducted correctly, adheres to the business case, and meets quality standards, without being involved in the day-to-day management. This role is separate from the Project Manager and Project Support to maintain objectivity.