PRINCE2 Foundation (PRINCE2F) — Questions 1126–1189

The Executive owns the Business Case, being accountable for ensuring the project remains justified and delivers value for money. This satisfies the stem because ownership sits with the single individual representing the business interest, not the Project Manager, who only maintains it.

Separating these roles preserves objectivity: Project Assurance reports to the Project Board, not the Project Manager, so it can scrutinise the project's viability, costs and risks independently. This satisfies PRINCE2's accountability principle, letting the Project Manager concentrate on day-to-day delivery without self-reviewing their own performance.

The 'Defined roles and responsibilities' principle ensures that a project has a clear organizational structure with defined roles for all stakeholders, including business, user, and supplier. This principle is essential for effective decision-making and accountability. It requires that the project management team is structured to represent these interests, ensuring that the project meets its objectives and that all parties are engaged appropriately.

In PRINCE2, the project board sets tolerances for the project manager. When an issue or change is forecast to exceed those tolerances, it must be escalated to the project board for a decision. The board can then approve, reject, or defer the change, and may also adjust tolerances. This preserves management by exception and keeps accountability at the right level.

Assessing impact on stage tolerances first satisfies the Controlling a Stage requirement to manage by exception. The Project Manager must determine whether the delay breaches delegated tolerance before acting; if within tolerance, corrective action stays at stage level, avoiding unnecessary escalation to the Project Board.

The Executive owns the Business Case and is accountable for the project's ongoing viability and business justification, continuing to verify it throughout delivery. This role sits on the Project Board, distinct from the Project Manager who handles day-to-day delivery.

Tailoring allows adaptation of processes, themes, roles, terminology, and management products to suit the project. However, all seven principles must remain applied; tailoring cannot be used to justify removing a principle such as continued business justification or manage by exception. This statement accurately reflects the relationship between tailoring and principles.

The Project Product Description is a special type of product description that defines the project's final product. It includes the product's purpose, composition, derivation, quality criteria, quality tolerance, and acceptance criteria. It is used to gain agreement on the project's output and is part of the PID. This description ensures that the project board and stakeholders have a shared understanding of what the project will deliver.

The project board is responsible for approving the PID at the end of the Initiation Stage. This approval authorizes the project to proceed and confirms that the project is viable and aligned with strategic objectives. The project board reviews the PID to ensure it contains the necessary information to manage the project and that the Business Case is sound.

The business case theme is concerned with establishing whether the project is desirable, viable and achievable, and with maintaining that justification throughout the project. In this CRM implementation, the project board uses the business case to confirm continued alignment with corporate strategy and to decide whether to continue, change or stop the project. This theme directly addresses ongoing viability and investment justification, making it the correct answer.

This principle requires PRINCE2 to be adapted to the project's size, complexity, and organisational context. Using the Programme Office's templates and assurance reviews is an example of tailoring to the existing environment, ensuring the method fits the organisation's standards and governance without reinventing processes.

Closing a Project confirms that the project's products have been formally accepted by the customer and that the project is disbanded in a controlled manner. It satisfies the stem's requirement for controlled closure, covering handover, acceptance records and post-project recommendations.

Project Assurance is an ongoing role delivering independent oversight of the project's viability and compliance to the board, whereas a quality review is a structured technique applied at a point in time to evaluate whether a specific product meets its quality criteria.

The End Stage Report is produced by the Project Manager at the end of each stage, summarising progress, issues and the next stage plan so the Project Board can authorise the following stage at the end stage assessment.

The Project Board is ultimately accountable for the project and retains authority for decisions beyond the delegated threshold. When a change exceeds the Change Authority's limit, it must be escalated to the Project Board for a decision. This aligns with the PRINCE2 principle of management by exception, ensuring that higher-level authority handles significant deviations.

Product-based planning defines the project's products and their components before activities, so the plan is driven by what must be delivered. This satisfies the stem's purpose by focusing the project on creating and verifying agreed products, clarifying scope and reducing the risk of missing deliverables.

Ad-hoc direction from the Project Board occurs within Directing a Project, the process owned by the Board itself. It provides the decision-making channel through which the Board authorises, monitors and controls the project, issuing guidance outside scheduled stage boundaries. Managing a Stage Boundary and Controlling a Stage sit with the Project Manager, so they cannot satisfy this constraint.

Establishing a common vision and objectives helps align team members from different organizations towards a shared goal. This is crucial for building effective teams, as it provides direction and fosters collaboration, reducing the risk of misunderstandings and conflicts.

The End Project Report summarises project performance against the baseline and records lessons learned, providing the Project Board with the information needed to confirm project closure. This satisfies the requirement to evaluate achievements and capture organisational learning during Closing a Project.

This is the definition.

The Executive owns the Business Case and remains accountable for the project's ongoing viability, so business justification sits with this role. The Project Manager handles day-to-day delivery, while the Senior User and Senior Supplier represent user and supplier interests respectively.

Cost tolerance breach means the stage or project plan can no longer be delivered within its agreed limits, so the deviation must be escalated to the Project Board. The Exception Report documents the cause, impact and options, enabling the Board to decide whether to authorise a revised plan.

PRINCE2 mandates Project Board meetings at each stage boundary to authorise the next stage, and additionally whenever an Exception Report is escalated, since tolerances have been breached. This satisfies the stem's requirement by defining the two trigger points, rather than relying on a fixed calendar schedule.

Within Managing Product Delivery, the Team Manager must obtain authorisation from the Project Manager before starting or continuing work on a Work Package. Since the design phase is complete and the build phase is part of the same Work Package, the Team Manager needs the Project Manager's approval to proceed. This ensures the Project Manager maintains control over the work.

The Executive is the single point of accountability for the project and is responsible for ensuring that the project delivers the business benefits outlined in the Business Case. This role owns the Business Case and must ensure that the project remains aligned with business objectives throughout its lifecycle.

The Change Authority is a role that can be appointed by the Project Board to make decisions on changes within defined tolerances. They are responsible for approving or rejecting changes that fall within their delegated authority, thus reducing the burden on the Project Board. In this scenario, the Change Authority is the correct role to approve changes within the set limits.

The Quality Register records quality review results and quality check progress, tracking planned and completed quality activities for products. This satisfies the stem's requirement by providing the central log of quality review outcomes and the status of each quality check throughout the project.

These are distinct issue types on different axes. A Request for Change asks to alter an already-agreed product's baseline, whereas an Off-specification reports that a product has failed to meet its agreed specification. Both are captured in the Issue Register and assessed for impact.

This principle requires that the project remains aligned with strategic objectives and that the business case is reviewed at stage boundaries. The board is checking that the project still provides value. This is a direct application of the principle, as it ensures the project continues to be justified beyond the initial approval.

Dividing a project into management stages directly enacts the Manage by Stages principle, which requires that the project be planned, monitored and controlled stage by stage. The stem's act of splitting work into discrete management stages is precisely this principle in operation.

The Board delegates authority to the Change Authority for certain decisions.

The End Stage Report is produced during the Managing a Stage Boundary process. It summarizes the stage's performance against its plan and provides a forecast for the next stage. It is exactly what the project board requested. The report also includes an updated Business Case and a review of risks and issues.

The Executive is the single point of accountability for the project and is responsible for ensuring that the project delivers the specified benefits. They own the business case and must ensure that the project remains justified throughout. This role represents the business interests and is ultimately answerable for the project's success in realizing benefits.

Project Support provides specialist help with the project's planning and control products, assisting those producing and updating plans and schedules. This satisfies the stem by naming a genuine support responsibility, distinct from the Project Manager's accountability for the plans themselves.

The outline Business Case is a high-level justification that includes estimated costs, benefits, risks and timescales. It is expected to be refined and detailed further during Initiating a Project when the full Business Case is developed. Including high-level estimates and noting future refinement is exactly what PRINCE2 recommends for this stage, making this the correct approach.

The Project Manager authorises Work Packages, agreeing the scope, tolerances and reporting requirements with the Team Manager before work begins. This sits within the Controlling a Stage process, where the Project Manager retains accountability for delivery against the Stage Plan.

Controlling a Stage is the process where the project manager authorises work packages, monitors progress against tolerances and takes corrective action. Re-prioritising and loss of focus indicate a stage drifting from plan, so this process restores control through work package review and exception escalation.

Risk Management proactively identifies threats and opportunities, assesses them and plans responses before they materialise, embedding risk thinking into all PRINCE2 processes. This satisfies the stem's requirement for proactive identification and management rather than reactive firefighting after issues occur.

The Work Package is the document that authorizes the Team Manager to start work. It includes the product description, constraints, interfaces, and reporting requirements. Once agreed, it serves as the authority for the Team Manager to proceed with the assigned work.

Tailoring adapts PRINCE2's processes, themes and roles to suit a specific project's scale and complexity, whereas embedding integrates the method into an organisation's culture and working practices. This distinction satisfies the stem by separating project-level adaptation from organisation-wide adoption.

Assessing the Business Case impact and submitting a change request to the project board satisfies PRINCE2's principle that changes must be evaluated against continued business justification before approval. The board, not the project manager, decides whether increased benefits outweigh increased costs.

Ownership sits with whoever is accountable for managing and monitoring the risk through its lifecycle, whereas the actionee carries out the specific response actions assigned. This split satisfies the stem's need to separate accountability for the risk from execution of planned responses.

The Highlight Report is produced by the Project Manager for the Project Board, summarising stage progress, status and any exceptions. This satisfies the stem by identifying both the sender and recipient, distinguishing it from Checkpoint Reports, which stay within the team.

This principle requires that a project has a valid Business Case and that it remains justified throughout. Changes that are not assessed against the Business Case could undermine the project's viability. Therefore, allowing changes without impact assessment directly violates the principle of continued business justification.

The Risk Register records all identified risks, their probability, impact, proximity, and assigned responses throughout the project. It is the single repository PRINCE2 mandates for capturing and tracking every risk that may affect the project, satisfying the stem's requirement.

Project Assurance provides independent monitoring of all aspects of the project, checking that the project remains viable and aligned with the business case. This independence from the project manager satisfies the Organising practice's requirement for objective oversight across all stakeholder interests.

The Project Board retains overall accountability for the project and is responsible for authorizing changes that fall outside the authority delegated to the Change Authority. When a change exceeds the delegated limits, the Project Manager must escalate it to the Project Board for a decision.

Directing a Project is the Project Board's process for ad-hoc direction, authorising the project, stage boundaries and closure. It satisfies the stem's requirement for board-level guidance outside the normal Managing a Stage Boundary cycle, enabling decisions such as exception handling without invoking delivery processes.

Purchasing insurance transfers the financial impact of supplier bankruptcy to the insurer, satisfying the stem's constraint of a third party absorbing the loss. Under PRINCE2, transfer shifts ownership of the risk's financial consequences, though the threat itself remains; the insurer now bears the cost should bankruptcy occur.

The principle of continued business justification states that a PRINCE2 project must have a justifiable reason to start and continue. This principle directly emphasizes the need for a valid Business Case that is reviewed and updated throughout the project. It ensures that the project remains aligned with business objectives and delivers value. The Executive's request for benefits and measures aligns with this principle.

The Executive, also called the Senior Responsible Owner, owns the business case and is accountable for confirming the project remains viable and delivers the expected benefits throughout each stage, justifying continued investment against the Business Case theme.

Spending 95% of budget against only 40% of scope breaches the approved +/-10% cost tolerance, so the business case no longer holds. Recommending closure lets the board stop further investment rather than continue a project whose forecast benefits cannot justify remaining spend.

PRINCE2 uses SRO, not sponsor.

Tailoring allows the Risk Management Strategy and Risk Register to be combined into one document for small projects, provided the required information is still captured. This reduces documentation and effort while maintaining risk management. It is an acceptable tailoring action when the project's scale and complexity do not justify separate artefacts.

The Business Case is the document that contains the business justification for the project, including the summary of costs, benefits, and risks. It is updated at stage boundaries to reflect the current situation. The project board uses the Business Case to make informed decisions about the project's continuation. Therefore, this is the correct document to provide the requested information.

Tailoring the number of stages is valid for small projects, provided that the Project Board retains control and can review progress. A single stage may be sufficient for a low-risk website update, but the Project Board must still authorize the project and review at key points to maintain the manage by exception principle and overall control.

The Team Plan sits below the Stage Plan and covers the work a team performs to produce one or more products within a stage. It translates stage-level products into team-level activities, scheduling and tolerances, which is precisely the granularity the question describes.

Updating the Business Case is a Managing a Stage Boundary activity: the Project Manager reassesses viability and benefits at each stage end, then submits the updated Business Case with the End Stage Report for the Project Board's continuation decision.

Managing Product Delivery sits between the Project Manager and Team Manager, receiving authorised Work Packages and executing them. Accepting and executing Work Packages is a stated purpose, satisfying the question's requirement for a genuine purpose of that process.

The Quality Review technique examines a product against the quality criteria defined in its Product Description, then records any required improvements. This satisfies the stem's purpose by combining assessment against criteria with identifying follow-up actions, rather than merely approving or rejecting the product.

Project Assurance is a defined PRINCE2 role within the project management team, responsible for monitoring all aspects of the project independently of the Project Manager. A quality review is a technique used to assess a product against its quality criteria. This distinction satisfies the stem's requirement to differentiate a role from a technique.

The Executive owns the Business Case, remaining accountable for its viability throughout the project. They judge whether the justification still holds at each stage boundary and can trigger premature closure if benefits no longer outweigh costs.

Risk tolerances define the acceptable level of risk exposure for the project. If a risk's probability and impact exceed these tolerances, it must be escalated to the Project Board, as it may threaten the project's business case. The Project Manager cannot unilaterally accept risks beyond delegated tolerances.