PRINCE2 Foundation (PRINCE2F) — Questions 526–600

The PRINCE2 principle 'tailor to suit the project environment' allows the method to be adapted to the specific context of the project. This includes scaling documentation and combining management products where appropriate, while ensuring that the principles are still applied. Tailoring helps make PRINCE2 practical and proportionate, avoiding unnecessary bureaucracy for smaller or less complex projects.

Project Assurance in PRINCE2 is the role responsible for independently monitoring all three stakeholder interests — business, user, and supplier — on behalf of the Project Board. It checks that the project remains justified, viable, and compliant with PRINCE2 and corporate standards. It is not a decision-making role but an oversight and reporting one.

The Risk practice provides the framework for identifying, assessing, and controlling risks, including selecting responses such as transfer. To transfer a risk to a supplier, the Project Manager must document it in the Risk Register with a risk owner and ensure the response is agreed. This maintains active risk management and accountability throughout the project.

In PRINCE2, the Project Board sets stage tolerances for the Project Manager as part of the 'Manage by Stages' principle. This allows the Project Manager to manage the stage within defined tolerances without needing to escalate every minor deviation, ensuring delegated authority is clear and controlled.

The Project Board is accountable for approving the next Stage Plan at a stage boundary. This ensures that the project continues to have a valid business justification and that resources are committed appropriately. The Project Manager prepares the plan, but the Project Board authorizes it.

In PRINCE2, the Project Initiation Documentation (PID) provides a comprehensive baseline for the project, including defined roles and responsibilities. When team members are unclear about their roles, the PID is the management product that formally documents these assignments, ensuring everyone understands their accountabilities. This aligns with the PRINCE2 principle of 'defined roles and responsibilities' and the 'People' domain focus on organizational clarity.

PRINCE2 requires that any change to the business case, especially one that significantly reduces NPV and extends payback period, must be escalated to the project board for a decision. As project manager, you cannot unilaterally update the business case or change scope; you must request an extraordinary meeting to present the revised business case and seek approval to continue. This aligns with the 'continued business justification' principle and the 'manage by stages' theme.

Management by exception is a core PRINCE2 principle where the Project Board only gets involved when forecasts indicate that tolerances (e.g., time, cost, quality) will be exceeded. This allows the Project Manager to manage day-to-day within agreed tolerances, escalating only exceptions. Option B correctly captures this delegation of authority.

The principle of defined roles and responsibilities demands an explicit organisational structure, typically a Project Board with business, user and supplier representation plus defined project management roles. Telling the project manager to report to a single senior manager and proceed without a board strips out that accountability structure, so this is the principle being compromised.

The Executive is the single individual accountable for the project's success and chairs the Project Board in PRINCE2. This role provides the business justification, secures funding, and makes key strategic decisions, ensuring the project remains viable and aligned with organizational objectives.

The Project Initiation Documentation (PID) is the key document produced as an output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single source of information that defines the project's scope, objectives, and controls, and is used to obtain authorization to proceed.

The project manager should update the Communication Management Strategy to include the operational manager. This ensures the stakeholder receives relevant information and is engaged appropriately, which is part of effective stakeholder management during initiation.

Continued business justification is the principle that keeps the project aligned with strategic objectives by requiring a valid business case throughout. It ensures the project remains desirable, viable, and achievable, with reviews at stage boundaries. This gives the project board confidence that the investment continues to be worthwhile.

Continued business justification means the project must have a valid business case that is reviewed and updated throughout the project, not just at the start. Reviewing the justification at stage boundaries and on significant changes keeps the project aligned with business objectives and enables the board to stop it if the justification disappears.

The Project Brief is the key document created during the Starting Up a Project (SU) process. It outlines the project's scope, objectives, and approach at a high level, providing the foundation for the Initiating a Project process. It is later expanded into the Project Initiation Documentation (PID) during the Initiating a Project process.

The Highlight Report is produced by the Project Manager and sent to the Project Board to provide a summary of stage progress.

The Plans practice defines the means of delivering the products by establishing a structured approach to planning, including the creation of project and stage plans. This facilitates communication and control by providing a clear roadmap for stakeholders and enabling progress tracking against baselines. It is not about defining quality criteria, managing changes, or assigning roles, which are covered by other PRINCE2 practices.

A Work Package is the agreement between the Project Manager and the Team Manager covering the products, quality criteria and methods, reporting requirements, tolerances and constraints. Quality criteria and Checkpoint Report requirements are therefore essential contents. The Project Board does not authorise individual Work Packages, and the Work Package sits under the Stage Plan rather than replacing it.

The correct answer is Controlling a Stage because this process covers the day-to-day management of a stage, including authorizing work packages, monitoring progress, and taking corrective action. Once the Project Board approves the Project Initiation Documentation, the project manager uses Controlling a Stage to delegate work to Team Managers, ensuring the stage plan is executed.

During the Controlling a Stage process, the Project Manager is responsible for reporting Highlights to the Project Board (A), authorising Work Packages to Team Managers (C), and reviewing the progress of stage activities against the Stage Plan (E). Option B (reviewing and updating the Business Case) is a responsibility of the Executive/Project Board, not the Project Manager during this process. Option D (giving ad-hoc direction to the Project Manager) is performed by the Project Board, not the Project Manager.

The Project Board in PRINCE2 is the management committee responsible for overall project direction and key decisions. The three mandatory roles on the Project Board are the Executive (who owns the business case), the Senior User (who represents the users' needs), and the Senior Supplier (who represents the supplier's interests). Option A is correct because the Senior Supplier is a core Project Board role, ensuring the supplier's resources and capabilities are aligned with project deliverables.

In PRINCE2, the 'Controlling a Stage' process is responsible for authorizing work packages to be executed by the team. This process ensures that each work package is formally assigned, with clear acceptance criteria, reporting arrangements, and any constraints, before the team proceeds with delivery.

In the RACI model, accountability (A) means ultimate ownership and answerability for the task or decision, while responsibility (R) means actually performing the work. There should be only one accountable person per task, but multiple people can be responsible. This distinction ensures clear ownership and execution.

Project Assurance is independent from the Project Manager and reports to the Project Board.

The Highlight Report is the correct choice because it is the PRINCE2 management product used to provide the Project Board with a summary of progress at regular intervals during a stage. Since the stage is on track and no issues or deviations require escalation, the Project Manager should send a Highlight Report to keep the Board informed, not an Exception or End Stage Report.

The Project Manager assesses each Request for Change, evaluates its impact on the project's baselines, and provides the necessary information to the Change Authority for a decision. This ensures that the Change Authority can make an informed choice. The Project Manager is accountable for the change control procedure and acts as the link between those raising changes and those deciding on them.

The Highlight Report is a progress report that provides the Project Board with a summary of the project's status at a frequency defined in the Communication Management Approach. It is specifically designed to keep the Project Board informed of progress, achievements, and any issues or risks that require their attention. The Project Board is the sole recipient of the Highlight Report, as they are responsible for overall project governance and decision-making.

The End Project Report is produced during the Closing a Project process. It summarises actual versus planned performance, confirms the project has delivered its products, captures lessons, and provides the Project Board with the information needed to authorise project closure. It is a key output of that process.

Project Assurance is an ongoing, independent oversight role that ensures the project remains aligned with its business justification and adheres to standards throughout the project lifecycle. In contrast, a quality review is a specific, time-boxed event (e.g., a PRINCE2 quality review technique) used to evaluate a completed product against its quality criteria. The key difference is that Project Assurance is a continuous role, while a quality review is a discrete event.

The Starting Up a Project (SU) process produces the Project Brief, which outlines the project's scope and feasibility, while the Initiating a Project (IP) process produces the Project Initiation Documentation (PID), which provides a detailed plan and baseline for execution. This distinction is fundamental in PRINCE2 as SU focuses on pre-project preparation and IP on detailed planning and governance.

An off-specification (Off-spec) is the correct type of issue when a product has been delivered but does not meet its agreed specification. In PRINCE2, an off-specification is defined as a situation where a product should be produced according to its specification but is not, or where a product is delivered that does not meet its specification. This directly matches the scenario described.

Management by exception in PRINCE2 delegates day-to-day decision-making to the Project Manager within agreed tolerances set by the Project Board. The Board only intervenes when the Project Manager forecasts that a tolerance (time, cost, scope, quality, risk, benefit) will be exceeded, at which point an Exception Report is escalated. This keeps senior stakeholders focused on strategic oversight rather than routine operational detail.

A forecast breach of a stage cost tolerance removes the deviation from the Project Manager's delegated authority. PRINCE2 requires the Project Manager to produce an Exception Report and escalate it, so the Project Board can decide whether to request an Exception Plan, adjust tolerances or take other direction. Waiting, quietly cutting quality or pushing costs onto the supplier all bypass this control.

Continued business justification is a core PRINCE2 principle that requires the business case to remain viable throughout the project lifecycle. This principle ensures that the project is not started without a clear justification and that this justification is reviewed and updated at key decision points, such as stage boundaries. It directly supports the PRINCE2 focus on ongoing viability rather than a one-time approval.

The Team Manager produces Checkpoint Reports while executing the Managing Product Delivery process. This process involves accepting and executing Work Packages, and reporting progress to the Project Manager. Therefore, the Team Manager is executing Managing Product Delivery when producing a Checkpoint Report.

The Project Plan and product descriptions with quality criteria are created during the 'Prepare the Project Plan' activity. This activity ensures that the project's products, their quality requirements, and the schedule are defined before the PID is assembled. The other activities produce different strategies or consolidate the PID, but they do not involve creating the plan or defining products.

In PRINCE2, the Project Manager is responsible for preparing the Project Initiation Documentation (PID) during the Initiating a Project process. The PID is a key management product that defines the project's scope, objectives, and controls, and the Project Manager must compile it based on input from the project board and other stakeholders.

According to PRINCE2, when a Team Manager reports a work package as complete, the Project Manager must first accept the completed work package and then update the stage plan to reflect the actual progress. This ensures the stage plan remains accurate and provides a basis for assessing the impact on the project plan and any necessary corrective actions.

The Project Initiation Documentation (PID) is the definitive document produced during the Initiating a Project process. It consolidates the project's scope, objectives, approach, and controls, serving as the baseline against which project execution, monitoring, and control are measured throughout the PRINCE2 project lifecycle.

The Benefits Management Approach is produced during the Initiating a Project process because it defines how the project's benefits will be measured, managed, and realized. This document is created as part of the detailed planning and governance setup that occurs in this process, ensuring alignment with the business case.

A project is defined as a temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case. This temporary nature is the key characteristic that distinguishes a project from business-as-usual (BAU), which involves ongoing, repetitive operations with a permanent team structure. PRINCE2 explicitly states that a project has a defined start and end, and once the objectives are achieved, the project is disbanded.

In PRINCE2, the Highlight Report is a management product that is prepared by the Project Manager and sent to the Project Board. The purpose of the Highlight Report is to provide the Project Board with a summary of the project's progress at intervals defined in the Communication Management Strategy. Therefore, the statement that the Project Manager receives a Highlight Report from the Project Board is incorrect; the flow is from the Project Manager to the Project Board.

Management by exception is a key principle where tolerances are set and escalation occurs only when tolerances are forecast to be exceeded.

Project Assurance is a role within the PRINCE2 framework, responsible for ensuring that the project remains viable and compliant with its business case, while quality review is a technique used to assess the quality of products. The correct relationship is that Project Assurance is a role, and quality review is a technique, making option C correct. They are distinct concepts: one is a governance role, the other is a specific method for evaluating deliverables.

The Initiating a Project process is where the project's foundations are fully developed and documented, culminating in the Project Initiation Documentation (PID). The PID is the key output because it consolidates all essential information—including the Business Case, Project Plan, and other elements—into a single, controlled document that defines the project's scope, objectives, and governance. The Project Brief is an input to this process, not a component of the PID.

The Starting Up a Project (SU) process is designed to ensure that the project has a viable business justification and is worthwhile before committing significant resources. It answers the question 'Do we have a viable and worthwhile project?' by creating the Project Brief and selecting the Project Manager, not by producing detailed plans or the PID.

Separation ensures independent oversight. Project Assurance provides an objective check on the project's health, free from the PM's day-to-day pressures.

Learn from experience is the principle that requires the project to seek out and apply lessons from previous projects and from its own performance. Using PMO templates and reviewing similar payroll implementations directly demonstrates this principle. The other principles address viability, stage control, and product definition, but none of them specifically mandates organizational learning and contextual embedding.

Preparing the Project Plan is a key activity in the Initiating a Project process, where the detailed plan for the project is developed based on the Project Brief and the chosen strategy. This plan covers time, cost, quality, and scope, and is a core component of the Project Initiation Documentation (PID).

The principle 'Continued business justification' is fundamental to PRINCE2 and requires that a project has a justifiable reason to begin and continue. During the Initiation Stage, the project manager develops the Business Case as part of the PID to provide that justification. This ensures the project remains aligned with organizational objectives and can be stopped if the justification is no longer valid.

The Product Flow Diagram (PFD) in PRINCE2 product-based planning is specifically designed to show the sequence in which products are created and the dependencies between them. It maps out the order of product development, identifying which products must be completed before others can begin, and highlights any dependencies or parallel development paths. This helps in scheduling and understanding the critical path of product creation.

When a stage is forecast to exceed its cost tolerance, the Project Board should first request an Exception Plan from the Project Manager. The Exception Plan details how the Project Manager will recover from the exception and is a key output of Managing a Stage Boundary. Other actions like closing the project or updating the Business Case may follow, but the immediate step is to regain control through an Exception Plan.

When a Work Package is forecast to exceed its tolerances, the Project Manager must escalate the exception to the Project Board by producing an Exception Report, since only the Board can authorize a deviation beyond stage or project tolerances. The Project Manager cannot unilaterally change the baseline or instruct the Team Manager to raise the exception.

In PRINCE2, the Managing a Stage Boundary process is owned by the Project Manager and is triggered at (or near) the end of each stage. Its purpose is to prepare the End Stage Report (reviewing performance against the Stage Plan) and the next Stage Plan, which are then submitted to the Project Board for approval to continue. This process bridges the closing of one stage and the authorisation of the next.

The principle 'manage by exception' establishes that project board members set tolerances for the project manager, and the project manager only escalates if a tolerance is forecast to be exceeded. In this scenario, the stage time tolerance is forecast to be breached, so the project manager must escalate to the project board with options. This enables the board to make a decision and maintain control.

In PRINCE2, the first formal recording of lessons occurs during the 'Starting Up a Project' process. This process includes the activity 'Capture Previous Lessons' (from the 'Learn from Experience' principle), where the project manager reviews lessons from similar previous projects and records them in the Lessons Log before the project is even initiated. This ensures that the project starts with the benefit of past experience.

The Team Manager produces the Checkpoint Report for the Project Manager to report progress of a Work Package.

Project Assurance provides independent oversight to ensure that the project is managed correctly. If the Project Manager also performed assurance, it would compromise objectivity and independence.

In PRINCE2's Starting Up a Project (SU) process, the very first activity is 'Appoint the Executive and the Project Manager.' The Executive is the single individual ultimately accountable for the project's business case and is appointed by corporate/programme management; the Executive then appoints the Project Manager. This preserves the principle that accountability for business justification sits above day-to-day delivery.

In PRINCE2, the Executive (Senior Responsible Owner) is the single point of accountability for the project's business justification. This role owns the business case, ensures the project remains viable, and has ultimate authority over its initiation, continuation, and closure. The Project Manager is accountable for day-to-day management, not the business justification.

In PRINCE2, the Project Board requests a detailed plan for the next stage, which is the Stage Plan. The Stage Plan is produced at the end of the current stage (or during Initiation for the first stage) and provides the detailed management and technical steps for the upcoming stage, aligning with the 'Managing a Stage Boundary' process. This plan is essential for the Project Board to approve the continuation of the project into the next stage.

The defined roles and responsibilities principle ensures that a PRINCE2 project has a clear organizational structure, with the Project Board comprising business, user, and supplier representatives. This structure provides accountability and decision-making authority, directly addressing the need for clear representation of all three interests. Without this principle, the project would lack the necessary governance to ensure that stakeholder needs are met and that the project remains aligned with business objectives.

The Executive is ultimately accountable for the project's business justification, including ensuring value for money. Concerns about cost versus benefits must be escalated to the Executive, who owns the Business Case and has the authority to approve changes or stop the project if value is not being delivered.

The PRINCE2 principle of continued business justification requires that a project remains desirable (aligned with business objectives), viable (feasible within constraints), and achievable (realistic in scope and resources) throughout its lifecycle. This principle mandates that the business justification is formally reviewed and updated at key decision points, such as stage boundaries, to ensure the project is still worth undertaking.

The principle of defined roles and responsibilities ensures that everyone understands their role and what is expected of them, and that there is clear accountability for decisions. This is achieved by establishing a project management team structure with defined roles such as the Project Board, Project Manager, and Team Manager. The other principles address different aspects of project management, such as product focus or staging, but not the specific need for clear accountability.