PRINCE2 Foundation (PRINCE2F) — Questions 826–900

The Highlight Report is produced by the Project Manager for the Project Board at regular intervals to summarize progress and issues.

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.

The purpose of the Managing a Stage Boundary process is to enable the Project Board to review the current stage, approve the next Stage Plan, and confirm continued business justification. Option C correctly describes this.

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.

A Request for Change (RFC) is a formal proposal to modify a baseline (e.g., a product, plan, or scope), while an Off-specification is a documented deviation where a product or component fails to meet its agreed specification or baseline requirement. In PRINCE2, an RFC seeks approval for a change, whereas an Off-specification identifies a non-compliance that must be resolved, often through a change request or concession.

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 is the PRINCE2 document specifically designed to capture, track, and manage all requests for change, including off-specifications, problems, and concerns. Since the project is experiencing many changes due to evolving requirements, the Project Manager must log each change request in the Issue Register to ensure proper impact analysis, decision-making, and audit trail. This aligns with the PRINCE2 practice of managing issues and changes through a controlled process.

In PRINCE2, an Off-specification is the correct record when a product fails to meet its agreed specification or quality criteria. The Project Manager logs this in the Issue Register as a type of issue, not a risk, change, or lesson, because the product already exists and does not conform to its defined requirements.

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.

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 'Directing 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 three roles: the Executive (Senior Responsible Owner), Senior User(s), and Senior Supplier(s). In this question, the two roles from the Project Board that are listed are Senior User (Option A) and Executive (Option E). Team Manager, Project Manager, and Project Support are not Project Board roles.

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.

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.

The Starting Up a Project process is the pre-project phase where the project is evaluated for viability before full initiation. Its key outputs include the Project Brief, which outlines the project's scope, objectives, and approach, and the Initiation Stage Plan, which details the work needed to produce the Project Initiation Documentation. These two outputs are formally defined in PRINCE2 as products of this process.

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 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 update the Project Plan and Business Case with any new information. This ensures that the project remains viable and aligned with business objectives before committing to the next stage.

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 is the PRINCE2 management product that defines the quality criteria, quality methods, and acceptance methods for a specific product. It is created during the Initiating a Project process and is used to ensure that the product meets its required quality standards before it is approved.

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.

The Benefits Management Approach is first produced during the Initiating a Project process, as it forms part of the Project Initiation Documentation (PID). Options A, B, and D are incorrect: Managing a Stage Boundary reviews and may update the approach, Closing a Project evaluates benefits, and Starting Up a Project does not create it.

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.

The correct matches are: Starting Up a Project ensures prerequisites are in place; Initiating a Project establishes the project's foundation. Common confusion: mixing up these two 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 Managing a Stage Boundary process is designed to provide the Project Board with the information needed to review the current stage's performance, approve the next Stage Plan, and update the Business Case and Project Plan. This ensures that the project remains viable and aligned with business objectives before committing further resources.

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.

In PRINCE2, the Team Manager produces a Checkpoint Report during the Managing Product Delivery process to inform the Project Manager of progress at a regular, predefined frequency. This report provides a snapshot of actual progress against the Work Package plan, including achievements, next steps, and any issues or risks. It is the primary mechanism for the Team Manager to communicate status to the Project Manager within this process.

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 update the Business Case and Project Plan. It ensures that the project remains viable and aligned with business objectives before committing further resources.

The Team Manager is executing the 'Managing Product Delivery' process because this process controls the work of the team, including the creation and delivery of products. A key activity within this process is the production of Checkpoint Reports, which provide the Project Manager with progress updates on the work assigned to the team. The Checkpoint Report is a formal PRINCE2 management product that is specifically defined as an output of the 'Managing Product Delivery' process.

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.

In PRINCE2, quality is defined as 'fit for purpose,' meaning the product meets the stated requirements and is suitable for its intended use. This definition aligns with the PRINCE2 principle of continued business justification, ensuring the product delivers value to the stakeholders. It is not merely about conformance to specification or zero defects, but about satisfying the user's needs in the operational environment.

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 definitive output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and Project Plan into a single, controlled document that defines the project's scope, objectives, and governance. PRINCE2 mandates that the PID is created and approved during this process to provide a firm foundation for the project.

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

After the Project Board authorizes the project and the first stage, the Project Manager uses the Controlling a Stage process to assign work, monitor progress, handle issues, and report to the Board throughout the stage. This process governs the day-to-day management of the stage and ensures it stays within tolerance.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product baseline (e.g., a specification or plan), while an Off-specification is a notification that a product has failed to meet its agreed baseline (e.g., a defect or missing requirement). Option A correctly captures this fundamental distinction: RFCs propose changes to baselines, whereas Off-specifications report deviations from baselines.

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.

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.

In PRINCE2, the Project Board is responsible for providing assurance that the project is being conducted properly. This includes ensuring that the project remains viable, that risks are managed, and that the business case is still valid. The Project Board delegates day-to-day management to the Project Manager but retains overall accountability and oversight through assurance activities.

The Project Manager maintains the Business Case, but the Executive (SRO) owns it and is ultimately responsible for ensuring business justification.