PRINCE2 Foundation (PRINCE2F) — Questions 301–375

The Project Manager is responsible for producing and maintaining the Project Plan, as defined in PRINCE2's management products. This includes defining the project's stages, activities, dependencies, and resource estimates, and ensuring the plan aligns with the Business Case. The Project Manager owns the planning process and is accountable for the plan's accuracy and updates throughout the project.

In SB, the PM produces the End Stage Report, updates the Project Plan, and produces a Stage Plan for the next stage. Authorizing work packages is done in CS. Producing Highlight Reports is done in CS.

The separation ensures independent oversight. The Project Manager is responsible for day-to-day management, while Project Assurance provides an impartial view to the Project Board to avoid conflicts of interest.

A Highlight Report is sent from the Project Manager to the Project Board regularly, while a Checkpoint Report is sent from the Team Manager to the Project Manager more frequently.

PRINCE2 provides a common language and improves communication, and it ensures a focus on business justification through the Business Case. It does not eliminate the need for project managers nor guarantee successful delivery.

The End Stage Report in PRINCE2 serves a dual purpose: it summarizes the current stage's performance against the plan and requests authorization to proceed to the next stage. This aligns with the PRINCE2 principle of managing by stages, where each stage ends with a formal review and decision point. The report provides the Project Board with the necessary information to approve continued investment.

When an Exception Plan is approved, the project board authorizes the project manager to proceed with the plan. This triggers the Managing a Stage Boundary process because the exception plan replaces the current stage plan, requiring a formal stage boundary to update the project plan, business case, and risk register before the next stage begins.

Managing Product Delivery involves accepting the work package, executing the work, delivering the products, obtaining approval, and then reporting completion.

An RFC is a proposal for a modification (change) to the project's products, while an Off-specification is a situation where a product does not meet its specification (a deviation).

Manage by stages is the most important principle because it requires the project to be planned, monitored, and controlled in discrete stages, with each stage authorizing the next only after a formal review. In a highly regulated environment, this creates clear, auditable decision points (e.g., stage boundary approvals) that external auditors can trace. The project manager can document stage plans, exception reports, and end-stage assessments as explicit evidence of governance.

The Risk practice in PRINCE2 is specifically designed to identify, assess, and control uncertainties that could affect the project's objectives. During the initiation stage, the project manager applies this practice to systematically identify major risks, evaluate their probability and impact, and plan appropriate responses, ensuring proactive management of threats and opportunities.

In PRINCE2, during the Controlling a Stage process, the Project Manager receives Checkpoint Reports from Team Managers. The Project Manager uses the information from these reports to compile the Highlight Report for the Project Board. Therefore, the correct action is to use it to compile the next Highlight Report.

The Starting up a Project (SU) process in PRINCE2 is the pre-project phase where the project is evaluated before any detailed planning begins. During SU, the Project Brief is created to outline the project's scope, objectives, and approach, and the Business Case is developed at a high level to justify the project's viability. Both documents are essential for the Project Board to decide whether to proceed to the Initiation Stage.

Project Assurance is an independent monitoring function, separate from the project management team, that ensures the project remains compliant with PRINCE2 principles and controls. Project Support, in contrast, is a service-oriented function that provides administrative and clerical services to the project manager and team, such as maintaining logs, filing, and scheduling. Option B correctly captures this distinction: independence for assurance versus administrative services for support.

The Business Case is the document that justifies the project by providing the justification, costs, benefits, and risks. During the initiation stage, the project manager develops the Business Case to confirm that the project is viable and aligns with corporate objectives. The Project Board then reviews and approves it to authorize the project to proceed.

In PRINCE2, the risk owner is the person who is accountable for the management and monitoring of a specific risk, including ensuring that appropriate response actions are planned and executed. The risk actionee, on the other hand, is the person assigned to implement the specific response actions defined for that risk. Option B correctly captures this distinction: the risk owner is accountable, while the risk actionee implements the response actions.

The Project Board is the decision-making body that reviews Exception Plans when a stage is forecast to exceed its tolerances. This review is performed as part of the 'Directing a Project' process, which covers board-level decisions such as approving exception plans, mid-stage corrections, and project closure. The board does not execute the plan; it authorizes or rejects it.

Directing a Project includes authorizing initiation, authorizing stages, giving ad-hoc direction, and authorizing closure. Producing Highlight Reports is for the PM during Controlling a Stage. Appointing the Project Manager is during Starting Up a Project.

The Business Case includes reasons, expected benefits, costs, timescale, etc.

Project Assurance is the Project Board's responsibility, but it can be delegated to individuals or teams independent of the Project Manager.

The Lessons Report is produced during the Closing a Project process to capture lessons learned for future projects.

The Project Board uses the Directing a Project process throughout the project, including authorising closure. Closing a Project is the process that produces the recommendation, but the decision to close is taken by the Project Board via Directing a Project.

The Team Manager is responsible for delivering one or more Work Packages as defined in the Stage Plan. This role focuses on the technical delivery of products within the constraints agreed with the Project Manager, ensuring quality, time, and cost targets are met for those specific work packages.

The risk owner is responsible for managing the risk overall. The risk actionee is responsible for carrying out specific risk response actions.

A Request for Change is a proposal for a change that would modify agreed baselines or requirements. An Off-specification is something that should be provided but is not currently present (or is incorrect).

During the Managing Product Delivery process, the Team Manager is responsible for producing the Checkpoint Report. This report provides a regular update on progress against the Work Package, including actual time and resources used, quality activities completed, and any issues or risks. It is the primary communication from the Team Manager to the Project Manager during the work delivery phase.

The Starting Up a Project (SU) process produces the Project Brief, which outlines the project's scope, objectives, and feasibility. The Initiating a Project (IP) process then uses that brief to develop the detailed Project Initiation Documentation (PID), which includes the Business Case, plans, and risk assessment. This distinction is fundamental because SU is a pre-project process to ensure there is a viable idea, while IP is the detailed planning phase that creates the management documents needed to proceed.

The Project Initiation Documentation (PID) is the definitive output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single baseline that defines 'what, why, who, when, and how' for the project. The PID is formally approved by the Project Board at the end of initiation, authorizing the project to proceed to the next stage.

Project Assurance is an independent oversight function, performed on behalf of the Project Board, to ensure that the project is being conducted correctly and remains viable. Project Support, in contrast, is a set of administrative and advisory services provided to the Project Manager to help them manage the project effectively. This distinction is fundamental to PRINCE2's separation of 'doing' from 'checking'.

The Product Breakdown Structure (PBS) in PRINCE2's product-based planning technique is a hierarchical diagram that decomposes the final project output into all the component products (both management and specialist) that must be created. It ensures that the project scope is fully defined before any activity planning begins, directly supporting the 'focus on products' principle. Option A correctly identifies this purpose.

The Business Case includes: reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The Quality Register is a separate document used for tracking quality activities.

The Project Board is responsible for authorizing the movement from one stage to the next, which includes approving the Stage Plan for the next stage and reviewing the current stage's completion. This is a key control point in PRINCE2's stage-gate management approach, ensuring that the project only proceeds when the Board is satisfied with progress and the business case remains viable.

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager as part of Managing Product Delivery.

Project Assurance is a role within the PRINCE2 management structure, responsible for ensuring that the project remains viable and compliant with the business case, while a quality review is a technique used to assess the quality of a product. Option D correctly distinguishes between these two concepts: Project Assurance is a role, and quality review is a technique. This aligns with PRINCE2's separation of management responsibilities from quality control activities.

The End Stage Report is produced during the Managing a Stage Boundary process to summarize the current stage's performance and inform the Project Board's decision to authorize the next stage.

The Initiating a Project process is where the project's scope, objectives, and approach are fully defined and documented. Its key output is the Project Initiation Documentation (PID), which consolidates all the baseline plans and strategies needed to justify and manage the project. The PID replaces the Project Brief, which is created earlier in the Starting Up a Project process.

When a work package tolerance is forecast to be exceeded, the team manager should inform the Project Manager via a Checkpoint Report so the PM can assess impact.

When the Project Board authorizes a stage plan, the next process to execute is Controlling a Stage, where the Project Manager manages the work of that stage.

The Starting Up a Project (SU) process is designed to evaluate the project's viability by creating the Project Brief and checking if the project is worthwhile, while the Initiating a Project (IP) process focuses on establishing a solid management foundation by creating the Project Initiation Documentation (PID) and detailed plans for how the project will be managed and controlled.

In PRINCE2, the Project Board is responsible for authorising the start of a project. This occurs at the end of the Initiating a Project process, when the Project Board reviews the Project Initiation Documentation and gives approval to proceed with the project. The Project Board provides overall direction and control, ensuring the project aligns with business, user, and supplier interests.

The Team Manager must escalate the issue to the Project Manager promptly, as they cannot exceed Work Package tolerances without authorization. The Project Manager will then handle the escalation.

The Project Manager manages day-to-day activities, produces Highlight Reports for the board, and updates the Business Case as needed. The PM does not chair the board or perform assurance.

The Team Manager is responsible for delivering Work Packages and managing the team's day-to-day work, reporting to the Project Manager.

The Starting Up a Project process is responsible for appointing the Executive and the Project Manager because it occurs before the project is formally initiated. During this pre-project process, the project mandate is reviewed, and key roles are assigned to ensure the project has the necessary leadership and management before proceeding to the Initiation Stage.

According to PRINCE2, when an Off-specification is identified, the Project Manager must first log it in the Issue Register and assess its impact. This ensures that all issues are formally recorded and evaluated before any corrective action is taken, maintaining control over project baselines.

Team Manager and Project Assurance are PRINCE2 roles. The others are not.

'Expected benefits' is a core component of the Business Case in PRINCE2, quantifying the justification for the project. Option C is correct because 'Major risks' are also a required component, as the Business Case must include an assessment of the risks that could affect the project's viability.

PRINCE2 promotes a common vocabulary and provides a framework for consistent project management. It does not guarantee cost savings or eliminate all risks.

In PRINCE2, when a project forecasts exceeding its stage-level cost tolerance, the Project Manager must first escalate the issue to the Project Board by raising an Exception Report. This is because the Project Manager does not have authority to exceed the delegated tolerance; the Project Board must decide on corrective action, such as approving a revised plan or closing the project. Option C is correct as it aligns with the PRINCE2 principle of management by exception.

The Project Board authorises initiation, stage plans, and project closure. They do not create Work Packages (PM does) nor approve Checkpoint Reports (PM receives them).

The Project Manager uses the Controlling a Stage process to monitor progress, review Work Packages, and manage issues. Checkpoint Reports are received from Team Managers during CS.

In PRINCE2, accountability refers to the ultimate answerability for the successful completion of a deliverable or objective, and it is always held by a single person (e.g., the project manager is accountable for the project). Responsibility, in contrast, can be shared among multiple team members or delegated to others who perform the work. Option B correctly captures this distinction, which is fundamental to the PRINCE2 management product structure and role definitions.

The Senior Responsible Owner (SRO/Executive) is the single person ultimately accountable for the project's business justification. They own the Business Case and are responsible for ensuring it remains viable, aligned with corporate strategy, and is formally reviewed at key decision points (e.g., stage boundaries). The PRINCE2 principle of continued business justification places this accountability squarely on the Executive, not on the Project Manager or support roles.

The Managing Product Delivery process is designed to control the link between the Project Manager and the Team Manager(s) by ensuring that work on products is authorized, executed, and delivered according to the agreed quality criteria and acceptance requirements. Its primary purpose is to create and deliver the project's products to the specified quality standards, as defined in the Product Description and Work Package.

Highlight Reports are produced by the Project Manager and sent to the Project Board during Controlling a Stage.

Controlling a Stage includes authorizing work, reviewing progress, assessing stage status, reporting to the Project Board, and taking corrective action as needed.

The Change Authority role is specifically authorized to approve Requests for Change within delegated limits set by the Project Board. This delegation allows the Change Authority to make decisions on low-impact changes without requiring full Board approval, streamlining the change control process.

In PRINCE2, the Project Manager, Project Board, and Team Manager are all mandatory roles within the project management team. Project Support is the only optional role, as its responsibilities can be absorbed by the Project Manager or other team members, or provided by a separate office like a PMO. The PRINCE2 manual explicitly states that Project Support is not a required role, making D the correct answer.

The Project Board is accountable for the project's success, meets exception-driven, and comprises SRO, Senior User, and Senior Supplier. It does not meet regularly; it meets when exceptions occur or at stage boundaries.

The Senior Responsible Owner (Executive) is accountable for the Business Case throughout the project in PRINCE2. This role owns the Business Case, ensures it remains viable, and is responsible for the project's justification and continued alignment with organizational objectives. The Executive is the ultimate decision-maker and must approve any changes to the Business Case.

The Senior Responsible Owner (Executive) is the single point of accountability for ensuring the project delivers value for money and remains aligned with the organization's business strategy. This role owns the business case, approves key stage boundaries, and has ultimate authority over project funding and continuation, directly linking project outputs to strategic objectives.

SB includes planning the next stage, updating the project plan, reporting on the current stage (End Stage Report), and capturing lessons. Authorizing Work Packages is done in CS, and delivering products is in MP.

The Directing a Project process is the only process that is exclusively for the Project Board, providing overall direction and control. It includes key decision points such as authorizing project initiation, ad hoc direction, and authorizing project closure. The Managing a Stage Boundary process also involves the Project Board because it requires the board to approve the End Stage Report and the next Stage Plan, thereby making a key decision to proceed.

During SU, the Executive and the Project Manager are appointed. The Project Board is also appointed, but the question asks for two specific roles. The Senior User and Senior Supplier are part of the Project Board but may be appointed later if not already in place.

The Business Case in PRINCE2 is a document that justifies the project's initiation and continued viability. It contains components such as Expected Benefits, Investment Appraisal, and Major Risks. The Risk Register is a separate management product used to record and track identified risks, not a component of the Business Case itself.

Directing a Project is the process that covers the Project Board's decision-making and direction-giving activities throughout the project, including ad-hoc direction.

In PRINCE2, during the Initiation Stage, the Project Manager does not have authority to approve scope changes. Any issue that could impact the Business Case or project viability must be formally documented as an Issue Report and escalated to the Project Board for a decision. This ensures governance is maintained and the Business Case remains viable.

Expected benefits and major risks are key components of the Business Case. Options and timescale are also components but not listed as correct in this set; the question asks for exactly two.

The Project Board is responsible for providing overall direction and control to the project, which includes approving key documents such as the Project Initiation Documentation (PID). The PID formalizes the project's scope, objectives, and plans, and board approval is required to authorize the project to proceed.