PRINCE2 Foundation (PRINCE2F) — Questions 1351–1425

The Senior User is primarily responsible for defining the benefits and ensuring the project delivers a product that meets user needs. When an Exception Report recommends a scope change, the Senior User must assess whether the change is justified from a user-benefit perspective, as they represent the interests of those who will use the project's output. In PRINCE2, the Senior User's role includes approving changes that affect the project's scope, ensuring they align with the business case and user requirements.

PRINCE2 separates the Project Manager from Project Assurance to ensure independent oversight of the project's direction, progress, and compliance with standards. This separation prevents conflicts of interest that would arise if the same person were responsible for both managing the project and objectively assessing its health. Project Assurance provides an impartial check on the Project Manager's decisions, ensuring that the project remains viable and aligned with business, user, and supplier interests.

The final activity in MP is to 'Deliver a Work Package', which involves handing over the completed products to the Project Manager and obtaining formal acceptance.

The Project Board authorizes the closure of the project after reviewing the End Project Report and Lessons Report, ensuring all products are accepted and benefits review plans are in place.

The Project Initiation Documentation (PID) is the definitive document that defines the project and forms the basis for its management. It is created during the Initiating a Project process.

During CS, the PM authorizes Work Packages and reviews the Business Case (if needed). Producing Highlight Reports is also a CS activity, but the question asks for two; authorizing Work Packages and reviewing the Business Case are both correct. Producing the End Stage Report is from SB.

The Initiating a Project process is where the project's baselines are established, and the key output is the Project Initiation Documentation (PID). The PID consolidates all the information needed to justify the project, define its scope, and provide a basis for decision-making. It is the definitive document that is approved by the project board to authorize the project to proceed.

The Project Manager produces an End Project Report and a Lessons Report, and then recommends closure to the Project Board.

The Quality Review technique is used to assess the quality of a product and identify defects. It is a form of quality control.

Authorizing Work Packages, reviewing progress, and escalating exceptions are all activities in CS. Producing the PID is done in IP. Approving the next Stage Plan is done by the Project Board in DP.

Highlight Reports are prepared by the Project Manager and sent to the Project Board (and possibly stakeholders) at regular intervals.

Option C is correct because PRINCE2 emphasizes that the project board must provide unified direction and timely decisions. When conflicting priorities arise, a facilitated session is a recognized technique to align the board's priorities, ensuring effective governance without bypassing the board's authority. This approach directly addresses the root cause—misalignment—rather than delaying, escalating prematurely, or reducing board involvement.

Managing Product Delivery is the process where the Team Manager executes the work and delivers completed products to the Project Manager for acceptance. Controlling a Stage is the PM's process for managing the stage; Managing a Stage Boundary focuses on stage end and next stage planning; Closing a Project handles final project closure.

A Product Description includes purpose, composition, derivation, format, quality criteria, quality method, and quality tolerance. Cost and benefits are not part of a Product Description; they are in the Business Case.

Option C is correct. Product Descriptions define the quality criteria, acceptance methods, and other details for each product. The Quality Management Approach defines the overall quality strategy.

A cautious appetite means risk-averse; even low probability opportunities may be rejected if they carry risk.

SU ensures that the project has a viable business case and necessary foundation before committing to full initiation. It checks if the project is worthwhile and doable.

In PRINCE2, the Directing a Project process is the decision-making layer where the Project Board exercises overall control. A key responsibility is authorizing the next Stage Plan, which formally approves the detailed plan for the upcoming management stage and commits the resources required to execute it. This ensures the project remains viable and aligned with business justification before proceeding.

PRINCE2 defines three types of issues: Request for Change, Off-specification, and Problem/Concern. Risk and change are not types of issues.

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager to inform about progress within a Work Package.

Project Assurance is an independent role that ensures the project remains aligned with business, user, and supplier interests.

An RFC proposes a change to baselined products, while an Off-spec identifies that a product does not meet its specification (a defect or non-conformance).

The risk owner is responsible for managing the risk and ensuring appropriate responses are implemented; the risk actionee is the person who carries out specific risk response actions.

In PRINCE2, the Senior Responsible Owner (SRO) is the single point of accountability for the project's success, as they own the Business Case and are ultimately responsible for ensuring the project delivers the expected benefits. The Project Manager is responsible for managing the project on a day-to-day basis but is not accountable for overall success. Option C correctly identifies the SRO's accountability, and option E correctly states that responsibility (for tasks) can be delegated, while accountability cannot.

The Project Board defines project-level tolerances; the Project Manager sets stage-level tolerances within them.

The Project Plan is created during Initiating a Project.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It consolidates all baselines for managing the project.

Project assurance is the responsibility of the Project Board, which provides independent assurance.

Expected benefits and major risks are key components of a Business Case in PRINCE2.

Directing a Project includes authorizing initiation and authorizing a stage or exception plan. Managing day-to-day work and producing the PID are not Board activities.

An RFC is a proposal for a modification to a product that has been baselined, while an Off-specification is a product that should be produced but is not meeting specifications.

During CS, the Project Manager authorizes Work Packages, reviews progress, and reports to the Project Board. Producing Checkpoint Reports is a Team Manager responsibility, and making decisions on project tolerances is a Project Board responsibility.

The Project Manager prepares the Highlight Report and sends it to the Project Board at regular intervals (e.g., weekly or monthly) to provide a summary of stage status.

The Starting Up a Project (SU) process produces the Project Brief and the Initiation Stage Plan. The Project Brief provides a high-level overview of the project's justification, scope, and approach, while the Initiation Stage Plan details the activities, resources, and controls for the initiation stage. Both are mandatory outputs of SU, ensuring the project has a clear mandate and a plan for the next phase before committing to full initiation.

Transferring the financial impact to a third party (insurance) is a 'transfer' response. 'Reduce' would involve actions to lower probability or impact. 'Accept' would be to take the risk without action.

The Project Board authorises initiation as part of the Directing a Project process. The Executive is a member of the Project Board, but the decision is taken collectively by the Board.

Project Support and Change Authority are optional roles in PRINCE2. The other roles are mandatory.

Options B and D are correct. The recommended risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate. 'Assess' includes both probability and impact evaluation. 'Implement' involves executing the planned responses. 'Monitor' and 'Control' are not separate steps; they are part of Implement and Communicate.

Product-based planning follows: write Project Product Description, create Product Breakdown Structure, create Product Flow Diagram, then produce Product Descriptions for each product.

In PRINCE2, when a project is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board via an Exception Report. This is because the Project Manager does not have authority to exceed tolerances; the Project Board must decide whether to approve a revised Business Case, adjust tolerances, or terminate the project. Option C correctly follows the PRINCE2 principle of management by exception.

Option C is correct because during the Initiating a Project process, the Business Case is reviewed to develop a detailed justification for the project and confirm it remains viable. This involves refining the outline Business Case from the Starting Up a Project process into a fully detailed document that justifies the project's continued existence based on costs, benefits, risks, and timescales. The review ensures the project is still aligned with corporate objectives and that the investment is worthwhile before proceeding to the next stage.

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

Threat response strategies include Avoid, Reduce (Mitigate), Fallback, Transfer, Accept, and Share. Exploit is an opportunity response, not a threat response.

The Project Initiation Documentation (PID) is the key output of IP, consolidating all the information needed to decide whether to authorize the project.

In PRINCE2, when a Work Package is forecast to exceed its tolerance, the Project Manager must first discuss with the Team Manager to understand the situation and explore options. This aligns with the 'manage by exception' principle, where the PM is responsible for managing within stage tolerances and only escalates to the Project Board if the stage tolerance itself is threatened. The PM must gather detailed information before deciding on corrective actions or escalation.

Option C is correct. When a stage tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board immediately via an Exception Report — this is PRINCE2's management by exception principle. The Project Manager cannot unilaterally exceed tolerances (A), continue without escalation (B), or close the project without Board decision (D).

The Project Board is responsible for providing overall direction, approving plans, and ensuring assurance. Producing Highlight Reports is the PM's responsibility; managing risks on a daily basis is the PM's role.

Managing a Stage Boundary: plan next stage, update project plan, update business case, report, and produce exception plan if required.

Project Assurance is an independent, ongoing role providing objective oversight to the Project Board. Quality review is a specific technique for reviewing product quality at defined points.

The Project Initiation Documentation (PID) is the primary output of the Initiating a Project process. It provides the basis for the Project Board to decide whether to proceed.

A Request for Change is a proposal for a modification to a product that has been baselined, while an Off-specification is something that should be provided but is not (or is forecast not to be). The key difference is that RFC is about changing what was agreed, whereas Off-spec is about failing to deliver what was agreed.

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

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It defines the project and forms the basis for its management. The Project Plan is part of the PID.

The Benefits Management Approach defines how the project's benefits will be measured, tracked, and realized throughout the project and into operations. Since the project board is concerned about benefits realization, updating this approach with revised measurement criteria, review timing, or ownership details directly addresses their concern by providing a clear plan for ensuring benefits are achieved.

Option D is correct because in PRINCE2, the Highlight Report is a formal report from the Project Manager to the Project Board, providing a summary of progress, risks, and issues at predefined intervals during a stage. The Checkpoint Report is produced by the Team Manager for the Project Manager, detailing progress against the Work Package. This distinction in audience and purpose is a core PRINCE2 principle.

The 'Tailor to suit the project environment' principle directly addresses the need to adapt PRINCE2 to the specific context of the project, including its size, complexity, importance, capability, and risk. For a complex infrastructure project, this means adjusting management products, roles, and processes (e.g., simplifying the Business Case or using a more detailed Risk Register) to fit the project's unique technical and organizational environment, ensuring the method remains effective without being overly burdensome.

A Request for Change is a proposal for a change, while an Off-specification is something that should be there but isn't.

PRINCE2 defines three issue types: Request for Change, Off-specification, and Problem/Concern. Options A, B, and D are correct. Options C and E are not issue types.

The correct answer is D, Initiating a Project, because this process is where the Project Board reviews the Initiation Stage Plan and the Business Case, then formally authorizes the project to proceed by approving the project initiation. This authorization triggers the transition from planning to execution, giving the Project Manager authority to start the first delivery stage.

The PID includes the Business Case, Project Plan, and Risk Register. The Lessons Log is separate; the Work Package is created later.

The Project Initiation Documentation (PID) is the key document created during the Initiating a Project process that defines how the project will be controlled. It consolidates the project's scope, objectives, and controls, including the management stages, tolerances, and reporting arrangements, providing a baseline for decision-making and governance throughout the project.

The Project Board meets at key decision points, which are exception-driven (when tolerances are forecast to be exceeded) and at stage boundaries. Option D is correct.

In PRINCE2, threat responses are actions taken to address negative risks. 'Reduce' (also called 'Mitigate') is a valid response that aims to lower the probability and/or impact of a threat to an acceptable level. This is one of the five standard threat response categories defined in the PRINCE2 risk management practice.

The Business Case includes expected benefits and costs (investment appraisal). Options A and B are correct. Options C, D, and E are not standard components.

The 'Manage by Exception' principle is applied when the Project Manager escalates a forecast tolerance deviation to the Project Board. This principle delegates decision-making authority within defined tolerances; only when a deviation is forecast to exceed those tolerances does the Project Manager escalate to the Project Board for a decision. The escalation triggers exception management, ensuring the board retains control at key decision points without micromanaging day-to-day activities.

The Business Case includes expected benefits, costs, timescales, major risks, etc. Options, investment appraisal, and dis-benefits are also components.

Starting Up a Project (SU) is the pre-project process that produces the Project Brief, which includes the outline business case and project approach. Initiating a Project (IP) is the second process that produces the Project Initiation Documentation (PID), which contains the detailed plans, business case, and risk register needed to justify proceeding with the project. The key distinction is that SU creates the high-level Project Brief, while IP creates the comprehensive PID.

When the Project Board receives an Exception Report, they typically request an Exception Plan to evaluate options. They then decide whether to approve the plan, which may involve changes to the project. A new Project Plan may be part of the Exception Plan, but the immediate step is to request the plan.