PRINCE2 Foundation (PRINCE2F) — Questions 1651–1725

Starting Up a Project (SU) is the pre-project process that takes the Project Mandate and develops the Project Brief.

The Executive (Senior Responsible Owner) owns the Business Case and is accountable for its viability.

PRINCE2 separates the role of Project Manager from Project Assurance to ensure that assurance activities are performed independently of day-to-day management. This allows the Project Manager to focus on delivering the project's products and managing the team, while Project Assurance provides an objective check that the project remains viable, compliant with standards, and aligned with business expectations. The independence prevents conflicts of interest and ensures that assurance is not compromised by the pressures of daily project work.

The Executive (Senior Responsible Owner) owns the Business Case. The Project Manager maintains it on a day-to-day basis, but accountability rests with the Executive.

The seven themes are: Business Case, Organization, Quality, Plans, Risk, Change, Progress.

The PID includes the Project Plan, Business Case, and various management approaches. Checkpoint Reports are from MP, End Stage Report from SB, Lessons Report from CP.

If a Checkpoint Report indicates a deviation within stage tolerances, the PM can take corrective action themselves. If it threatens stage tolerance, they must escalate.

The Executive (Senior Responsible Owner) is accountable for the business justification.

A Request for Change is a proposal for a change that is not required to meet the original specification; an Off-specification is something that should be there but is not.

The Business Case is initially outlined in Starting Up a Project and fully developed in Initiating a Project, where it becomes part of the PID. It is then reviewed and updated at each stage boundary (Managing a Stage Boundary) and at project closure.

Closing a Project ensures controlled closure, product handover, and lessons learned.

Project Assurance is a continuous, independent oversight role for the Project Board, while a quality review is a specific technique to assess product quality at a point in time.

The Directing a Project process is where the Project Board authorizes the initiation of a project, authorizes stage plans, and authorizes the project closure. The Initiating a Project process includes the key authorization of the Project Initiation Documentation (PID) by the Project Board, which formally authorizes the project to proceed. Both processes involve the Project Board making critical go/no-go decisions that control the project's lifecycle.

The End Stage Report is produced at the end of each stage to summarize progress for the Project Board.

Product-based planning ensures that the project focuses on defining and delivering products rather than activities. It starts with identifying the products needed, then plans the activities required to create them.

The 'Directing a Project' process covers the Project Board's decision-making responsibilities, including providing ad-hoc direction to the Project Manager. This process runs from project initiation to closure and is the only process where the Board gives unplanned guidance outside of stage boundaries.

The End Project Report provides a final assessment of project performance against the PID, and is used to evaluate project success and inform future projects.

The Project Board, as part of the Directing a Project process, authorizes the initiation stage. The Executive chairs the Board but authorization is a Board decision.

The Change Authority is a role that can approve changes within an agreed delegated authority level. It is set up by the Project Board and can be an individual or group.

The Executive (SRO) has single-point accountability for the Business Case.

Closing a Project ensures controlled closure, handover of products, and confirmation of benefits review arrangements.

The principle 'Learn from experience' is not being applied because the project team is repeating the same mistakes from previous projects without reviewing lessons learned logs or incorporating feedback. PRINCE2 requires continuous learning throughout the project lifecycle, but the exhibit shows no evidence of lessons being documented or used to improve current practices.

The PM must escalate via an Exception Report to the Project Board.

PRINCE2 recommends that Project Boards meet at the end of each management stage (Stage Boundary) and when an Exception Report is raised. They should not meet on a fixed monthly basis; meetings are exception-driven.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is the principle of management by exception.

The Quality Register records all planned quality activities and their results, providing a log of quality checks.

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

The Project Board is responsible for providing overall direction and control to the Project Manager, but it does not handle day-to-day management. It meets on an exception-driven basis to review and decide on exception reports when a project deviates significantly from its tolerances, ensuring management by exception is applied. This is a core PRINCE2 principle that allows the board to focus on strategic decisions rather than routine operations.

Option B is correct. The principle 'Manage by stages' states that a project should be planned, monitored, and controlled on a stage-by-stage basis. 'Manage by exception' is about tolerances.

The Change Authority is an optional role delegated by the Project Board to make decisions on change requests within defined limits. They can approve RFCs up to a certain cost or impact. They are not responsible for configuration management or raising RFCs.

Options A and D are correct. DP includes authorizing initiation and authorizing the project. Managing product delivery is MP; escalating issues is part of CS (PM role).

The Initiating a Project process produces the Project Initiation Documentation (PID), which includes the Project Plan, Business Case, and various management approaches. The Project Brief is an output of SU, and the End Stage Report is from SB.

In PRINCE2, the recommended leadership style for a Project Manager when the team has high competence but low commitment is Supporting (S3). This is because the team already possesses the necessary skills and knowledge (high competence) but lacks motivation or confidence (low commitment), so the PM should focus on encouraging, praising, and involving them in decision-making rather than providing technical direction or close supervision.

PRINCE2 provides a common language, control of resources, and a focus on business justification.

Project Support provides administrative and support services, such as maintaining files, providing planning support, and managing project administration.

The Project Board provides direction, approves plans, and authorizes deviations. Detailed review of products is not a Board responsibility; that is done by quality review. The configuration management plan is part of the project's management approach and is approved by the Board but not 'maintained' by them.

An RFC proposes a change or enhancement; an Off-specification is a product that fails to meet its specification. Both are issues but differ in cause.

Option A is correct. The Project Manager authorizes Work Packages in Controlling a Stage.

The Quality Review technique is a formal process for reviewing product descriptions and checking quality. It involves a chair, presenter, and reviewers. Options A and D are correct; B is wrong because reviewers are not necessarily from the project team; C is wrong because it is a 'peer review', not an 'audit'; E is wrong because it can be used for any product, not just those for external stakeholders.

The Controlling a Stage (CS) process is where the Project Manager authorizes work packages, monitors progress, and handles issues. The Team Plan is part of the work package assignment, so it is used in CS.

The Project Board authorises initiation, gives ad-hoc direction, and authorises closure. Producing Highlight Reports is a Project Manager responsibility, and managing day-to-day work is a Team Manager responsibility.

An RFC is a proposal for a change that adds value or modifies requirements; an Off-spec is something that should be provided but is not (e.g., a defect or omission).

The project manager should use the Controlling a Stage process because it is specifically designed to monitor the day-to-day work of the stage, manage issues and risks, and take corrective action to keep the stage on track. The symptom of frequent re-prioritization and loss of focus indicates a lack of control within the current stage, which this process directly addresses by providing mechanisms for work package assignment, progress monitoring, and escalation. It ensures the stage remains within tolerance and that the team's efforts are aligned with the stage plan.

Option A is correct because a Request for Change (RFC) is a formal proposal to modify an agreed product, baseline, or configuration item, while an Off-specification (Off-spec) is a notification that a product does not meet its agreed specification. In PRINCE2, these are distinct issue types: RFCs seek authorization for a change, whereas Off-specs report a deviation from the specification that must be resolved.

The Risk Management practice aims to identify and manage risks proactively. Avoiding all risks is unrealistic; removing uncertainty is not possible.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets the user's needs and acceptance criteria.

Quality review: plan, distribute, prepare, meet, and follow up.

The Plans practice aims to define the means of delivering the project, create a baseline for control, and communicate the work to stakeholders. Options A, B, and E are correct; C is the purpose of the Business Case; D is the purpose of the Risk practice.

Option C is correct. Tailoring is adapting PRINCE2 to the project's specific context. Embedding is integrating PRINCE2 into the organization's management system.

In PRINCE2, any change that impacts the Business Case must be formally assessed before action is taken. The project manager's first responsibility is to evaluate the change's effect on the Business Case (costs vs. benefits) and then submit a formal change request to the Project Board, which holds authority for approving changes that alter the project's justification. Option D aligns with the 'manage by stages' and 'continued business justification' principles.

CS includes activities like authorizing Work Packages, managing issues, and reviewing progress. Closing the project is CP; creating the Project Plan is IP.

The risk owner is responsible for managing the risk; the risk actionee is responsible for carrying out specific actions.

The Senior User is responsible for specifying the required quality criteria for the project's products and ensuring that the delivered products meet those criteria. This role represents the interests of those who will use the project's outputs and is accountable for defining acceptance standards and verifying that products satisfy the defined quality expectations.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and ensuring it remains viable. The Project Manager maintains it day-to-day, but the SRO owns it. This is a key PRINCE2 principle.

The Highlight Report is a periodic report from the Project Manager to the Project Board, summarizing progress against the current stage plan.

The purpose of Closing a Project is to provide a fixed point to verify that all project products have been accepted, confirm that the project has met its objectives, and recommend project closure.

The Risk Register is the PRINCE2 management product used to record and track all identified risks that could affect the project. It captures details such as risk description, probability, impact, proximity, and planned responses, ensuring risks are managed proactively throughout the project lifecycle.

The Project Brief is the correct management product to review because it contains the high-level project definition, including the project objectives and how they align with corporate strategy. During the initiation stage, if the objectives are misaligned, the Project Brief provides the basis for reassessing the project's justification and strategic fit before proceeding further.

Managing a Stage Boundary enables the Project Board to review progress, approve the next stage plan, and update the Business Case.

Project Assurance provides independent oversight to ensure that the project is being managed correctly, separate from management and delivery.

PRINCE2 defines specific threat response types: avoid, reduce, fallback, transfer, accept, and share. 'Mitigate' is not a PRINCE2 term; 'reduce' is used instead.

The Directing a Project process is specifically designed for the Project Board to provide overall direction and control, including making key decisions and issuing ad-hoc instructions outside of the regular stage management cycle. It covers activities like authorizing initiation, stage plans, and project closure, as well as giving ad-hoc direction to the project manager when needed.

Transfer involves shifting the financial impact of a risk to a third party, such as through insurance.

The Senior Responsible Owner (SRO/Executive) is accountable for the business case and its ongoing viability throughout the project.

Option C is correct because the project has consumed 95% of the budget while delivering only 40% of the scope, making the original business case no longer viable. PRINCE2 requires continuous business justification; if the costs outweigh the benefits, the project should be closed. The project manager must advise the board to close the project as continuing would waste further resources.

Option B is correct because PRINCE2 defines the Senior Responsible Owner (SRO) as the single person accountable for the business case and overall project success, and it is a formal role within the PRINCE2 Project Board. 'Project Sponsor' is a generic term used in many organizations but is not a defined role in the PRINCE2 methodology. Therefore, the key difference is that the SRO is a specific PRINCE2 role, while 'Project Sponsor' is not part of the PRINCE2 terminology.

Starting Up a Project is a pre-project process to ensure that the project has a viable business justification and that the necessary people and resources are available before committing to the full initiation stage.

The purpose is to provide the Project Board with information to approve the current stage's completion and authorize the next stage.

Option B is correct. A Team Plan is created by the Team Manager to detail the work needed to deliver the products assigned in a Work Package. Stage Plans cover an entire stage; the Project Plan covers the whole project; Exception Plans replace a plan when tolerances are exceeded.

Option A is correct because '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, complexity, size, and risk of the project, ensuring the framework remains relevant and practical without unnecessary overhead.

SB includes updating the Business Case and planning the next stage. Authorising Work Packages is done in CS, and delivering products is done in MP.