PRINCE2 Foundation (PRINCE2F) — Questions 1351–1425

PRINCE2 defines a project as a temporary organization created to deliver one or more business products according to an agreed Business Case. This definition emphasizes the temporary nature of a project, its focus on outputs (products), and the necessity of a validated Business Case to justify the investment. It distinguishes projects from ongoing operations by highlighting the unique, time-limited structure and the governance provided by the Business Case.

The 'Plan' step is where risk responses are developed and selected. The 'Assess' step evaluates probability and impact, but the decision on how to respond is part of planning.

The Project Manager is delegated by the Project Board to manage the project on a day-to-day basis within agreed tolerances.

In PRINCE2, quality is defined as 'fit for purpose,' meaning the product meets the stated requirements and is suitable for its intended use. This definition emphasizes that quality is about satisfying the agreed-upon specifications and user needs, not about achieving an abstract standard like zero defects or ISO compliance.

Starting Up a Project (SU) is a pre-project process. Its purposes include ensuring that the project has the necessary authorities to proceed (Option C) and ensuring that a viable Business Case exists before the project proceeds (Option D). Option A (authorize the project) is done in Directing a Project; Option B (produce the PID) is done in Initiating a Project; Option E (update the Business Case with actual costs) is done during Controlling a Stage.

Project Assurance provides independent oversight of the entire project on behalf of the Project Board, whereas a quality review is a specific technique to assess the quality of a product.

In the Controlling a Stage process, the Project Manager sends the Highlight Report to the Project Board at regular intervals to provide a summary of progress against the stage plan, including achievements, next steps, and any issues or risks. This report is the standard communication tool for keeping the board informed during a stage, as defined in PRINCE2.

MP is where the Team Manager executes the Work Package and produces Checkpoint Reports. The PM authorises the Work Package at the start.

The seven principles include Manage by Stages and Continued Business Justification. 'Use of Agile' is not a principle.

The Project Plan is the correct artifact to update because it defines the overall project timeline, milestones, and resource estimates. When the duration is underestimated during Initiation, the Project Plan must be revised to reflect a realistic schedule before it is approved by the project board. Updating the Project Plan ensures the baseline for the entire project is accurate, which is critical for subsequent stage planning and control.

The Purpose of the product is a mandatory element in a PRINCE2 Product Description. It defines why the product is needed and how it contributes to the project's objectives, ensuring all stakeholders understand its role before development begins.

During Managing a Stage Boundary, the PM prepares the End Stage Report and next Stage Plan. The issue should be documented with a recommendation for the Project Board to decide.

The Initiating a Project process produces the Project Initiation Documentation (PID) as its key output. The PID consolidates all essential information required to manage the project, including the Business Case, Project Plan, and controls, and serves as the foundation for the next stage. It is the definitive document that authorizes the project to proceed.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case and its continued viability because PRINCE2 defines this role as the single point of accountability for the project's justification. The Executive owns the Business Case throughout the project lifecycle, ensuring it remains aligned with corporate strategy and approving any changes that affect its viability. This accountability cannot be delegated to the Project Manager, who is responsible for day-to-day management but not for the business justification.

The Initiating a Project process is responsible for establishing a solid foundation for the project, and its key output is the Project Initiation Documentation (PID). The PID consolidates all the essential information needed to justify, define, and plan the project, including the Business Case, Project Plan, and Risk Register. It serves as the definitive reference document for the project board to authorize the project.

The Project Board authorises the stage by approving the Stage Plan. Work cannot start without this authorised plan.

The Project Initiation Documentation (PID) is the main output of Initiating a Project.

The Business Case in PRINCE2 justifies the project's initiation and continued viability. It must include the expected benefits (tangible and intangible) that the project aims to deliver, as well as the major risks that could affect those benefits. Therefore, options C and D are correct components.

The Product Description includes quality criteria and is used to verify that the product meets requirements.

The Project Manager must first assess the impact of the delay on the Stage Plan and decide on corrective action within the agreed stage tolerances. This aligns with the PRINCE2 principle of management by exception, where the Project Manager handles deviations within tolerances before escalating. Only if the delay exceeds stage tolerances should an Exception Report be raised to the Project Board.

The PRINCE2 definition of a risk owner is the person who is responsible for managing all aspects of a specific risk, including monitoring the risk, implementing the planned response actions, and ensuring the risk is effectively controlled. This role is accountable for the risk throughout its lifecycle, not just for executing a single task.

Project Assurance is a PRINCE2 role responsible for providing an independent, objective check to the Project Board that the project remains viable, compliant, and on track. It is not a day-to-day management function but a governance safeguard, ensuring that the project adheres to its business case, quality standards, and tolerances without being influenced by the Project Manager or delivery team.

CS includes authorising Work Packages, reviewing progress, reporting highlights, and managing issues and risks.

Closing a Project (CP) is the process that ensures controlled closure, including product handover and formal acceptance.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is management by exception. The PM cannot increase the budget or continue without escalation.

A Request for Change (RFC) is a proposal for a future modification to the project's baselined products, while an Off-specification (Off-spec) is a problem that has already occurred, indicating that a product does not meet its specification. In PRINCE2, the key distinction is timing: RFCs are proactive and seek approval for a planned change, whereas Off-specs are reactive and document a deviation that has already happened.

When a Work Package tolerance is forecast to be exceeded, the Team Manager must escalate to the Project Manager via an Exception Report. The Project Manager can then negotiate corrective actions.

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

The Risk practice covers the systematic management of threats and opportunities.

The 'manage by stages' principle requires that the project manager plans only one stage at a time in sufficient detail, while the next stage is planned just before it begins. In a distributed team with time zone delays, the first step is to plan the next management stage with clear communication milestones that explicitly account for time zone differences, ensuring that stage boundaries and decision points are synchronized despite the delays.

The key output of the Initiating a Project process is the Project Initiation Documentation (PID). The PID consolidates all baseline information needed to justify proceeding with the project, including the Business Case, project scope, and management strategies. It serves as the foundation for decision-making by the Project Board and is formally approved before moving to the next stage.

According to PRINCE2, if a stage has exceeded its cost tolerance, the Project Board cannot authorize the next stage without first assessing the situation. The correct action is to request an Exception Plan, which details how to recover from the deviation and bring the project back within tolerance. This ensures the board has a revised forecast and recovery strategy before committing to further expenditure.

The Risk Management Approach and Benefits Management Approach are both management products created during the Initiating a Project process. The Risk Management Approach defines how risk will be managed throughout the project, while the Benefits Management Approach defines how the project's benefits will be realized and measured. These are documented in the Project Initiation Documentation (PID) and are key outputs of this process.

The Executive is accountable for the Business Case, appoints the Project Manager, and chairs the Project Board. Providing customer assurance is the Senior User's role; producing Highlight Reports is the Project Manager's role.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information—such as the current stage's performance, updated business case, and the next stage's plan—to make an informed decision about whether to authorize proceeding to the next stage. This process ensures that the project remains viable and aligned with business objectives before committing further resources.

Avoid, reduce, and transfer are threat responses. Exploit and enhance are opportunity responses.

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

During CP, the PM should ensure all products are accepted. If a defect exists, it should be documented in the Lessons Report and an updated product status should be provided. The board decides acceptance.

The Project Plan contains the project-level tolerances, including cost and time.

The project is within the stage tolerance of 10% (currently at 5% over time), and the Project Manager expects the trend to continue but has not yet exceeded the tolerance. According to PRINCE2, the Project Manager should continue managing the work within the agreed tolerance and report the deviation in the next Highlight Report, as this is the standard mechanism for communicating progress and forecast deviations that are still within tolerance. Raising an Exception Report is only required when a deviation is forecast to exceed the stage tolerance, which is not the case here.

The Business Case in PRINCE2 is the key document that justifies the project's initiation and continued viability. It must include the expected benefits (B) to demonstrate the positive outcomes the project aims to achieve, and it must identify major risks (E) to provide a balanced view of the potential downsides and uncertainties. These two components are explicitly required by the PRINCE2 Business Case theme.

The Senior User specifies user needs, ensures the solution meets them, and is responsible for realizing benefits. The Senior User does not own the Business Case (Executive does) and does not manage risks day-to-day (Project Manager does).

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a foundation for project execution.

The Senior User represents the users and is responsible for ensuring the project delivers the required benefits; however, the Executive (Senior Responsible Owner) owns the Business Case. In PRINCE2, the Executive is ultimately accountable for the Business Case, but the Senior User provides input on benefits. The question asks who maintains it, and the correct answer is the Executive.

Project Assurance is a PRINCE2 role responsible for verifying that the project remains viable and compliant with its business case, plans, and standards, independent of the Project Manager. A quality review is a specific technique used to assess whether a product meets its defined quality criteria and to identify defects. The key difference is that Project Assurance provides ongoing oversight of the project's adherence to plans and governance, while a quality review focuses on the quality of a specific product at a point in time.

The Senior Responsible Owner (SRO/Executive) is accountable for the project's success and owns the Business Case.

Directing a Project (DP) is the process where the Project Board makes key decisions, including authorizing initiation. Starting Up a Project (SU) prepares the conditions but does not authorize initiation.

The End Project Report confirms acceptance of products and provides a summary of project performance.

The Project Manager produces Highlight Reports to inform the Project Board of progress during a stage.

The Benefits Review Plan is created during the Initiating a Project process.

In a strong matrix structure, team members report to both functional and project managers, which can create loyalty conflicts. PRINCE2's 'defined roles and responsibilities' practice, documented in the Project Initiation Documentation (PID), clarifies each team member's authority, accountability, and reporting lines. This formal definition reduces ambiguity and reinforces commitment to the project by making project responsibilities explicit.

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

In PRINCE2, the separation of Project Management and Project Assurance ensures that those who are managing the project (Project Manager) are not the same individuals providing independent assurance. This prevents conflicts of interest and ensures objective oversight of the project's adherence to plans, standards, and controls.

The Project Brief contains the outline Business Case, project approach, and other information needed for the Project Board to decide whether to proceed to initiation.

According to PRINCE2's management by exception, if a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. The PM cannot unilaterally change the plan.

The Team Manager provides Checkpoint Reports at regular intervals. The Project Manager uses these to compile Highlight Reports for the Project Board.

The Senior User is responsible for specifying the user requirements and ensuring that the project delivers the expected benefits. This role represents the interests of the users and is accountable for defining the desired outcomes and confirming that the project's products meet those needs.

If the change is outside the Change Authority's delegated scope (e.g., affects items they cannot approve), the Project Manager must escalate to the Project Board.

The PRINCE2 methodology is built on seven core principles that guide project management. 'Learn from Experience' (B) is a principle that requires the project team to actively seek and apply lessons learned from previous projects and throughout the current project's lifecycle. 'Focus on Products' (D) is another principle, emphasizing that a project is only successful if it delivers the defined products that meet the agreed-upon quality criteria, shifting the focus from activities to outputs.

The Project Board is responsible for approving Stage Plans and any updates to them during the Directing a Project process. This ensures that the project remains aligned with the business case and that management stage boundaries are properly controlled.

The Team Manager should first record the quality problem as an issue and escalate it to the Project Manager, who will decide how to handle it. The Team Manager cannot unilaterally change the product or stop work without authorization.

PRINCE2 defines a project as a temporary organization that creates a unique product. Business as usual is ongoing and repetitive, not temporary.

The PRINCE2 risk management procedure follows: identify, assess, plan responses, implement, and monitor.

In PRINCE2, the Project Manager must first review the completed work package against its agreed criteria (e.g., quality tolerances, deliverables) before formally accepting it. This aligns with the 'Review Work Package' step in the Controlling a Stage process, ensuring that only verified outputs are approved. Option B is correct because the Project Manager cannot proceed to authorize further work or update plans until the current work package is formally accepted.