PRINCE2 Foundation (PRINCE2F) — Questions 1–75

Option B is correct because the PRINCE2 'Organizing' practice defines the project management team structure, which establishes clear roles and responsibilities for all team members. This structure ensures accountability and effective communication throughout the project lifecycle.

SU is a pre-project process to determine if there is a viable project, while IP formally establishes the project foundation with detailed planning and management strategies.

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

Reviewing progress against the stage plan is a key activity within Controlling a Stage, where the PM monitors and controls work.

SU outputs include the Project Brief, initiation Stage Plan, Daily Log, and appointment of the Executive and PM. The PID and Risk Register are outputs from IP.

In PRINCE2, the Executive is the single point of accountability for the business case and must approve any changes to it. If the Executive is unavailable, no other role can substitute for this authority; the project manager must escalate the decision to the full Project Board. This ensures that business justification decisions are never made without the accountable party or the collective board.

The Project Manager manages the project on a day-to-day basis within the tolerances set by the Project Board.

According to PRINCE2, when a Stage Plan exceeds the agreed cost tolerance, the project board cannot approve it. Instead, the project manager must produce an Exception Plan that describes the options to bring the stage back within tolerance or to request a revised tolerance. This is a formal exception management process defined in the PRINCE2 manual.

A Product Description defines the product's purpose, composition, derivation, and quality criteria.

When a stage tolerance is forecast to be exceeded, the Project Manager raises an Exception Report and then, if directed by the Project Board, produces an Exception Plan during Managing a Stage Boundary.

The PRINCE2 risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate. After identification, the next step is to assess the risk (probability and impact).

The Highlight Report is a time-driven report from the Project Manager to the Project Board, providing a summary of progress during a stage.

Continued Business Justification requires that the Business Case remains valid throughout the project.

The Benefits Management Approach is created during the Initiating a Project process as part of the PID.

According to PRINCE2, when a team manager raises a technical difficulty that could result in a change, the project manager must first log it as an issue in the Issue Register. Only after logging and assessing the impact can the project manager decide on the appropriate response. Since the change does not affect the stage plan or business case, the project manager can handle it within the stage without escalating to the project board.

The Project Board authorizes the project, initiation, stage plans, and closure. Authorization is a key output of DP.

In PRINCE2, management stages are defined by key decision points and major risks, not by arbitrary time intervals. The project board uses stage boundaries to reassess business justification, approve continued investment, and control exposure to risk. Therefore, the primary factor is where significant risks or decisions are anticipated, as this aligns with the PRINCE2 principle of managing by stages.

The End Project Report is produced during Closing a Project (CP) to summarize project performance and confirm closure.

Directing a Project (DP) is the process that covers the Project Board's activities from start to finish, including authorizing stages and closure.

The Project Manager is responsible for day-to-day management, including preparing Highlight Reports for the Project Board and managing stage boundaries. Project Assurance is independent, and the Project Board defines tolerances.

Separation ensures independence and objectivity in assurance, preventing conflicts of interest where the PM would be checking their own work.

Managing a Stage Boundary (SB) is the process where the PM plans the next stage and produces an End Stage Report.

The Team Manager reports progress to the Project Manager via Checkpoint Reports.

The Project Board is the decision-making body of a PRINCE2 project, and its mandatory roles are the Executive, Senior User, and Senior Supplier. The Senior User (Option C) is correct because they represent the interests of those who will use the project's outputs and are responsible for specifying requirements and ensuring the project delivers the expected benefits. The Executive (Option D) is correct as they own the business case and have ultimate authority over the project.

The risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate.

Project Assurance provides independent oversight and is accountable to the Project Board. Project Support provides administrative services to the Project Manager.

Project Assurance provides independent oversight, reporting to the Project Board, and cannot be delegated to the Project Manager.

The Starting Up a Project (SU) process occurs before the project is formally initiated, focusing on verifying the project's viability and creating the Project Brief. The Initiating a Project (IP) process then establishes the project's foundations by creating the Project Initiation Documentation (PID), which includes detailed plans and controls. Thus, the key difference is that SU is a pre-initiation process, while IP formally establishes the project's management foundation.

The Project Manager should assess the impact of the delay on the stage plan. If the deviation can be managed within stage tolerances, the PM will take corrective action. If tolerances are forecast to be exceeded, escalation is needed.

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

Option A is correct. Directing a Project is the process by which the Project Board provides ongoing direction and authorizes key decisions.

The risk owner is accountable for managing the risk and ensuring appropriate responses are implemented. The risk actionee performs the specific actions to respond to the risk.

In PRINCE2, the trigger for preparing an Exception Plan during the Managing a Stage Boundary process is the raising of an Exception Report. This report is created when the Project Manager forecasts that stage tolerances will be exceeded, indicating that the current Stage Plan cannot be completed within its agreed tolerances. The Exception Plan then replaces the existing Stage Plan to bring the project back within tolerance.

An RFC is a proposal for a change to a product that has been agreed as part of the baseline, while an Off-spec is something that should be provided by the project but currently is not or is forecast not to be.

The End Stage Report is produced in the Managing a Stage Boundary process, which reviews the current stage and plans the next. The report is sent to the Project Board for a decision.

IP produces the PID, which includes the Risk Management Approach and Communication Management Approach. The Project Brief is from SU, and the End Stage Report is from SB.

SU produces the Project Brief and the Stage Plan for the initiation stage. The Daily Log is also created but not a formal output. The PID is from IP.

The Project Initiation Documentation (PID) is the key output of Initiating a Project and defines the project's approach, controls, and plans.

Option B is correct. Project Assurance is an independent role that monitors project performance and compliance. Project Support provides administrative support.

The risk owner is responsible for managing the risk and ensuring the response is implemented. The risk actionee is the person who carries out the response actions. The risk owner may delegate actions but retains accountability.

The three permanent roles on the Project Board are the Executive (SRO), Senior User, and Senior Supplier. The Project Manager is not a permanent member; they attend but are not on the Board.

The quality review technique specifies three roles: Presenter, Chair, and Reviewer. The Chair is responsible for managing the review meeting and ensuring it is effective and fair.

Starting Up a Project produces the Project Brief, initiation Stage Plan, and Daily Log. The Project Brief is a key output.

Closing a Project provides a controlled closure, ensuring that all products are handed over, the project is formally completed, and lessons are captured.

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

A Request for Change is a proposed modification, while an Off-specification is something that was required but not delivered.

The Project Board uses Directing a Project to give ad-hoc direction, including responding to exception reports.

In PRINCE2, the risk owner is the person accountable for the management and outcome of a specific risk, including ensuring that appropriate response actions are planned and executed. The risk actionee, by contrast, is the person assigned to carry out the specific response actions defined in the risk response plan. This distinction ensures clear accountability versus execution responsibility within the risk management process.

Option D is correct because in PRINCE2, a Request for Change (RFC) is a formal proposal to change a product, baseline, or agreed scope, while an Off-specification is a formal notification that a product or deliverable does not meet its specified requirements. The key distinction is that an RFC is a proactive suggestion for change, whereas an Off-specification is a reactive report of a deviation or failure against an agreed specification.

The Project Board is accountable for the project's success, provides unified direction, and includes the Executive, Senior User, and Senior Supplier. Option A is false because the Project Manager is not on the Board. Option E is false because the Board does not perform day-to-day management.

A Request for Change is a proposal for a modification to a product that has been approved or baselined. An Off-specification is a situation where a product is not meeting its specification. Both are issue types.

The Senior Responsible Owner (SRO) is accountable for the Business Case and ensures it remains viable throughout the project.

The Project Board is responsible for overall project governance, including authorizing expenditure beyond the delegated authority of the Project Manager. This ensures that financial control remains at the senior management level, preventing unauthorized spending that could jeopardize the project's budget.

Project Assurance is a PRINCE2 role that provides an independent, objective view of the project's progress, ensuring that it remains viable and compliant with the business case, quality standards, and risks. Option A is correct because the Project Assurance role must be independent of the Project Manager to avoid conflicts of interest and provide unbiased oversight to the Project Board.

In PRINCE2, the Team Manager is responsible for delivering the work package and reports to the Project Manager on progress, issues, and risks. The Project Manager (Sarah Lee) is the single point of contact for the Team Manager within the project management team. Therefore, any potential delay must be reported to the Project Manager, who will then escalate to the Project Board if necessary.

The Managing a Stage Boundary process is triggered at the end of each stage (except the final stage) to plan the next stage and produce an End Stage Report.

Option A is correct because the defect in version 2.1 of the User Authentication Module is a new issue that must be formally logged and managed within the current stage. PRINCE2 requires that all issues (including defects) be captured in the Issue Register and handled through the Controlling a Stage process, which includes assessing the impact, deciding on corrective action, and updating the Configuration Item Record (CIR) accordingly. The baseline remains 2.0 because version 2.1 is still under development and has not been baselined, so the defect does not trigger a baseline change request.

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 aspects of the project, while reporting any deviations that exceed the agreed tolerances to the Project Board.

The three types of issue are Request for Change, Off-specification, and Problem/Concern.

The Quality Review technique is a systematic review of a product to assess its conformance to quality criteria.

A Product Status Account provides information about the status of one or more products, including version, status, and location.

The project manager must escalate the issue to the project board because the stage tolerance for time is about to be exceeded. According to PRINCE2, when a forecast indicates that a stage will exceed its tolerances, the project manager must produce an Exception Report and submit it to the project board, which then decides on corrective action. This is a mandatory escalation step to maintain management by exception.