PRINCE2 Foundation (PRINCE2F) — Questions 1126–1200

PRINCE2 separates assurance from management to ensure independent oversight. Assurance provides objective checking that the project is being managed correctly and that the project's products will meet business needs. Management is responsible for delivery.

Project Assurance is independent of the Project Manager and can be performed by individuals from the Project Board or external reviewers.

The Executive (Senior Responsible Owner) is accountable for the Business Case and its maintenance throughout the project.

Quality checks are performed by the Team Manager and the Project Manager ensures the process is followed, but the ultimate responsibility for quality lies with the Project Board, specifically the Senior User.

Project Assurance is independent of the Project Manager and reports to the Project Board, ensuring that the project is being managed correctly.

A Checkpoint Report is produced by the Team Manager to provide the Project Manager with progress details on a Work Package at regular intervals.

Option A is correct because PRINCE2 provides a structured framework with defined roles, responsibilities, and management products (e.g., Highlight Reports, Issue Reports) that standardize communication channels and enable better control through stage-gate approvals and exception management. This reduces ambiguity and ensures stakeholders receive timely, relevant information.

The Change Authority is an optional role that can be set up to make decisions on change requests within agreed limits, thereby relieving the Project Board from reviewing every change.

Option B is correct because the Initiating a Project process is where the Project Initiation Documentation (PID) is produced. The PID consolidates key planning information, including the detailed business case, project plan, and risk register, to form a solid foundation for the project. This process ensures that all stakeholders have a shared understanding of the project's scope, objectives, and approach before proceeding.

The Project Board consists of the Executive, Senior User, and Senior Supplier. The Project Manager is not a permanent member.

The risk owner is accountable for managing the risk, while the risk actionee carries out specific actions.

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

Option B is correct because PRINCE2 requires that any change to the project's scope, including the addition or removal of a product, must be formally assessed against the Business Case. The project manager should update the Business Case with the costs and benefits of including the disputed product and then present it to the Project Board, which holds the authority to approve or reject changes to the project's products. This aligns with the 'continued business justification' principle and the 'change control' practice.

CS focuses on day-to-day management, including authorising work packages and taking corrective action. Producing the Project Initiation Documentation is done in IP, and producing the End Project Report is done in CP.

The Product Status Account provides information about the status of products, typically including their version, state (e.g., in development, approved), and configuration records. It is used to report on the state of the project's products.

Managing a Stage Boundary includes capturing lessons learned as part of the End Stage Report.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process because it consolidates all essential information needed to justify and manage the project, including the Business Case, Project Plan, and controls. It serves as the foundation for decision-making by the Project Board and is formally approved at the end of the initiation stage.

These are five of the seven PRINCE2 themes.

In PRINCE2, the Senior Responsible Owner (SRO) is the same role as the Project Sponsor, but PRINCE2 uses the term 'Executive' for this role. The Executive is the single point of accountability for the project's success, representing the business interests and owning the business case. Option B correctly identifies this equivalence, which is a fundamental concept in PRINCE2's organizational structure.

The End Stage Report is produced to give the Project Board a summary of progress to date, plus the next Stage Plan for approval.

In PRINCE2, the Controlling a Stage process is responsible for authorizing Work Packages. This process manages the day-to-day activities within a stage, including assigning work to teams and ensuring it is completed according to the agreed tolerances. The Project Manager uses this process to issue Work Packages to the team manager or team members, formally delegating the work defined in the Stage Plan.

The PRINCE2 framework consists of 7 principles, 7 practices (themes), and 7 processes. Tailoring is also an element but is not listed here.

The Organising practice defines the project management team structure and the roles and responsibilities.

Option D is correct. SB provides the PM with information to report on the current stage and plan the next, for the Board to decide on continuation.

The End Stage Report provides the Project Board with information to decide whether to continue to the next stage.

The Project Manager maintains the Business Case on behalf of the Executive, but the Executive (SRO) owns it. However, the question asks who maintains it, which is the Project Manager.

The Executive chairs the Project Board in PRINCE2. This is because the Executive is the ultimate decision-maker, accountable for the project's business justification and overall success. The Project Board is chaired by the Executive, not the Project Manager, Senior Supplier, or Senior User, as the Executive represents the business interests and has the authority to approve key decisions.

The Business Case is the PRINCE2 document that justifies the project on economic grounds, and it must contain clearly defined benefits to enable ongoing viability assessment. If benefits are not clearly defined, the Business Case itself is incomplete and must be updated to ensure the project remains justified and aligned with organizational objectives.

The Executive is the single individual on the Project Board who has ultimate accountability for the project's business justification. They own the Business Case and must ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Project Manager manages the day-to-day work but does not own the Business Case; the Executive alone is responsible for its ongoing viability.

Separation ensures independence of assurance, preventing the Project Manager from making biased assessments of their own work.

Checkpoint Reports are produced by the Team Manager for the Project Manager during Managing Product Delivery. Highlight Reports are produced by the Project Manager for the Project Board during Controlling a Stage. They serve different audiences and have different frequencies.

The Managing Product Delivery process is designed to control the interface between the Project Manager and the Team Manager. Its purpose is to accept, execute, and deliver work packages, ensuring that the work is done according to the agreed criteria and that the completed products are handed back to the Project Manager. This process focuses on the team's work and the delivery of products, not on the Project Manager's day-to-day activities.

The Daily Log is first created as an output of the Starting Up a Project process. This process establishes the project's initial records, including the Daily Log, to capture informal issues, observations, and lessons from the very beginning of the project lifecycle.

A Request for Change proposes a modification to agreed products; an Off-specification is a product that does not meet its specification.

Enhance is the response for opportunities that seeks to increase the probability or impact of the opportunity.

An RFC is a proposal for a change to a baselined product; an Off-spec is something that should be provided but is not, or is provided incorrectly.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report — this is PRINCE2's management by exception principle.

PRINCE2 defines three issue types: Request for Change, Off-specification, and Problem/Concern. Options A and B are correct; the others are not types of issue.

PRINCE2 specifies that a Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. Expected benefits, major risks, and costs are explicitly listed.

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

The 'continued business justification' principle requires that the business justification for the project is reviewed and updated throughout the project. Options A and B are other principles but do not directly address viability. Option D is not a PRINCE2 principle.

An Exception Plan is produced in the Managing a Stage Boundary (SB) process when the Project Board directs the Project Manager to create one in response to an Exception Report.

The Project Board is responsible for ensuring that project assurance is independent of the Project Manager. This is because the Project Board provides overall governance and oversight, and project assurance is a key function that must be objective and separate from the day-to-day management activities of the Project Manager. The PRINCE2 principle of 'defined roles and responsibilities' explicitly assigns this accountability to the Project Board to maintain the integrity of the assurance function.

SU is a pre-project process to determine if the project is viable before committing to detailed planning. IP formally establishes the project foundation and produces the PID. Key difference: SU decides whether to proceed; IP creates the detailed plans and strategies.

When a stage tolerance is forecast to be exceeded, the PM produces an Exception Report (part of Controlling a Stage) and then the Board decides, but the escalation itself occurs within CS. However, the process for creating an Exception Plan is SB. The escalation step is part of CS.

The Initiating a Project process produces the Project Initiation Documentation (PID), which includes the Project Plan and Business Case. The Highlight Report is from Controlling a Stage, and the Work Package is from Managing Product Delivery.

Option B is correct because a Request for Change (RFC) is a formal proposal to modify a baseline product or process, while an Off-specification (Off-spec) is a product that has been identified as not meeting its agreed specification. In PRINCE2, both are types of issues, but an RFC seeks a change to the specification itself, whereas an Off-spec indicates a deviation from the existing specification that must be resolved.

Starting Up a Project is a pre-project process to decide if the project is viable; Initiating a Project formally establishes the project foundation. SU happens before initiation.

The End Project Report is the key document in Closing a Project that confirms the project's deliverables and performance against the original PID. It also includes lessons and a summary of benefits reviews.

The Quality practice in PRINCE2 provides the guidance for defining the project's outputs and acceptance criteria. It ensures that the project product description includes the quality criteria, quality methods, and acceptance criteria that the product must meet to be accepted by the customer. This practice directly addresses how to specify and verify the project's deliverables.

Option A is correct because the risk register is a PRINCE2 management product that formally records all identified risks, their status, and related information throughout the project. It is created during the Initiating a Project process and maintained as risks are identified, assessed, and responded to.

The PID and several management approaches are produced in IP. The Project Brief is from SU, and the End Stage Report is from SB.

During the Managing a Stage Boundary process, the Project Manager must update the Project Plan with actuals and forecasts to reflect the current stage's performance and provide a basis for planning the next stage. This ensures the Project Board has accurate information to authorize the next stage or take corrective action.

The Directing a Project process includes the 'Authorize Initiation' activity, where the Project Board gives approval to start initiation.

PRINCE2 does not cover HR management; it focuses on project management processes.

The SB process provides the Project Board with information needed to review the current stage, approve the next stage Plan, and assess the continued viability of the project.

The purpose is to enable the Project Board to review the current stage's performance, approve the next stage plan, and ensure the Business Case remains viable.

The Senior Responsible Owner (Executive) is the ultimate owner of the Business Case and is responsible for its development and maintenance throughout the project. PRINCE2 mandates that the Executive ensures the Business Case remains viable, justified, and aligned with corporate strategy at every stage, approving any changes to it.

The Executive is the single individual who owns the business case and is ultimately accountable for the project's justification. Throughout the project, the Executive must ensure that the business case remains viable, approving any changes that affect its justification. This is a core responsibility defined in the PRINCE2 Business Case theme.

Option A is correct because PRINCE2 explicitly allows tailoring to simplify processes and documentation to suit the project's needs, ensuring the method remains scalable and practical. This is a core concept of PRINCE2's flexibility, not a deviation from the framework.

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

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 board's responsibilities from project initiation through to closure, including authorizing the initiation, stage plans, and project closure, as well as providing ad hoc direction. This process does not involve detailed planning or day-to-day management, which are handled by other processes.

Project Assurance is independent of the Project Manager and provides objective oversight to the Project Board.

The Project Plan and Business Case are components of the PID. Options B and D are correct.

Option B is correct because the Project Board is responsible for authorizing the initiation of the project during the Directing a Project process. This authorization formally allows the Project Manager to proceed with the Initiation Stage, committing resources and funding. It is a key decision point that ensures the project aligns with corporate or programme strategy before detailed planning begins.

Transfer involves shifting the financial impact of a risk to a third party, e.g., through insurance or outsourcing.

The principles are the guiding obligations; the practices provide the management activities; the processes describe the flow of activities. They are integrated and complementary.

In the Initiating a Project process, the Risk Management Approach is a strategy document that defines how risk management will be performed throughout the project. It must include the risk categories (e.g., technical, external, organizational) used to classify risks, as these provide a consistent framework for identifying and assessing risks. The risk register, risk appetite, and risk budget are not part of the approach itself; they are outputs of later processes or separate management products.

IP produces the PID, which includes the Project Plan, Business Case, and various management approaches. The Project Brief and End Stage Report are not outputs of IP.

Managing Product Delivery is the process where Team Managers accept, execute, and deliver Work Packages, reporting progress via Checkpoint Reports.