PRINCE2 Foundation (PRINCE2F) — Questions 1126–1200

The Checkpoint Report is a PRINCE2 management product used by the Team Manager to report on team-level progress to the Project Manager at a frequency defined in the Work Package. Its purpose is to provide the Project Manager with information on team progress, including completed work, planned activities, and any issues or risks, enabling informed decision-making without escalating to the Project Board.

The 'Reduce' response involves actions to lower the probability and/or impact of a threat. The scenario describes reducing probability, which fits 'Reduce'. 'Avoid' would change the plan to eliminate the risk; 'Transfer' would shift the risk to a third party; 'Accept' would acknowledge the risk without action.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets its stated requirements and acceptance criteria.

In PRINCE2, opportunity responses are specific actions to address opportunities (positive risks). 'Enhance' is a correct response because it involves proactively increasing the probability and/or impact of an opportunity, such as allocating additional resources to maximize a potential benefit. 'Exploit' is also correct as it seeks to ensure the opportunity is realized by making it happen, often by assigning ownership or implementing a specific plan.

In PRINCE2, management by exception means the Project Manager must escalate to the Project Board when a stage tolerance is forecast to be exceeded. The correct action is to raise an Exception Report.

In PRINCE2, the Change Management Approach is created during the Initiating a Project process to define how issues, changes, and configuration items will be managed throughout the project. It specifies the procedures for capturing, assessing, and deciding on issues and change requests, including the roles and responsibilities involved. This document ensures a consistent and controlled approach to handling changes, which is critical for maintaining project stability.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case, ensuring the project remains viable and aligned with organizational objectives. This includes approving the Business Case at initiation and any subsequent changes, as well as securing the necessary funding. The SRO also chairs the Project Board, providing overall leadership and direction, and is ultimately responsible for the project's success.

The Project Plan is approved by the Project Board as part of the PID approval.

The Quality Management Approach is the correct document because it defines the project's quality management strategy, including both quality assurance (systematic checks to ensure the project is using appropriate processes) and quality control (specific activities to verify that products meet their quality criteria). This is a key PRINCE2 management product that sets out how quality will be planned, performed, and governed throughout the project lifecycle.

PRINCE2 is a process-based project management methodology that focuses on business justification, defined roles, and product-based planning. It explicitly excludes detailed human resource management techniques such as team motivation, conflict resolution, and performance appraisals, which are typically covered by general management disciplines. Therefore, human resource management is not covered by PRINCE2.

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 project's lifecycle from initiation through closure, ensuring that the board authorizes each stage, reviews progress, and provides strategic direction without getting involved in day-to-day management.

The Project Manager uses Checkpoint Reports to monitor progress and compile the Highlight Report for the Project Board.

The Directing a Project process is designed to enable the Project Board to make key decisions and exercise overall control over the project, from initiation through closure. It provides a framework for the Board to authorize project initiation, approve stage plans, monitor progress via highlight reports, and authorize closure, ensuring strategic alignment and governance.

A Request for Change is a proposal for a change to a product that has been baselined; an Off-specification is a product that does not meet its specification.

A Checkpoint Report is a progress report from the Team Manager to the Project Manager, typically covering the frequency defined in the Work Package.

The Project Manager is responsible for creating the Project Initiation Documentation (PID) because PRINCE2 assigns the Project Manager the role of assembling and producing the PID, which consolidates key planning documents like the Business Case, Project Plan, and Risk Register. The Project Board approves the PID, but does not create it, as the Project Manager acts as the single point of accountability for its preparation and quality.

The Senior User is responsible for defining the project's acceptance criteria because they represent the interests of those who will use the project's products. Acceptance criteria specify the conditions that must be met for the project's outputs to be accepted by the users, and the Senior User ensures these criteria reflect actual user needs and business requirements. This role is defined in PRINCE2's 'Business Case' and 'Quality' management products, where the Senior User provides the user perspective on quality expectations.

Project Assurance provides independent oversight, not management or support. It checks that the project is being run correctly.

Issues that threaten tolerances or require changes to baselines should be escalated. The PM manages issues within their authority.

PRINCE2 provides a structured framework with defined processes, roles, and management products, which encourages consistency in how projects are delivered across an organization. This standardization reduces variability in project execution and improves repeatability of successful practices.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two defined types of issue are Request for Change (a proposal for a change to the product's specification or baseline) and Off-specification (something that should be provided but is not, or is provided incorrectly). These are formally documented and managed through the issue and change control procedure.

An Exception Plan is approved by the Project Board, and the project then returns to the Controlling a Stage process to execute the plan.

In PRINCE2, 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 because tolerances are delegated authority limits; exceeding them requires the Project Board's decision to either approve a revised plan or take corrective action. Option D correctly follows the PRINCE2 exception management process, ensuring governance and control are maintained.

B is correct because PRINCE2's continued business justification principle requires that the business case remain viable throughout the project. As project manager, you must escalate to the project board for an immediate review when the senior user raises concerns about benefits and market changes. If the business case is no longer viable, the project should be stopped to avoid further waste of resources, regardless of sunk costs.

In PRINCE2, the Project Board is ultimately accountable for the project's success, and it delegates the task of providing independent assurance to the Project Assurance role. This ensures that the project is being managed correctly, in line with the business case, and that all management stages are compliant with PRINCE2 principles. The Project Board (via Project Assurance) is the correct answer because it is the only role with the authority to provide objective, independent oversight, separate from the day-to-day management performed by the Project Manager.

Project Assurance is an independent role that checks the project is on track and cannot be delegated to the Project Manager. It supports the Board.

PRINCE2 defines three issue types: Request for Change, Off-specification, and Problem/Concern. 'Risk' and 'Change budget' are not issue types.

The Quality Review technique in PRINCE2 is a structured assessment to evaluate whether a product meets its defined quality criteria and is fit for purpose. Its primary purpose is to identify defects and ensure the product is complete and correct before it is approved for use. This aligns with option B, as the review focuses on verifying product quality rather than planning or risk management.

The Quality Management Approach defines the quality procedures, techniques, and responsibilities for the project.

The risk owner manages the risk overall; the risk actionee performs specific actions.

The Project Board is accountable for the project and must ensure that independent assurance is in place. The Executive (SRO) often appoints assurance roles, but ultimate responsibility lies with the Project Board.

Escalation via Exception Report is required when a tolerance is forecast to be exceeded.

Options A, D, and E are correct. The Project Initiation Documentation (PID) includes the Project Plan, Risk Management Approach, and Business Case. The Highlight Report is a product of the Controlling a Stage process, and the Checkpoint Report is a product of the Managing Product Delivery process.

The risk owner manages the risk and is accountable for its management. The risk actionee carries out specific actions but is not accountable. This is a key distinction in PRINCE2 risk practice.

PRINCE2's principle of 'continued business justification' and the requirement for unified direction mandate that the project board make decisions by consensus, not by majority vote. The project board represents business, user, and supplier interests as a single cohesive unit; majority voting would risk dividing the board and undermining the principle of unified direction, as it could allow one interest to override others without full agreement.

The Project Manager is responsible for reviewing progress against the stage plan and taking corrective action when deviations occur, as defined in the Controlling a Stage process. This ensures the stage remains within tolerance and aligns with the project plan.

The Project Initiation Documentation (PID) is the key document created during the Initiating a Project process. It provides a comprehensive baseline that defines the project's scope, objectives, approach, and controls, against which the project's progress and performance are managed throughout its lifecycle.

This is an Off-specification because the product cannot meet a defined quality criterion specified in the product description. In PRINCE2, an off-specification is a type of issue that occurs when a product's actual or forecast quality does not match its agreed specification. The Team Manager has identified a deviation from the baseline, which is the defining characteristic of an off-specification.

The Checkpoint Report is a progress report on the work completed within a Work Package during a specific period. According to PRINCE2, the Team Manager is responsible for producing the Checkpoint Report to inform the Project Manager of progress against the Work Package plan.

In PRINCE2, the Project Board is responsible for authorizing the initiation of a project. This occurs at the end of the Starting Up a Project process, when the Project Board reviews the Project Brief and decides whether to proceed with the Initiation Stage. The Project Board's authority is defined in the project's governance framework, and it must formally approve the initiation plan before the Project Manager can begin detailed planning.

The integrated elements are the principles, practices (themes), and processes. Tailoring is how they adapt, but it is not an element itself. The project mandate is an input.

In the Controlling a Stage process, after a Team Manager reports that a product is complete, the Project Manager must first review the product to confirm it meets the quality criteria defined in the Product Description. This is part of the 'Review Work Package' activity, ensuring that the product is fit for purpose before any further actions, such as reporting or planning, occur. Only after this quality check can the Project Manager proceed to other activities like updating logs or sending reports.

The Closing a Project process produces the End Project Report, which provides a summary of the project's performance and lessons learned. The Project Product Description is an input to the Closing a Project process, not an output. The other options (Benefits Management Approach, Lessons Log, Project Plan) are also inputs or earlier outputs, not deliverables of the Closing a Project process.

The Project Board is chaired by the Executive, also known as the Senior Responsible Owner (SRO). This role has overall accountability for the project's success, ensuring it delivers the required business justification and remains aligned with organizational strategy. The Executive chairs the board to provide leadership and make key decisions, not the Senior User, Senior Supplier, or Project Manager.

Options A, B, and D are correct. The three types of issue are: Request for Change (RFC), Off-specification, and Problem/Concern. 'Risk' is not an issue; it is a potential future event. 'Change' is a general term, not a specific type.

The Project Manager assists the Executive in preparing the Project Brief and other initiation documentation.

The Project Board must authorize project closure through the Directing a Project process. The PM prepares the recommendation, but only the Board can formally close.

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, monitoring, and controlling project activities, escalating issues or deviations that exceed tolerances. The Project Board sets the overall direction and tolerances but does not manage daily tasks.

The primary purpose of the End Stage Report in the Managing a Stage Boundary process is to provide the Project Board with a summary of the stage's performance against the plan, including progress, issues, and risks, so they can make an informed decision on whether to authorize the next stage. This aligns with PRINCE2's principle of management by stages, where the board reviews stage-end information to confirm continued business justification.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case throughout its lifecycle. This role owns the Business Case and ensures the project remains viable, justified, and aligned with organizational objectives from initiation through closure.

The Lessons Log is used to capture lessons throughout the project, including during a stage.

D is correct because PRINCE2 requires the Project Manager to escalate any forecast deviation beyond tolerance to the Project Board via an Exception Report. This triggers a formal decision process, ensuring the board can authorize corrective action before the situation worsens.

The Senior User is responsible for defining the acceptance criteria as they represent the users who will accept the final product.

A is correct because the Project Manager is responsible for preparing Stage Plans, which detail how the work for a management stage will be executed, including schedules, resources, and controls. This is a core PRINCE2 responsibility as the Project Manager translates the Project Plan into actionable Stage Plans for the Project Board's approval.

The Lessons Log is the PRINCE2 document specifically designed to capture and reference lessons from previous projects. During Initiation, the project manager should review the Lessons Log to identify relevant lessons that can inform planning and avoid past mistakes. The other documents serve different purposes and are not the primary source for historical lessons.

SU is a pre-project process to check viability; IP is the full initiation to establish the project on a solid foundation, creating the PID.

The Initiating a Project process is where the Project Board and Project Manager agree on the detailed planning required to deliver the project. The key output is the Project Initiation Documentation (PID), which consolidates all the baselines (including the Business Case, Project Plan, and Project Brief) into a single, approved document that defines what the project will deliver, how it will be delivered, and the controls to be applied. Without the PID, the project cannot proceed to the next stage.

Administering quality reviews is a core administrative task of Project Support, ensuring that review meetings are scheduled, documented, and follow-up actions are tracked. This role provides the logistical and clerical backbone for quality management activities within a PRINCE2 project.

The two correct PRINCE2 principles are 'Manage by Exception' (B) and 'Tailor to suit the project environment' (D). Options A (Business Case) and C (Risk Management) are PRINCE2 themes, not principles. Option E (Project Support) is not a PRINCE2 principle.

The Senior Supplier is responsible for providing the project's products and ensuring they meet the specified quality criteria. This role represents the suppliers who design, develop, and deliver the products, and thus bears the accountability for product quality against the defined acceptance criteria.

In PRINCE2, an Exception Plan is triggered when a stage tolerance is forecast to be exceeded. The Project Board authorizes this plan to address the deviation and keep the project on track. This is a key control mechanism within the Directing a Project process.

PRINCE2 defines Project Assurance as an independent oversight function that monitors compliance with the project's management stages, while Project Support provides administrative and clerical help to the Project Manager and team. This distinction is fundamental to PRINCE2's separation of assurance from management and support roles.

The Project Board authorizes initiation, authorizes stage plans, and gives ad-hoc direction. Producing Highlight Reports and managing day-to-day issues are PM/CM responsibilities.

The Project Board is responsible for ensuring that project assurance is independent of the Project Manager, making Option C the correct answer.

Project Assurance provides an independent check that the project is being conducted properly, reporting directly to the Project Board, while Project Support assists the Project Manager with administrative and coordination tasks. This separation ensures objectivity in oversight without compromising the Project Manager's authority.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress updates on work packages, including actual versus planned progress, quality activities, and any issues or risks. The Team Manager is the role that manages the day-to-day work of the team and reports back to the Project Manager.

'Tailor to suit the project environment' is one of the seven PRINCE2 principles. This principle requires that the method be adapted to the specific context of the project, including its size, complexity, importance, capability, and risk, ensuring that PRINCE2 is applied appropriately without unnecessary bureaucracy.

The Quality Management Approach defines how quality will be managed, including methods and tools.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The three defined types of issue are Request for Change (C), Off-specification (E), and Problem/Concern. Option C is correct because a Request for Change is a formal proposal for a modification to a product's specification or baseline, which is a standard type of issue in the PRINCE2 issue management procedure.