PRINCE2 Foundation (PRINCE2F) — Questions 676–750

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

A Highlight Report is periodic and reports progress within tolerances; an Exception Report is triggered when a tolerance is forecast to be exceeded.

Starting Up a Project is a pre-project process to ensure that there is a viable and worthwhile project before committing to significant resources. It creates the Project Brief and Initiation Stage Plan.

An RFC proposes a change to agreed baselines; an Off-spec is a product that does not meet its specification.

The quality practice includes Quality Planning, Quality Control, and Quality Assurance. Configuration Management is part of the Change practice.

The Senior Responsible Owner (SRO) is the single person accountable for the project's success and the realization of benefits.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides the foundation for project governance and control.

The PRINCE2 Project Board is the decision-making body responsible for overall project governance. It comprises three roles: the Executive (Senior Responsible Owner), the Senior User, and the Senior Supplier. The Senior User represents the interests of those who will use the project's outputs and is essential for defining requirements and benefits.

In PRINCE2, an Exception Report is triggered when a forecast indicates that a stage will exceed its agreed tolerance (e.g., cost or time). Option C is correct because exceeding stage cost tolerance is a formal deviation that requires escalation to the Project Board via an Exception Report, as the Project Manager cannot authorize changes beyond tolerance.

The PID and Business Case are refined and approved during Initiating a Project. The Project Brief is from Starting Up a Project, and the Risk Register is created during this process but not listed as a key output; it's part of the PID. However, the question asks for outputs, and both PID and Business Case are key outputs.

A Request for Change is a proposed modification to a baseline, while an Off-specification is a failure to meet a requirement. Option B is correct.

Option B is correct because PRINCE2 requires that each risk has a named risk owner who is accountable for managing that risk and implementing the planned responses. This ensures clear accountability and proactive risk management throughout the project lifecycle.

The Executive (also known as Senior Responsible Owner) is accountable for the Business Case and securing funding.

The Project Product Description defines the overall product and its expectations, including user needs, but the User Requirements document captures detailed user needs. However, in PRINCE2, the Project Product Description is the key document for defining what the user expects.

CS includes authorizing Work Packages, reviewing progress, and reporting highlights. Producing the End Stage Report is done in SB.

PRINCE2 defines six aspects of project performance that must be managed: Costs, Time, Quality, Scope, Risk, and Benefits. Risk (Option B) and Time (Option C) are explicitly included in this set. These aspects are used to measure and control project success throughout the lifecycle.

Project Assurance is an independent oversight role ensuring the project stays on track, while a quality review is a specific technique to assess the quality of products.

The Team Manager should notify the Project Manager that the product is ready for acceptance. The PM arranges quality review and acceptance.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and must ensure it remains viable. The Project Manager develops and maintains it on behalf of the SRO.

Project Support provides administrative and support services to the project team. It is an optional role.

Project Assurance independently monitors compliance with standards and assesses risks and issues, reporting to the Project Board. It does not manage day-to-day or provide admin support.

Checkpoint Reports are produced by the Team Manager (or team members) and sent to the Project Manager to report progress on a Work Package.

If a product does not meet quality criteria, the Project Manager should raise an Issue (specifically an Off-specification) and decide on corrective action.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and ensuring it remains viable. Option A is correct.

Option C is correct because the End Stage Report is the formal mechanism to report stage performance, including cost variances, to the Project Board. The project manager must include the actual cost ($520,000) against the planned budget ($500,000) and provide an updated forecast, allowing the board to make an informed decision. This aligns with PRINCE2's management by exception principle, where variances within tolerance are reported in the End Stage Report, not via an exception report.

The project management team includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and Project Assurance. Project Support is also a role but not part of the management team? Actually Project Support is a role. The three correct ones are Executive, Senior User, and Project Manager.

Option D is correct because the Project Board is responsible for providing resources and authorizing funds for the project. This is a key duty of the board, as they own the business case and must ensure the project remains viable by approving the necessary budget and resource allocation.

The Team Manager should escalate to the Project Manager via the Managing Product Delivery process. The Project Manager will decide to revise the Work Package or raise an exception.

PRINCE2 defines quality as 'fit for purpose' — meeting agreed requirements and fulfilling its purpose.

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

The Risk Register records identified risks, their analysis, and planned responses.

In PRINCE2, when a stage is forecast to exceed its cost tolerance, the Project Manager must 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 agreed tolerance; the Project Board must decide whether to approve a revised plan or take other corrective action. Option D correctly follows the PRINCE2 exception management process.

The Project Board meets on an exception-driven basis, i.e., when decisions are needed due to deviations or at stage boundaries, not on a fixed schedule.

Option A is correct. The Directing a Project process covers Project Board decisions, including authorization to start a stage. Controlling a Stage is a Project Manager process.

A Work Package is the document that authorizes the Team Manager to create one or more products. It contains details of the work to be done and constraints.

The SRO owns the Business Case and is accountable for the project's success and benefits realization. They also chair the Project Board.

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.

This process provides the Project Board with information to decide whether to continue with the next stage, based on review of the current stage's performance and updated plans.

When a stage 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 Organising practice defines the roles and responsibilities within the project management team.

The Project Brief is the key output that provides a definition of the project and justifies its viability.

The Project Board approves the Stage Plan for the next stage, allowing the project to proceed. This is part of the exception-driven decision-making.

Directing a Project is the process by which the Project Board authorizes initiation, authorizes the project, authorizes stage plans, and gives ad hoc direction.

The Starting Up a Project process produces the Project Brief, which provides a high-level overview of the project to support the decision to proceed to initiation.

Options B and D are correct. A Product Description includes quality criteria (B) and acceptance methods (D). The risk budget and stage boundaries are not part of a Product Description.

Managing a Stage Boundary (SB) is the process where the PM reports on the current stage (End Stage Report) and plans the next stage (next Stage Plan).

Issue types are: Request for Change, Off-specification, and Problem/Concern. Risk is not an issue; it is a separate practice.

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

The Project Board sets project-level tolerances (e.g., time, cost, quality) in the PID, providing boundaries within which the Project Manager operates.

Option B is correct because PRINCE2 mandates that Project Assurance is independent of the Project Manager to ensure objective oversight. Option C is correct because Project Assurance's primary role is to provide an independent view of the project's health, checking compliance with standards and business justification.

In PRINCE2, tolerances are the permissible deviations from a plan without needing to escalate to the next management level. The six standard tolerances are Time, Cost, Quality, Scope, Risk, and Benefit. Time (B) and Cost (D) are explicitly defined as tolerances for managing stage and project plans.

The Project Brief is the key output of the Starting Up a Project process, providing the initial information to decide whether to proceed to initiation.

Options A and B are correct. The six tolerances in PRINCE2 are time, cost, quality, scope, risk, and benefits. Options C, D, and E are not standard PRINCE2 tolerances; they are management approaches or budgets.

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

Authorizing Work Packages is an activity in the Controlling a Stage process, where the PM assigns work to Team Managers.

The purpose is to provide the Project Board with sufficient information to review the current stage, approve the next stage plan, and confirm continued business justification.

Option A is correct because the Project Manager is responsible for producing the Project Initiation Documentation (PID) in PRINCE2. The PID is a key deliverable that consolidates the project's scope, business justification, plans, and controls, and the Project Manager compiles it based on input from the Project Board and other stakeholders. This responsibility is explicitly defined in the PRINCE2 Project Manager role description.

In PRINCE2, the risk register is the central repository for recording all identified risks, and the risk management approach defines how risks will be managed throughout the project. During the Initiating a Project process, the project manager must formally document the supplier delay risk and plan appropriate responses (e.g., mitigation, contingency) within the risk management approach. This ensures the risk is actively managed rather than ignored or deferred, aligning with PRINCE2's principle of continued business justification.

The three issue types are Request for Change, Off-specification, and Problem/Concern.

An Exception Plan is produced when a stage is forecast to exceed its tolerances, as an alternative to the current Stage Plan, for approval by the Project Board.

The Team Manager is responsible for delivering the Work Package within agreed tolerances and reporting progress via Checkpoint Reports.

The PID and Benefits Management Approach are created in IP. The Project Brief is from SU, and the End Project Report is from CP.

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

Highlight Reports are produced by the Project Manager during the Controlling a Stage process and sent to the Project Board to provide a summary of progress.

Option B is correct because Project Assurance and quality reviews serve distinct purposes in PRINCE2. Project Assurance is an independent oversight function that ensures the project remains viable, compliant, and on track against the business case and plans. A quality review, on the other hand, is a structured technique used to assess whether a specific product meets its defined quality criteria and is fit for purpose.

Exploit and Enhance are opportunity responses. Avoid and Transfer are threat responses. Accept can be used for both.

SB produces the End Stage Report and the next Stage Plan (or Exception Plan).

SU is a pre-project process that ensures the prerequisites for initiating a project are in place, including the appointment of the Executive and Project Manager and the creation of the Project Brief.