PRINCE2 Foundation (PRINCE2F) — Questions 1276–1350

D is correct because PRINCE2 requires the Project Manager to escalate any forecast deviation beyond tolerance to the Project Board via an Exception Report. This triggers a formal decision process, ensuring the board can authorize corrective action before the situation worsens.

The Senior User is responsible for defining the acceptance criteria as they represent the users who will accept the final product.

A is correct because the Project Manager is responsible for preparing Stage Plans, which detail how the work for a management stage will be executed, including schedules, resources, and controls. This is a core PRINCE2 responsibility as the Project Manager translates the Project Plan into actionable Stage Plans for the Project Board's approval.

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.

SU is a pre-project process to check viability; IP is the full initiation to establish the project on a solid foundation, creating the PID.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides the foundation for the project and is used by the Project Board to decide whether to authorize the project.

Project Support provides administrative services. Options B, C, and E are typical. Option A is Project Assurance's responsibility, D is the PM's.

The Senior Supplier is responsible for providing the project's products and ensuring they meet the specified quality criteria. This role represents the suppliers who design, develop, and deliver the products, and thus bears the accountability for product quality against the defined acceptance criteria.

The Change Authority is an optional role that can be delegated by the Project Board to make decisions on change requests within defined limits. It is not the same as Project Support.

An Exception Plan is required when a stage tolerance is forecast to be exceeded and the Project Board approves a change to the plan.

Project Assurance is independent oversight; Project Support provides administrative assistance.

The Project Board authorizes initiation, authorizes stage plans, and gives ad-hoc direction. Producing Highlight Reports and managing day-to-day issues are PM/CM responsibilities.

The Business Case includes expected benefits, dis-benefits, costs, timescale, and investment appraisal. Options A and E are correct.

The Project Board is responsible for ensuring that project assurance is independent. Option D is correct.

The purpose is to provide the Project Board with information to review the current stage, approve the next stage plan, and update the project plan and Business Case.

Project Assurance is independent and checks that the project is being conducted properly, while Project Support provides administrative and advisory services.

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.

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 of the project, including its size, complexity, importance, capability, and risk, ensuring that PRINCE2 is applied appropriately without unnecessary bureaucracy.

The Quality Management Approach defines how quality will be managed, including methods and tools.

PRINCE2 defines three types of issue: Request for Change, Off-specification, and Problem/Concern. Therefore, RFC and Off-spec are correct.

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

Project Assurance is an independent oversight role that monitors the project's adherence to standards and controls, while a quality review is a specific technique used to check that a product meets its quality criteria.

An opportunity is a risk that could have a positive effect on objectives. 'Exploit' is the appropriate response to make the opportunity happen.

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.

The Project Board is accountable for the project's success and makes key decisions. Providing day-to-day management and assurance are separate roles.

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 PM produces an End Stage Report and a Stage Plan for the next stage (or Exception Plan if needed).

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process and serves as the baseline for the project.

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.

Checkpoint Reports are produced by the Team Manager (or team member) to report progress on work packages to the Project Manager during the Managing Product Delivery process.

The Project Board provides overall direction and makes key decisions. Approving stage plans and providing assurance are board responsibilities. Managing Work Packages is a Project Manager role; reporting progress is a team role; designing the risk management approach may be delegated.

The project product description is a key document that defines the project's scope, acceptance criteria, and quality expectations, which directly supports the Business Case practice by ensuring the project's outputs align with the justification for undertaking the project. It is created during the Initiating a Project process and is used to confirm that the project remains viable and aligned with the business case throughout its lifecycle.

The Starting Up a Project process ensures that the prerequisites for initiating a project are in place, such as having a Project Brief and approved initiation stage plan. It does not produce the PID or manage delivery.

The Project Brief defines the authority and responsibility of the Project Manager because it is created during the Starting Up a Project process and includes the project mandate, which outlines the Project Manager's role, authority levels, and accountability. PRINCE2 explicitly states that the Project Brief contains the project management team structure and role descriptions, making it the definitive document for the Project Manager's authority and responsibility.

Directing a Project (DP) is the process by which the Project Board authorises project closure. The Project Manager prepares the closure recommendation in Closing a Project, but the Board gives the final authorisation.

Avoid is a threat response, not an opportunity response. The opportunity responses are exploit, enhance, share, and reject.

In PRINCE2, when a project manager forecasts that a stage will exceed its stage tolerance, they must escalate the issue to the Project Board by raising an Exception Report. This is because the Project Manager has authority only within the agreed stage tolerance; exceeding it requires the Project Board to decide on corrective action, such as approving a revised plan or closing the project.

An RFC is a proposal for a change that is not currently in the project's scope or specifications. An Off-Spec is something that should be provided but is not, or is provided incorrectly. Both are types of issue.

The Starting Up a Project (SU) process appoints the Executive and Project Manager before formal initiation begins.

The Project Brief is produced in the Starting Up a Project (SU) process to provide a foundation for the Initiation Stage.

A Request for Change is a proposed change to a product specification or baseline, while an Off-specification is something that should be provided but is not (e.g., a product fails to meet its specification).

The scenario describes scope changes being implemented without formal approval, which violates the 'Manage by stages' principle. PRINCE2 requires that a project be planned, monitored, and controlled on a stage-by-stage basis, with each stage ending in a formal review and approval before proceeding. Implementing changes informally bypasses stage boundaries and the associated management controls, directly breaking this principle.

The Lessons Log is used to capture lessons as they arise. The Lessons Report is produced at the end of a stage or project.

The Executive is the single individual responsible for the Business Case in PRINCE2. They own the project's justification and ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Business Case is the Executive's primary accountability, as defined in the PRINCE2 manual.

Project Board meetings are exception-driven; they are not on a fixed schedule except for stage boundaries.

The 'Reduce' response aims to reduce probability or impact of a threat. Option B is correct.

Managing Product Delivery (MP) includes the activity of receiving and checking completed Work Packages. The Team Manager delivers the product, and the Project Manager ensures quality criteria are met before acceptance.

SU is a pre-project process to determine if there is a viable project; IP formally establishes the project with detailed planning and management approaches.

Transfer involves shifting the financial impact of a risk to a third party, e.g., through insurance or contract.

The Managing a Stage Boundary process includes updating the Project Plan and creating the next Stage Plan (or Exception Plan).

The Team Manager is responsible for producing Checkpoint Reports to inform the Project Manager of progress within a Work Package.

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

Project Assurance is an independent role that provides objective oversight to ensure the project remains viable and compliant with PRINCE2 principles, while Project Support is an administrative role that handles tasks like planning tools, filing, and configuration management. The independence of Project Assurance from the Project Manager is critical to avoid conflicts of interest, whereas Project Support serves the Project Manager and the team. This separation ensures that assurance activities are unbiased and that support services are efficient.

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

The Project Manager is responsible for maintaining the Business Case (keeping it up to date), while the Executive owns it and is accountable for its justification.

The 'Directing a Project' process in PRINCE2 is designed for the Project Board, not the project manager or team. Its purpose is to empower the Board to make key decisions (e.g., stage boundary approvals, exception plans) and exercise overall control from project initiation through closure, ensuring governance without involvement in day-to-day management.

The Project Manager is responsible for maintaining the Business Case, ensuring it remains viable and aligned with project progress. The Executive owns the Business Case but delegates maintenance to the Project Manager.

PRINCE2 is a process-based project management methodology that focuses on business justification, defined roles, and product-based planning. It explicitly covers risk management, business case management, and quality management as core themes, but it does not prescribe detailed human resource management practices; instead, it defines roles and responsibilities within the project management team.

Option A is correct because the Project Manager is responsible for preparing Stage Plans, which detail how a management stage will be executed, and submitting them to the Project Board for approval. This aligns with PRINCE2's principle of management by stages, where the Project Manager provides the detailed plan for the next stage.

An RFC is a proposal for a change that would deliver something not originally specified. An Off-specification is something that should have been provided but was not, i.e., a failure to meet a requirement.

The PID is the comprehensive document that defines the project and provides a basis for decision-making. Other documents like the Business Case are updated but the PID is the key output.

An Exception Report indicates that a tolerance is forecast to be exceeded. The Project Board must assess the situation and decide whether to approve an Exception Plan, amend the project, or close the project. Option D is correct.

IP produces the PID (which includes the Risk Management Approach) and the Project Plan, among others.

The Project Board authorizes the next stage during the Managing a Stage Boundary process. This process prepares the Stage Plan for the next stage and presents it to the Project Board for approval, ensuring that the project remains viable and aligned with the business case before proceeding.

In PRINCE2, a Request for Change (RFC) is the correct issue type for recording a proposal for a new product or a modification to a product that has already been baselined (i.e., approved and placed under configuration management). This aligns with the PRINCE2 principle of 'Manage by Stages' and the Change Control approach, where any change to a baselined product must be formally captured as an RFC before being assessed and potentially approved via the change authority.

PRINCE2 defines tolerances for time, cost, scope, quality, risk, and benefits. Quality and risk are valid tolerances.