PRINCE2 Foundation (PRINCE2F) — Questions 826–900

The Directing a Project process is owned by the Project Board and covers the board's ongoing oversight of the project between decision points. It explicitly includes giving ad-hoc direction and advice to the Project Manager whenever the board's authority or guidance is needed outside the formal stage boundaries. The other processes are owned by the Project Manager, not the board.

In PRINCE2, the Team Manager works within the Work Package tolerances agreed with the Project Manager. If the Team Manager forecasts that the work will breach those tolerances, the correct escalation path is to raise an Issue Report to the Project Manager, who then decides whether to handle it at project level or escalate further. The Team Manager does not go directly to the Project Board.

At a stage boundary, the Project Manager must provide the Project Board with an End Stage Report and an updated Business Case. The Board reviews these to decide whether to approve the next stage. Submitting the updated business case as part of this process is essential for the Board to assess the ongoing viability of the project and make an informed decision on continuation.

The PRINCE2 principle 'tailor to suit the project environment' requires that the method is adapted to the project's size, complexity, risk, and other factors. Combining processes and reducing stage boundaries for a small, low-risk project is a clear example of tailoring. This principle ensures that PRINCE2 is not applied in a one-size-fits-all manner but is scaled appropriately to add value without unnecessary overhead.

The Senior User (D) and the Executive (E) are two of the three mandatory roles on the PRINCE2 Project Board, alongside the Senior Supplier. The Executive is the Senior Responsible Owner (SRO) who owns the business case and has ultimate authority, while the Senior User represents the interests of those who will use the project's outputs. These roles are defined in the PRINCE2 'Organization' theme and are essential for project governance.

The 'Reduce' risk response in PRINCE2 (also called 'Mitigate' in other frameworks) involves taking action to lower the probability and/or impact of a risk. Since the risk owner is acting to reduce the probability of occurrence, this is the Reduce response. It is one of the responses in the PRINCE2 risk management procedure.

The principle of defined roles and responsibilities requires that a PRINCE2 project has a clear organisational structure that includes the three primary stakeholder interests: business, user, and supplier. This ensures that the project is accountable to these interests and that decisions are made with their input. The scenario describes exactly this need, making defined roles and responsibilities the correct principle.

In PRINCE2, the Change Management Approach is created during the Initiating a Project process to define how issues, changes, and configuration items will be managed throughout the project. It specifies the procedures for capturing, assessing, and deciding on issues and change requests, including the roles and responsibilities involved. This document ensures a consistent and controlled approach to handling changes, which is critical for maintaining project stability.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case, ensuring the project remains viable and aligned with organizational objectives. This includes approving the Business Case at initiation and any subsequent changes, as well as securing the necessary funding. The SRO also chairs the Project Board, providing overall leadership and direction, and is ultimately responsible for the project's success.

In PRINCE2, the Project Board is the project's ultimate decision-making authority, sitting above the Project Manager and owning overall accountability for the project. Approving the Project Plan (and the Project Initiation Documentation that contains it) is a formal board-level decision because the plan commits the organisation's resources and defines the baseline against which the project will be controlled. The Project Manager drafts the plan, but only the Project Board can authorise it.

The Quality Management Approach is the correct document because it defines the project's quality management strategy, including both quality assurance (systematic checks to ensure the project is using appropriate processes) and quality control (specific activities to verify that products meet their quality criteria). This is a key PRINCE2 management product that sets out how quality will be planned, performed, and governed throughout the project lifecycle.

PRINCE2 is a process-based project management methodology that focuses on business justification, defined roles, and product-based planning. It explicitly excludes detailed human resource management techniques such as team motivation, conflict resolution, and performance appraisals, which are typically covered by general management disciplines. Therefore, human resource management is not covered by PRINCE2.

In PRINCE2, the Checkpoint Report is produced by the Team Manager and sent to the Project Manager at a frequency defined in the Work Package. The Project Manager uses this progress information to update the Stage Plan with actual progress and to inform the Highlight Report, which is sent to the Project Board. This is the standard flow of progress information within the 'Controlling a Stage' process.

A Checkpoint Report is produced by the Team Manager at a frequency defined in the Work Package and sent to the Project Manager to report progress on that Work Package. Its primary purpose is to communicate the status of the Work Package — including progress, issues, and any forecast deviation — so the Project Manager can maintain the Stage Plan and take corrective action if needed.

The Project Manager is responsible for creating the Project Initiation Documentation (PID) because PRINCE2 assigns the Project Manager the role of assembling and producing the PID, which consolidates key planning documents like the Business Case, Project Plan, and Risk Register. The Project Board approves the PID, but does not create it, as the Project Manager acts as the single point of accountability for its preparation and quality.

The principle of manage by exception requires that the Project Board sets tolerances and delegates authority to the Project Manager to manage within those limits. When the Project Manager makes decisions that should be reserved for the board, they are acting outside the agreed tolerances, thus violating this principle. The other principles are not directly related to the delegation and control of authority in this scenario.

Project Assurance provides independent monitoring and oversight on behalf of the Project Board, ensuring the project remains aligned with its objectives, standards, and Business Case. It is not a management role but a check-and-balance function, giving the Board confidence that the Project Manager's reports are accurate and that PRINCE2 and organizational standards are being followed.

In PRINCE2, the Project Manager is delegated tolerances by the Project Board and manages the stage within those tolerances. Escalation to the Board is required when an issue (or a forecast issue) cannot be resolved within the delegated tolerances, because only the Board has authority to change tolerances, the Business Case, or the project's scope. This is the 'manage by exception' principle in action.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two defined types of issue are Request for Change (a proposal for a change to the product's specification or baseline) and Off-specification (something that should be provided but is not, or is provided incorrectly). These are formally documented and managed through the issue and change control procedure.

The outline Business Case should include a summary of the expected benefits and how they will be measured, as this provides an initial justification for the project. In this payroll system project, benefits such as cost savings and improved accuracy must be outlined, with measures to track them, to allow the Project Board to decide whether to proceed to the next stage.

B is correct because PRINCE2's continued business justification principle requires that the business case remain viable throughout the project. As project manager, you must escalate to the project board for an immediate review when the senior user raises concerns about benefits and market changes. If the business case is no longer viable, the project should be stopped to avoid further waste of resources, regardless of sunk costs.

In PRINCE2, the Project Board is ultimately accountable for the project's success, and it delegates the task of providing independent assurance to the Project Assurance role. This ensures that the project is being managed correctly, in line with the business case, and that all management stages are compliant with PRINCE2 principles. The Project Board (via Project Assurance) is the correct answer because it is the only role with the authority to provide objective, independent oversight, separate from the day-to-day management performed by the Project Manager.

Manage by exception means the project manager has authority to act as long as forecasted performance remains within agreed tolerances. When a tolerance is forecast to be exceeded, the project manager must escalate to the project board. In this scenario, the time tolerance is forecast to be breached, so immediate escalation is required to allow the board to decide on corrective action.

Reviewing the Business Case at the end of each stage is a direct application of the continued business justification principle. This principle requires that the project has a valid Business Case at the start and that it remains valid throughout, with reviews at stage boundaries to confirm alignment with business objectives. The other principles address product focus, stage control, and learning, not the ongoing justification of the project.

Project Assurance is a continuous, independent oversight activity that runs throughout the project lifecycle to ensure compliance with PRINCE2 principles and management by stages. A quality review, in contrast, is a scheduled, time-boxed event focused on assessing the quality of a specific product against its defined quality criteria. The key distinction is that Project Assurance is ongoing and embedded in governance, while a quality review is a discrete inspection meeting.

The Quality Review technique in PRINCE2 is a structured assessment to evaluate whether a product meets its defined quality criteria and is fit for purpose. Its primary purpose is to identify defects and ensure the product is complete and correct before it is approved for use. This aligns with option B, as the review focuses on verifying product quality rather than planning or risk management.

The Quality Management Approach is a PRINCE2 document that describes how quality will be managed on the project, including the quality methods, tools, techniques, standards, and responsibilities to be applied. It is created during the Initiating a Project process and defines the project's quality strategy.

In PRINCE2, the End Stage Report is the document produced by the Project Manager at the end of a stage during the Managing a Stage Boundary process. It summarizes the stage's performance against the Stage Plan, including actual versus planned costs, timescales, and products, and provides the basis for the Project Board to decide whether to approve the next stage.

When Project Board members disagree on a change, the Project Manager should facilitate a Board meeting to discuss the change's impact and reach a collective decision. The Board is the correct forum for resolving such conflicts, ensuring that both benefits and quality concerns are weighed. Escalating prematurely, acting unilaterally, or rejecting the change without discussion would bypass proper governance.

Under PRINCE2's manage by exception principle, the Project Manager is delegated tolerances by the Project Board. If a forecast indicates a breach of those tolerances, the Project Manager must escalate by producing an Exception Report so the Project Board can decide on corrective action. Taking unilateral action or delaying escalation would violate the principle and could lead to loss of control.

The Business Case theme is addressed by two specific components within the PID: the Business Case itself and the Benefits Management Approach. The Business Case provides the justification, while the Benefits Management Approach outlines how benefits will be measured and realized. Other PID components like the Project Plan, Risk Management Approach, and Quality Management Approach belong to different themes.

PRINCE2's principle of 'continued business justification' and the requirement for unified direction mandate that the project board make decisions by consensus, not by majority vote. The project board represents business, user, and supplier interests as a single cohesive unit; majority voting would risk dividing the board and undermining the principle of unified direction, as it could allow one interest to override others without full agreement.

The Project Manager is responsible for reviewing progress against the stage plan and taking corrective action when deviations occur, as defined in the Controlling a Stage process. This ensures the stage remains within tolerance and aligns with the project plan.

The Project Initiation Documentation (PID) is the key document created during the Initiating a Project process. It provides a comprehensive baseline that defines the project's scope, objectives, approach, and controls, against which the project's progress and performance are managed throughout its lifecycle.

This is an Off-specification because the product cannot meet a defined quality criterion specified in the product description. In PRINCE2, an off-specification is a type of issue that occurs when a product's actual or forecast quality does not match its agreed specification. The Team Manager has identified a deviation from the baseline, which is the defining characteristic of an off-specification.

In the Controlling a Stage process, after a Team Manager reports that a product is complete, the Project Manager must first review the product to confirm it meets the quality criteria defined in the Product Description. This is part of the 'Review Work Package' activity, ensuring that the product is fit for purpose before any further actions, such as reporting or planning, occur. Only after this quality check can the Project Manager proceed to other activities like updating logs or sending reports.

The PRINCE2 issue and change control procedure requires that issues be captured in the Issue Register and then assessed for their impact on the project. These steps ensure that decisions about changes are based on evidence and that the Project Board retains control over baselined products. Skipping assessment or ignoring issues would break the control loop and risk unmanaged change.

In PRINCE2, cost tolerance is defined at the stage and project levels within the Business Case and Project Plan. When a forecast indicates the stage or project will exceed its cost tolerance, this constitutes an exception, and the Project Manager must produce an Exception Report and escalate to the Project Board, which decides whether to approve a revised plan, change scope, or stop the project. The Project Manager cannot unilaterally increase budget or continue past tolerance.

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, monitoring, and controlling project activities, escalating issues or deviations that exceed tolerances. The Project Board sets the overall direction and tolerances but does not manage daily tasks.

The Quality Register is the PRINCE2 document that records quality activities and their results, including quality inspections and their outcomes. It provides the evidence needed to report on how products have performed against their quality criteria. The Project Manager should use the Quality Register to populate the End Stage Report with accurate quality performance information.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case throughout its lifecycle. This role owns the Business Case and ensures the project remains viable, justified, and aligned with organizational objectives from initiation through closure.

The Lessons Log is used to capture lessons throughout the project, including during a stage.

The Lessons Log is the PRINCE2 document specifically designed to capture and reference lessons from previous projects. During Initiation, the project manager should review the Lessons Log to identify relevant lessons that can inform planning and avoid past mistakes. The other documents serve different purposes and are not the primary source for historical lessons.

Administering quality reviews is a core administrative task of Project Support, ensuring that review meetings are scheduled, documented, and follow-up actions are tracked. This role provides the logistical and clerical backbone for quality management activities within a PRINCE2 project.

Tailoring means adapting PRINCE2 to the project's environment while still applying all principles. Using retrospectives to capture lessons is a valid way to apply 'learn from experience' in an agile context. This demonstrates that the principle can be fulfilled through techniques that align with the delivery approach, rather than being rigidly applied.

The Change Authority role in PRINCE2 operates within limits set by the Project Board. These limits define the scope of authority for approving change requests, ensuring that the Change Authority can make decisions without escalating every change to the Project Board, as long as the change falls within the agreed tolerances.

In PRINCE2, an Exception Plan is triggered when a stage tolerance is forecast to be exceeded. The Project Board authorizes this plan to address the deviation and keep the project on track. This is a key control mechanism within the Directing a Project process.

PRINCE2 defines Project Assurance as an independent oversight function that monitors compliance with the project's management stages, while Project Support provides administrative and clerical help to the Project Manager and team. This distinction is fundamental to PRINCE2's separation of assurance from management and support roles.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress updates on work packages, including actual versus planned progress, quality activities, and any issues or risks. The Team Manager is the role that manages the day-to-day work of the team and reports back to the Project Manager.

'Tailor to suit the project environment' is one of the seven PRINCE2 principles. This principle requires that the method be adapted to the specific context of the project, including its size, complexity, importance, capability, and risk, ensuring that PRINCE2 is applied appropriately without unnecessary bureaucracy.

The question describes a risk that could improve the project's likelihood of achieving its objectives, which is the definition of an opportunity (not a threat). The PRINCE2 guidance recommends the 'Exploit' response for opportunities when the project wants to ensure the opportunity is realized, making Option D correct.

In PRINCE2, the Project Board is the decision-making body that provides overall direction and control. The board meets at each stage boundary to review progress, approve the next stage plan, and assess continued business justification. It also meets when an Exception Report is raised, which signals that a stage is forecast to exceed its tolerances, requiring the board to decide on corrective action.

In PRINCE2, once the business case is approved and the initiation stage is authorized, the project manager's first step is to create the Project Plan. This is because the Project Plan provides the detailed schedule, costs, and resource allocations needed to manage the initiation stage effectively, and it is a mandatory management product for the Initiating a Project process. Without the Project Plan, the project manager cannot proceed with other activities like updating the Risk Register or reviewing the Business Case in a structured way.

Project Assurance is independent of the Project Manager and provides oversight to the Project Board. Project Support is administrative and not independent.

The Project Initiation Documentation (PID) is produced during the Initiating a Project process. This process refines the project's business justification, establishes the project management team, and creates the PID as the definitive reference document for how the project will be managed, including plans, controls, and tolerances.

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, delegating, monitoring, and controlling all project activities, and reporting progress to the Project Board. The Project Manager operates within the delegated authority of the tolerances (e.g., cost, time, scope) and must escalate any forecast deviation beyond those tolerances.

In the Managing a Stage Boundary process, the Project Manager produces an End Stage Report to summarize the current stage's performance. The PRINCE2 method requires that a Stage Plan for the next stage must also be produced during this process, as it provides the detailed plan for the upcoming work and is essential for the Project Board to authorize the next stage. Without the next Stage Plan, the project cannot proceed beyond the current stage boundary.

The Project Initiation Documentation (PID) is produced during the Initiating a Project process and serves as the baseline for the project. It consolidates key documents including the Project Plan, Business Case, and strategies, providing a comprehensive reference for measuring progress and managing the project.

The Executive is accountable for the project's success and for ensuring that the Business Case remains viable and that benefits are realized. In this scenario, the Executive must ensure the community center delivers the intended outcomes, such as social value, and is the ultimate decision-maker.

In PRINCE2, the 'Directing a Project' process is responsible for authorising project closure. The Project Board, which operates within the Directing a Project process, reviews the End Project Report and Lessons Report and gives final approval to close the project. This authorisation is a key decision point that confirms the project has delivered its objectives and can be formally closed.

The 'Manage by exception' principle requires that if a stage is forecast to exceed its tolerances, the project manager escalates the exception to the project board. The board then decides on corrective action. This ensures that decisions are made at the appropriate level of authority and that the project manager does not exceed delegated tolerances.

The Product Breakdown Structure (PBS) in PRINCE2's product-based planning technique is used to identify and decompose all the products (deliverables) required for the project. It provides a hierarchical view of the products, breaking them down from major deliverables into smaller components. The PBS answers 'what' needs to be produced, not 'how' or 'in what order' — those are addressed by the Product Flow Diagram and Product Descriptions.

The 'Communication Management Approach' describes the communication methods, roles, responsibilities, and reporting requirements for the project. It includes the format and frequency of reports to the Project Board, as well as the roles and responsibilities for managing communications. Technical specifications, budget details, and risk lists are documented in other management products, so they are not part of this approach.

PRINCE2 distinguishes projects from business as usual primarily through their temporary nature and the creation of a temporary organisation to deliver specific business products against an agreed business case. The payroll replacement fits this because it has a defined start and end and a dedicated team, whereas payroll processing itself is ongoing operations. The other options either describe business as usual or rely on size or method use, which are not defining characteristics.