PRINCE2 Foundation (PRINCE2F) — Questions 1501–1575

The 'manage by stages' principle requires that the project manager plans only one stage at a time in sufficient detail, while the next stage is planned just before it begins. In a distributed team with time zone delays, the first step is to plan the next management stage with clear communication milestones that explicitly account for time zone differences, ensuring that stage boundaries and decision points are synchronized despite the delays.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It forms the basis for management decision-making.

If a stage is within its tolerances, the Project Board authorizes the next stage. If tolerance is exceeded, an Exception Plan should be requested or the project may be closed.

The Risk Management Approach and Benefits Management Approach are both management products created during the Initiating a Project process. The Risk Management Approach defines how risk will be managed throughout the project, while the Benefits Management Approach defines how the project's benefits will be realized and measured. These are documented in the Project Initiation Documentation (PID) and are key outputs of this process.

The Executive is accountable for the Business Case, appoints the Project Manager, and chairs the Project Board. Providing customer assurance is the Senior User's role; producing Highlight Reports is the Project Manager's role.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information—such as the current stage's performance, updated business case, and the next stage's plan—to make an informed decision about whether to authorize proceeding to the next stage. This process ensures that the project remains viable and aligned with business objectives before committing further resources.

Avoid, reduce, and transfer are threat responses. Exploit and enhance are opportunity responses.

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

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

During CP, the PM should ensure all products are accepted. If a defect exists, it should be documented in the Lessons Report and an updated product status should be provided. The board decides acceptance.

The Project Plan contains the project-level tolerances, including cost and time.

The project is within the stage tolerance of 10% (currently at 5% over time), and the Project Manager expects the trend to continue but has not yet exceeded the tolerance. According to PRINCE2, the Project Manager should continue managing the work within the agreed tolerance and report the deviation in the next Highlight Report, as this is the standard mechanism for communicating progress and forecast deviations that are still within tolerance. Raising an Exception Report is only required when a deviation is forecast to exceed the stage tolerance, which is not the case here.

Expected benefits and major risks are key components of the Business Case. Options B and D are correct.

The Senior User specifies user needs, ensures the solution meets them, and is responsible for realizing benefits. The Senior User does not own the Business Case (Executive does) and does not manage risks day-to-day (Project Manager does).

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a foundation for project execution.

The Senior User represents the users and is responsible for ensuring the project delivers the required benefits; however, the Executive (Senior Responsible Owner) owns the Business Case. In PRINCE2, the Executive is ultimately accountable for the Business Case, but the Senior User provides input on benefits. The question asks who maintains it, and the correct answer is the Executive.

Project Assurance is a PRINCE2 role responsible for verifying that the project remains viable and compliant with its business case, plans, and standards, independent of the Project Manager. A quality review is a specific technique used to assess whether a product meets its defined quality criteria and to identify defects. The key difference is that Project Assurance provides ongoing oversight of the project's adherence to plans and governance, while a quality review focuses on the quality of a specific product at a point in time.

The Senior Responsible Owner (SRO/Executive) is accountable for the project's success and owns the Business Case.

Directing a Project (DP) is the process where the Project Board makes key decisions, including authorizing initiation. Starting Up a Project (SU) prepares the conditions but does not authorize initiation.

CS includes authorizing Work Packages, reviewing progress, managing issues, reporting highlights, and taking corrective action. Planning the next stage is done in SB. Producing Checkpoint Reports is done by Team Manager.

Highlight Reports and End Stage Reports are produced by the Project Manager for the Project Board. Checkpoint Reports are for Team Managers; the End Project Report is produced at the end.

The End Project Report confirms acceptance of products and provides a summary of project performance.

The Project Manager produces Highlight Reports to inform the Project Board of progress during a stage.

The Benefits Review Plan is created during the Initiating a Project process.

In a strong matrix structure, team members report to both functional and project managers, which can create loyalty conflicts. PRINCE2's 'defined roles and responsibilities' practice, documented in the Project Initiation Documentation (PID), clarifies each team member's authority, accountability, and reporting lines. This formal definition reduces ambiguity and reinforces commitment to the project by making project responsibilities explicit.

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 the continued viability of the Business Case.

The seven themes are Business Case, Organization, Quality, Plans, Risk, Change, and Progress.

PRINCE2 separates the management and assurance functions to maintain objectivity.

PRINCE2 lists avoid, reduce, fallback, transfer, accept, and share as threat responses. Exploit is an opportunity response.

The Project Brief contains the outline Business Case, project approach, and other information needed for the Project Board to decide whether to proceed to initiation.

According to PRINCE2's management by exception, if a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot unilaterally change the plan.

The Team Manager provides Checkpoint Reports at regular intervals. The Project Manager uses these to compile Highlight Reports for the Project Board.

Option A is correct because the Senior User is responsible for specifying the user requirements and ensuring that the project delivers the expected benefits. This role represents the interests of the users and is accountable for defining the desired outcomes and confirming that the project's products meet those needs.

If the change is outside the Change Authority's delegated scope (e.g., affects items they cannot approve), the Project Manager must escalate to the Project Board.

Option A is correct because the Project Board is responsible for approving Stage Plans and any updates to them during the Directing a Project process. This ensures that the project remains aligned with the business case and that management stage boundaries are properly controlled.

The Team Manager should first record the quality problem as an issue and escalate it to the Project Manager, who will decide how to handle it. The Team Manager cannot unilaterally change the product or stop work without authorization.

Option C is correct. PRINCE2 defines a project as a temporary organization that creates a unique product. Business as usual is ongoing and repetitive, not temporary.

The PRINCE2 risk management procedure follows: identify, assess, plan responses, implement, and monitor.

The Project Manager should review the completed work package to ensure it meets acceptance criteria before approving it.

The Quality Register records all planned quality activities and their results, serving as a log of quality events.

PRINCE2 recommends that the Project Board meets at stage boundaries and when an exception is raised (exception-driven).

Controlling a Stage (CS) is where the PM authorizes Work Packages, monitors progress, and takes corrective action.

Closing a Project ensures controlled closure, including handover of products, confirmation of benefits review arrangements, and release of resources.

Starting up a Project ensures that there is a viable and justified project idea before initiating the project.

The risk owner is accountable for the risk and ensures it is managed. The risk actionee is assigned to carry out specific responses. One risk owner may have several actionees.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and must ensure it remains viable throughout the project.

The Executive is the single person accountable for the Business Case and must ensure it remains viable throughout the project. PRINCE2 explicitly assigns ownership of the Business Case to the Executive, who approves any changes to it and decides whether the project should continue based on its ongoing justification.

The Project Manager manages day-to-day operations and prepares Highlight Reports. Creating the PID is done in Initiating a Project, and authorizing Work Packages is the Team Manager's role.

Option A is correct because PRINCE2 requires the Business Case to be a living document that reflects realistic projections, including uncertainties. By showing a range of benefits ($300,000–$500,000) and a corresponding risk assessment, the project manager provides a balanced view that supports informed decision-making, aligning with the 'continued business justification' principle.

An RFC proposes a modification to an agreed baseline, while an Off-spec is a product not meeting its specification (a deviation).

The Project Manager maintains the Business Case on a day-to-day basis, but the Executive owns it and is accountable for the business justification.

The risk actionee is assigned to implement the response actions, while the risk owner is accountable for managing the risk.

The risk owner is responsible for managing the risk overall, while the risk actionee is assigned to carry out specific actions to respond to the risk.

The PID includes the Business Case, Project Plan, Project Description, roles and responsibilities, etc. The Risk Register is a separate document, and the Checkpoint Report is a management product.

These are the four levels of management hierarchy in PRINCE2.

The Closing a Project process produces the End Project Report, which assesses how the project performed against its plan and justifies closure.

Starting Up a Project produces the Project Brief, Initiation Stage Plan, and Daily Log. PID and Benefits Management Approach are from Initiating a Project. End Stage Report is from Managing a Stage Boundary.

The Risk Register records identified risks, their analysis, planned responses, and status. It is a central repository for risk information.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It defines the 'what, why, who, when, and how' of the project.

Closing a Project ensures a controlled closure, handover of products, evaluation of the project, and recommendations for future projects.

Option A is correct because the Executive role in PRINCE2 is the chair of the Project Board. The Executive is the ultimate decision-maker for the project, responsible for ensuring the project remains viable and aligned with business objectives. Chairing the Project Board means the Executive leads board meetings, sets the agenda, and ensures decisions are made to authorize key stages and changes.

The risk owner is responsible for managing the risk. The risk actionee performs actions.

Option B is correct because one of the key purposes of the Directing a Project process is to confirm project closure, ensuring that all objectives have been met and that the project is formally closed. This includes authorizing the final stage and confirming that the project has delivered its products as defined in the Project Initiation Documentation.

If a product cannot meet its quality criteria, the Team Manager must escalate the issue to the Project Manager as an issue, following the issue and change control procedure.

The purpose of Managing a Stage Boundary is to provide the Project Board with information to approve the current stage's completion and authorize the next stage.

The End Project Report and the Lessons Report are both produced in CP. The Project Brief is from SU, the PID from IP, and the Stage Plan from SB.

The Executive (Senior Responsible Owner) is responsible for maintaining the Business Case throughout the project because they own the project's justification and ensure it remains viable. PRINCE2 explicitly assigns this accountability to the Executive, who must approve any changes to the Business Case and confirm its continued alignment with corporate strategy. The Project Manager develops and updates the Business Case, but the Executive holds ultimate responsibility for its content and approval.

Directing a Project is the process where the Project Board makes key decisions, including authorizing initiation, stage plans, exception plans, and project closure.

Option D is correct because the PRINCE2 principle of continued business justification requires that the Business Case be updated to reflect current risks and uncertainties. In this scenario, the market volatility and competitor risk could reduce benefits by 30%, dropping the expected benefits to £910,000, which is below the £1.2 million cost, making the project unviable. Presenting this risk-adjusted Business Case to the board allows them to make an informed decision on whether to proceed, rather than proceeding with an overly optimistic view.

The Quality Register records all quality management activities, including planned and actual dates, and results.