PRINCE2 Foundation (PRINCE2F) — Questions 901–975

The Initiating a Project process is where the project's foundations are established, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—including the Business Case, Project Plan, and Risk Register—into a single, coherent document that defines what the project will deliver, why, how, and against what constraints. It serves as the baseline for decision-making and is formally approved before the project proceeds to the next stage.

Option A is correct. The Managing a Stage Boundary process aims to provide the Project Board with enough information to review the current stage, approve the next stage plan, and confirm continued business justification.

The Controlling a Stage (CS) process covers the day-to-day management activities of the Project Manager within a stage.

According to the management by exception principle, when a stage tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The Project Manager cannot unilaterally increase the budget or ignore the breach.

The Senior Responsible Owner (SRO/Executive) owns the Business Case and is accountable for ensuring it remains viable. The Project Manager maintains the Business Case on behalf of the Executive.

Management by Exception means the PM is empowered within tolerances, and only escalates when tolerances are forecast to be exceeded.

An Off-specification is something that should be provided but is not (a gap), whereas a Request for Change is a proposal for a change that, if implemented, would alter an approved baseline.

The Project Initiation Documentation (PID) is the key output of Initiating a Project. It brings together all the information needed to justify the project and define its scope.

The Starting up a Project process ensures that the prerequisites for initiating a project are in place, starting with appointing key roles, then learning from past projects, building the team, developing the outline business case, and finally selecting the approach.

The Project Board reviews stage-end reports and decides whether to authorize the next stage. This is part of Directing a Project (DP). The PM produces the End Stage Report and next Stage Plan during Managing a Stage Boundary (SB).

The Project Manager authorizes work by issuing a Work Package to the Team Manager.

The Project Board members (Executive, Senior User, Senior Supplier) are responsible for project assurance. They delegate assurance tasks but remain accountable. The Project Manager does not perform assurance; that would compromise independence.

Separating Project Manager from Project Assurance ensures objectivity and independence of assurance activities. The Project Manager is responsible for day-to-day management and cannot objectively assess their own work.

The Issue Register records all issues including requests for change, off-specifications, and problems/concerns. The Configuration Item Record tracks product versions, and the Quality Register tracks quality activities.

An Off-specification is a deviation from a specification, typically found during quality inspection.

A Request for Change is a proposal for a modification, while an Off-specification is something that should have been provided but is missing or not working.

The Senior User is responsible for specifying the benefits and ensuring they are realized, but the Executive owns the Business Case. The Project Manager maintains it on a day-to-day basis.

The Highlight Report is provided by the Project Manager to the Project Board at the end of each reporting period to summarize progress.

The Business Case is the correct management product because it documents the justification for the project, including costs, benefits, and risks. A change in external regulations directly impacts the project's viability, which is a fundamental aspect of the Business Case. PRINCE2 requires the Business Case to be updated whenever there is a change that could affect the project's continued justification.

Management by exception requires escalation via an Exception Report to the Project Board when a tolerance is forecast to be exceeded.

In PRINCE2, the Project Board is collectively responsible for authorizing the initiation of a project. This decision is made during the 'Starting Up a Project' process, where the Project Board reviews the Project Brief and decides whether to proceed to the Initiation Stage. The Project Board's authority is derived from the corporate or programme management, but the actual authorization to initiate is a board-level responsibility.

The PM authorizes Work Packages, monitors progress, and manages issues and risks. Producing the next stage plan is done in SB, and producing the Project Plan is done in IP.

The Project Board consists of the Executive (SRO), Senior User(s), and Senior Supplier(s).

DP is performed by the Project Board and runs throughout the project. The Project Board gives direction and authorizes key decisions but does not manage day-to-day. The PM manages day-to-day in CS.

The Team Manager produces a Checkpoint Report to inform the Project Manager of progress against the Work Package plan.

Project Assurance is responsible for independent oversight, ensuring that the project adheres to standards and that the Project Board's interests are protected.

Option A is correct because Stage Plans in PRINCE2 are formally approved by the Project Board at the end of the current stage (or at the start of the next stage) as part of the 'Manage a Stage Boundary' process. The Project Board uses the Stage Plan to authorize the work for the upcoming stage, ensuring it aligns with the Business Case and tolerances.

Project Assurance is an independent role, separate from Project Support.

The Business Case practice is responsible for establishing and maintaining the justification for the project, including the link between objectives and expected benefits. During the Initiating a Project process, the Business Case must be refined to ensure that all benefits are clearly traceable to the project's objectives, as this alignment is critical for ongoing viability decisions. The project manager should use the Business Case practice to address this gap by updating the Business Case to explicitly map each benefit to a specific project objective.

SU produces the Project Brief, the initiation stage plan, and the Daily Log. The PID is an output of IP, and the Benefits Management Approach is an output of IP.

The Executive (Senior Responsible Owner) is the owner of the Business Case. The Project Manager maintains (updates) the Business Case on behalf of the Executive.

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

Option C is correct because the Project Assurance role is specifically tasked with monitoring and reporting on the project's adherence to PRINCE2 standards, and it reports directly to the Project Board to provide independent oversight. This ensures that the Project Board receives objective assessments of the project's progress and compliance, separate from the Project Manager's perspective.

The purpose of Managing a Stage Boundary 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 Board is responsible for overall project governance, including authorizing the Project Plan (which defines the project's scope, cost, and schedule) and authorizing the start of each management stage. These decisions ensure the project remains aligned with business objectives and that stage boundaries are properly controlled.

According to PRINCE2, if a product fails its quality inspection, the Team Manager should raise an Issue Report (specifically, an Off-specification) to the Project Manager. The PM then decides how to handle it. Option D is correct; Option B is wrong because the Team Manager should not bypass the PM.

SU produces the Project Brief, Daily Log, and Initiation Stage Plan. PID is from IP.

The Product Description defines quality criteria and acceptance methods. Option C is correct.

Project Board meetings are held at key decision points (end of stages) and when exceptions occur. They are not scheduled at regular intervals but are exception-driven.

Option B is correct. Benefits Management Approach is created during Initiating a Project as part of the PID.

Directing a Project (DP) is the process used by the Project Board to authorize initiation, stage plans, exception plans, and closure.

The Project Manager uses the Controlling a Stage process to monitor progress, review Highlight Reports, and report to the Project Board via Highlight Reports.

The Senior User is responsible for specifying the requirements and ensuring the final product meets the agreed quality criteria.

These are five of the seven PRINCE2 processes.

The Lessons Report is produced during CP to document what went well and what could be improved, for the benefit of future projects.

The Project Board (in the Directing a Project process) is responsible for authorising project initiation, as well as authorising the project itself.

The Risk Register is the document used to record and track risks.

Avoid is the response where action is taken to eliminate the threat by changing the plan or approach.

The Project Board consists of the Senior Responsible Owner (Executive), Senior User, and Senior Supplier.

Team plans are created by the team manager during the Managing Product Delivery process.

The Team Manager produces Checkpoint Reports at intervals defined in the Work Package. These reports inform the Project Manager of progress against the Work Package.

Managing a Stage Boundary allows the Project Board to review the current stage's performance, approve the next Stage Plan, and update the Business Case.

Checkpoint Reports are produced within Managing Product Delivery (MP) by the Team Manager.

In PRINCE2, risk responses for opportunities include exploit, enhance, share, and reject. 'Enhance' is an appropriate response to maximize the probability or impact of an opportunity.

The Lessons Report is used to inform future projects and improve organizational project management. It should be shared with the relevant stakeholders and added to the organizational lessons database. It is not just filed or destroyed.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve its completion, and authorize the next stage plan. This ensures that the project remains viable and aligned with business justification before committing further resources.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets its stated requirements and is suitable for its intended use.

SU is a pre-project process to determine if the project is viable and worth initiating, while IP formally establishes the project foundation with detailed plans.

According to PRINCE2, the Project Manager is responsible for maintaining the Business Case, while the Executive (Senior Responsible Owner) owns it and is accountable for its justification.

In PRINCE2, the Business Case is the key document for justifying the project's continued viability. When the cost-benefit ratio becomes unfavorable, the project manager must escalate this issue to the project board, which holds the authority to approve changes to the Business Case or decide on project continuation. Option D is correct because the project manager's first action is to request a formal review by the project board, as per the 'continued business justification' principle and the 'manage by stages' theme.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides the baseline for project execution and is used to get approval to proceed.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, containing the business case, project plan, and other baselines.

The PID is approved by the Project Board, which includes all three roles (Executive, Senior User, Senior Supplier). The Project Manager prepares it but does not approve it.

Controlling a Stage is the process for managing day-to-day work within a stage, including the first stage.

A Request for Change proposes a modification to an approved baseline, while an Off-specification is something that should have been provided but was not, or that deviates from the baseline.

Managing Product Delivery is the process where Team Managers accept Work Packages, execute them, and deliver products. Checkpoint Reports are produced by Team Managers for the Project Manager. Highlight Reports are produced by the PM, and End Stage Reports are produced in Managing a Stage Boundary.

The Initiating a Project process produces the Project Initiation Documentation (PID), which is the definitive document that defines the project's scope, objectives, and approach. It also produces the Stage Plan for the next stage, which details the work, resources, and controls for the first management stage. These are mandatory outputs that enable the Project Board to authorize the project to proceed.

Checkpoint Reports are produced by the Team Manager (or the team) to inform the Project Manager of progress on Work Packages. The Project Manager receives them, not the Project Board. Option B is correct.

Option D is correct because, in PRINCE2, a Request for Change (RFC) is a formal proposal to modify an approved baseline (e.g., a product description or project plan), while an Off-specification (Off-spec) is an issue that arises when a product does not meet its agreed specification or quality criteria. The RFC seeks to change the baseline, whereas the Off-spec identifies a deviation from the existing baseline. This distinction is fundamental to PRINCE2's issue management and change control processes.