PRINCE2 Foundation (PRINCE2F) — Questions 1426–1500

SU is a pre-project process to determine feasibility before committing to initiation, while IP establishes the project management foundation and produces the PID.

The Checkpoint Report is a PRINCE2 management product used by the Team Manager to report progress of a Work Package to the Project Manager. Its purpose is to provide regular, detailed progress updates on the work being performed by the team, ensuring the Project Manager can monitor delivery against the Work Package plan. This is distinct from higher-level reports like the End Stage Report or Highlight Report.

The Business Case includes expected benefits, costs, and investment appraisal, among others. Options and risks are also components.

Management by Exception is the principle of delegating authority within tolerances and escalating deviations.

The End Stage Report is produced to provide the Project Board with a summary of progress and to request approval to proceed.

PRINCE2 defines distinct roles for management and delivery. The Project Board and Project Manager are key roles.

In PRINCE2, the Senior Responsible Owner (SRO) is the single individual accountable for the project's success, ensuring it delivers the required outcomes and realizes the expected benefits. This role is defined in the PRINCE2 framework as the ultimate decision-maker and owner of the business case, distinct from the Project Board's collective responsibility or the Project Manager's day-to-day management.

The Project Plan is updated to reflect the actual progress of the completed stage and to provide a realistic baseline for the remaining stages. This helps the Project Board make an informed decision about whether to proceed with the next stage.

Option A is correct because in PRINCE2, the Senior Responsible Owner (SRO) is the single person accountable for the Business Case and ensuring the project delivers the expected benefits. The term 'Project Sponsor' is not a defined role in PRINCE2; it is a common industry term that may be used interchangeably with the SRO or other roles, but PRINCE2's official role structure uses the SRO as the key business representative on the Project Board.

Project Assurance is performed by individuals independent of the Project Manager, typically from the Project Board roles.

The 'Reduce' response involves proactive actions to lower the probability and/or impact of a threat.

A Request for Change proposes a modification to an agreed baseline; an Off-specification is something that should be there but is not, or is wrong.

The Directing a Project process includes the activity 'Give ad-hoc direction to the Project Manager'. The Board provides guidance as needed throughout the project.

The Team Manager manages the Work Package and reports issues/risks to the Project Manager via Checkpoint Reports and the Issue Register.

If a Team Manager forecasts that work will exceed Work Package tolerances, they must escalate to the Project Manager via an Exception Report. The Project Manager then decides on corrective action or escalation to the Project Board.

Managing a Stage Boundary includes producing an End Stage Report, updating the Project Plan, and planning the next stage. Authorizing Work Packages is part of Controlling a Stage, and handing over products is part of Closing a Project.

A Request for Change is a proposed change to a product that has been defined and possibly baselined. An Off-specification is something that is missing from a product or does not meet specifications. Both are types of issue, but the key difference is that a RFC is a change to the specification, while an Off-spec is a failure to meet it.

Checkpoint Reports are produced by the Team Manager in Managing Product Delivery and sent to the Project Manager for progress monitoring.

Option A is correct because the Project Manager is responsible for producing the Project Plan, which includes the detailed schedule, resource allocation, and cost estimates. This is a core PRINCE2 responsibility, as the Project Manager owns the planning process and ensures the plan aligns with the project's business case and stage tolerances.

The Project Board is responsible for providing direction and authorizing the next stage. The End Stage Report is presented to the Project Board for decision.

These management approaches are created during Initiating a Project as part of establishing solid foundations for the project.

Directing a Project is the process by which the Project Board authorises the initiation of a project, among other key decisions.

The Starting Up a Project process is designed to ensure that the prerequisites for initiating the project are in place before the project is formally authorized. It answers the question 'Do we have a viable and worthwhile project?' by creating the Project Brief (including an outline Business Case) and appointing key roles, but it does not produce the full Business Case or Project Plan, which are developed later in the Initiating a Project process.

Option C is correct because PRINCE2 provides a standardized framework with defined roles, responsibilities, and terminology, which ensures all stakeholders (including project board, team managers, and suppliers) share a common language. This reduces misunderstandings and aligns communication across the project lifecycle, directly supporting the principle of 'continued business justification' and 'manage by stages'.

The Project Plan is the high-level plan covering the entire project.

In PRINCE2, the Project Manager is responsible for preparing the Project Plan, as defined in the 'Plan' theme. This includes estimating, scheduling, and documenting the plan to achieve the project's objectives within agreed tolerances. The Project Manager owns the planning process and produces the plan for approval by the Project Board.

The Project Initiation Documentation (PID) is the key output of IP, consolidating all management approaches and plans.

The Project Manager is responsible for maintaining the Business Case on a day-to-day basis, while the Executive owns it and approves changes.

In MP, the Team Manager must escalate issues that affect the Work Package to the Project Manager. They cannot approve changes or bypass the PM.

The Business Case is a core component of the Project Initiation Documentation (PID) because it provides the justification for the project, detailing the costs, benefits, and risks. The Project Plan is also part of the PID as it defines the project's scope, schedule, and resource requirements, forming the baseline for execution and control.

Starting Up a Project is a pre-project process that ensures the prerequisites for initiation exist, while Initiating a Project formally establishes the project's foundations and produces the PID.

Closing a Project ensures the project is closed in a controlled manner, products are handed over, lessons are recorded, and the project is formally closed.

The purpose is to enable the Project Board to review the current stage's performance and approve the next stage plan.

The Project Manager maintains the Business Case under the direction of the Executive. The Executive owns it, but the PM does the updates.

The Project Manager is responsible for maintaining the risk register as part of the 'Manage Risk' practice. This includes ensuring that risks are recorded, updated, and reviewed throughout the project, and that the register reflects the current risk status. The Project Manager does not own individual risks but manages the register as a key project document.

This process aims to provide the Project Board with information to review the current stage and approve the next stage plan.

Option B is correct because PRINCE2 defines a project as a temporary organization created to deliver one or more business products according to an agreed Business Case. This definition emphasizes the temporary nature of a project, its focus on outputs (products), and the necessity of a validated Business Case to justify the investment. It distinguishes projects from ongoing operations by highlighting the unique, time-limited structure and the governance provided by the Business Case.

The 'Plan' step is where risk responses are developed and selected. The 'Assess' step evaluates probability and impact, but the decision on how to respond is part of planning.

The Project Manager is delegated by the Project Board to manage the project on a day-to-day basis within agreed tolerances.

In PRINCE2, quality is defined as 'fit for purpose,' meaning the product meets the stated requirements and is suitable for its intended use. This definition emphasizes that quality is about satisfying the agreed-upon specifications and user needs, not about achieving an abstract standard like zero defects or ISO compliance.

Starting Up a Project (SU) is a pre-project process. Its purposes include ensuring that the project has a viable Business Case and that the necessary authorities are in place to proceed to initiation. Option C (authorize the project) is done in Directing a Project; Option D (produce the PID) is done in Initiating a Project; Option E (update the Business Case) is done throughout the project.

Project Assurance provides independent oversight of the entire project on behalf of the Project Board, whereas a quality review is a specific technique to assess the quality of a product.

A Request for Change is a proposal for a modification, while an Off-specification is a product that does not meet its specification.

The Highlight Report is a periodic report from the PM to the Project Board on stage progress.

MP is where the Team Manager executes the Work Package and produces Checkpoint Reports. The PM authorises the Work Package at the start.

The seven principles include Manage by Stages and Continued Business Justification. 'Use of Agile' is not a principle.

The Project Plan is the correct artifact to update because it defines the overall project timeline, milestones, and resource estimates. When the duration is underestimated during Initiation, the Project Plan must be revised to reflect a realistic schedule before it is approved by the project board. Updating the Project Plan ensures the baseline for the entire project is accurate, which is critical for subsequent stage planning and control.

A Product Description includes purpose, composition, and quality criteria, among others.

During Managing a Stage Boundary, the PM prepares the End Stage Report and next Stage Plan. The issue should be documented with a recommendation for the Project Board to decide.

The Initiating a Project process produces the Project Initiation Documentation (PID) as its key output. The PID consolidates all essential information required to manage the project, including the Business Case, Project Plan, and controls, and serves as the foundation for the next stage. It is the definitive document that authorizes the project to proceed.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case and its continued viability because PRINCE2 defines this role as the single point of accountability for the project's justification. The Executive owns the Business Case throughout the project lifecycle, ensuring it remains aligned with corporate strategy and approving any changes that affect its viability. This accountability cannot be delegated to the Project Manager, who is responsible for day-to-day management but not for the business justification.

The Initiating a Project process is responsible for establishing a solid foundation for the project, and its key output is the Project Initiation Documentation (PID). The PID consolidates all the essential information needed to justify, define, and plan the project, including the Business Case, Project Plan, and Risk Register. It serves as the definitive reference document for the project board to authorize the project.

The Project Board authorises the stage by approving the Stage Plan. Work cannot start without this authorised plan.

The Project Initiation Documentation (PID) is the main output of Initiating a Project.

The Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. Expected benefits and major risks are correct.

The Product Description includes quality criteria and is used to verify that the product meets requirements.

The Project Manager must first assess the impact of the delay on the Stage Plan and decide on corrective action within the agreed stage tolerances. This aligns with the PRINCE2 principle of management by exception, where the Project Manager handles deviations within tolerances before escalating. Only if the delay exceeds stage tolerances should an Exception Report be raised to the Project Board.

The risk owner is responsible for managing the risk and implementing responses. The risk actionee carries out specific actions. The owner may delegate tasks but retains overall accountability.

Project Assurance is a PRINCE2 role responsible for providing an independent, objective check to the Project Board that the project remains viable, compliant, and on track. It is not a day-to-day management function but a governance safeguard, ensuring that the project adheres to its business case, quality standards, and tolerances without being influenced by the Project Manager or delivery team.

CS includes authorising Work Packages, reviewing progress, reporting highlights, and managing issues and risks.

Closing a Project (CP) is the process that ensures controlled closure, including product handover and formal acceptance.

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. The PM cannot increase the budget or continue without escalation.

Option B is correct because a Request for Change (RFC) is a proposal for a future modification to the project's baselined products, while an Off-specification (Off-spec) is a problem that has already occurred, indicating that a product does not meet its specification. In PRINCE2, the key distinction is timing: RFCs are proactive and seek approval for a planned change, whereas Off-specs are reactive and document a deviation that has already happened.

When a Work Package tolerance is forecast to be exceeded, the Team Manager must escalate to the Project Manager via an Exception Report. The Project Manager can then negotiate corrective actions.

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

The Risk practice covers the systematic management of threats and opportunities.