PRINCE2 Foundation (PRINCE2F) — Questions 76–150

Product-based planning starts with identifying the products (outputs) required, i.e., creating a Product Breakdown Structure.

The Stage Plan is the detailed plan for each management stage, created at the end of the previous stage.

The End Project Report is produced during Closing a Project. It reviews the project's overall performance and confirms the project has met its objectives.

Project Assurance provides independent assessment of project issues, including impact on the Business Case, to the Project Board.

Closing a Project involves preparing closure, handing over products, evaluating, recommending closure, and then formally closing.

The Executive (Senior Responsible Owner) is accountable for the Business Case and ensuring the project remains justified.

A Highlight Report is from the Project Manager to the Project Board; a Checkpoint Report is from the Team Manager to the Project Manager.

In PRINCE2, the Project Initiation Documentation (PID) is the key deliverable of the Initiation Stage. The stage is not considered complete until the PID has been created and approved, as it provides the foundation for project governance and decision-making. The Business Case, Project Plan, and Risk Register are all components that are assembled into the PID, but the PID itself is the definitive document that marks stage completion.

The Team Manager is responsible for managing the delivery of one or more Work Packages as assigned by the Project Manager.

The End Stage Report provides the Project Board with information on the performance of the current stage so they can decide whether to authorize the next stage.

Since stage tolerances are not exceeded, the Project Manager can handle the deviation within the stage. Option A is correct.

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

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

An Exception Plan is created when the Project Board approves an Exception Report, i.e., when a tolerance is forecast to be exceeded.

In PRINCE2, the Project Board is not a day-to-day management body; it meets only when decisions are needed outside the delegated authority of the Project Manager. The correct frequency is exception-driven, meaning the Board convenes when a stage boundary is reached, an exception report is raised, or the project is ready for closure. This aligns with PRINCE2's principle of management by exception, where the Board's involvement is triggered by specific events rather than a fixed schedule.

The Business Case is the key driver for the project, and if a fundamental assumption is invalid, the project manager must first update the Business Case to reflect the new reality. This ensures that the project remains viable and that the Project Board can make an informed decision about whether to continue. Updating the Business Case is the correct first step because it provides the basis for any subsequent decisions, such as escalating to the Project Board.

The Project Manager maintains the Business Case on behalf of the Executive (Senior Responsible Owner). The Executive owns the Business Case and is accountable for the business justification, but the Project Manager is responsible for day-to-day maintenance.

Avoid and Transfer are valid threat responses. Enhance is for opportunities; Reject is for opportunities.

The Project Manager maintains the Business Case on behalf of the Executive. The Executive owns it and ensures it remains viable.

The Senior Responsible Owner (SRO/Executive) owns the Business Case and is responsible for ensuring it remains viable throughout the project.

The Team Manager is responsible for coordinating the team to deliver Work Packages as defined by the Project Manager.

The Team Manager manages the delivery of one or more Work Packages (A), reports to the Project Manager (B), and is an optional role (C). They do not manage the entire stage (D) and are not part of the Project Board (E).

SU produces the Project Brief, Stage Plan for initiation, and Daily Log. The PID is produced in IP, and the End Project Report is produced in CP.

Project Assurance is independent of the Project Manager and reports to the Project Board.

The Project Board is responsible for approving the Project Initiation Documentation (PID) because it represents the collective authority of the business, user, and supplier interests. The PID formally authorizes the initiation of the project and commits resources, so only the Project Board has the necessary authority to approve it.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, consolidating all the management approaches and plans.

The risk owner is accountable for managing the risk and ensuring appropriate responses are implemented; the risk actionee carries out specific actions.

The recommended risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate. So after Identify, the next step is Assess (evaluate probability and impact).

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

In PRINCE2, the Project Board is responsible for appointing the Project Manager. This is because the Project Board represents the business, user, and supplier interests and has the authority to delegate day-to-day management to the Project Manager. The Project Board's responsibility includes ensuring the right person is appointed to manage the project on their behalf.

The PRINCE2 issue types are Request for Change, Off-specification, and Problem/Concern. Threat and opportunity are risk types.

The Executive (SRO) chairs the Project Board and is accountable for the project's success.

The Project Manager is responsible for producing the Highlight Report in PRINCE2. This report provides the Project Board with a summary of progress against the stage plan, including achievements, next steps, and any issues or risks. It is a key management product defined in the PRINCE2 manual, and its production is a specific responsibility of the Project Manager, not delegated to the Team Manager or others.

Management by exception means that tolerances are delegated; if they are forecast to be exceeded, the issue is escalated to the next management level.

Reduce means taking action to lower the probability or impact of a threat to an acceptable level.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets the stated requirements and is suitable for its intended use, not necessarily the highest possible standard.

The Team Manager is responsible for delivering the Work Package as defined by the Project Manager.

A Request for Change is a proposal for a change to a product that is already baselined, while an Off-specification is something that should have been provided but was not, or is faulty.

The End Stage Report provides a summary of the current stage's performance and the next stage plan for the Board to decide on continuation.

The End Stage Report is a management product that provides a summary of the stage's performance against the plan. When an Exception Plan has been used, the End Stage Report must include a summary of the issue that triggered the exception and the impact of the Exception Plan on the stage's objectives, budget, and schedule. This ensures that the Project Board has a complete picture of the stage's actual performance, including any deviations from the original Stage Plan.

The Project Manager is responsible for day-to-day management and preparing the Project Plan. Options A and D are correct. Options B, C, and E are not PM responsibilities.

Managing a Stage Boundary is the process where the Project Manager prepares the next Stage Plan and updates the Business Case for approval by the Project Board.

Since stage tolerance is not threatened, the Project Manager can take corrective action within the delegated tolerances, such as re-planning or re-assigning resources, without escalating to the Project Board.

The Project Initiation Documentation (PID) is the definitive document created during the Initiating a Project process. It consolidates the project's scope, objectives, and management controls, serving as the foundation for project governance and decision-making. PRINCE2 mandates the PID to ensure all stakeholders have a single source of truth for how the project will be managed.

Directing a Project includes authorising initiation, authorising the project, authorising stage/exception plans, giving ad-hoc direction, and authorising closure. Authorising a Work Package is done by the Project Manager in Controlling a Stage. Highlight Reports are produced by the Project Manager in Controlling a Stage.

The PID contains the Project Plan, which is a high-level plan for the entire project. Stage Plans are created in SB, not IP (except the first stage plan).

Managing Product Delivery is the PRINCE2 process that focuses on the work required to create the project's products and ensures they are delivered according to the agreed quality criteria. It is the process where the team manager accepts work packages, executes the work, and delivers completed products that meet the defined quality standards.

The Quality Register records all planned quality activities and their results.

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

Starting up a Project produces the Project Brief and Stage Plan. The PID is produced in Initiating a Project.

In Controlling a Stage, the PM authorises Work Packages to Team Managers for execution.

The Executive and Project Manager are appointed during SU, along with the Project Board members. The Team Manager is appointed later.

Option D is correct because PRINCE2 mandates that when a project manager forecasts a deviation beyond the stage tolerance, they must escalate the issue to the Project Board via an Exception Report. The Project Board then decides whether to approve an exception plan, adjust tolerance, or close the project. This ensures governance and control over the project's budget and scope.

The Starting Up a Project (SU) process is the pre-project process where the Executive and Project Manager are appointed. This ensures the necessary roles are in place before the project is formally initiated.

The Executive (Senior Responsible Owner) is responsible for the Business Case. The Project Manager maintains it day-to-day, but the Executive owns it.

Option A is correct. The Project Plan is created during Initiating a Project. Stage Plans are created during Managing a Stage Boundary; Team Plans are created by the Team Manager; Exception Plans are created when tolerances are exceeded.

The seven processes are these five plus 'Managing a Stage Boundary' and 'Closing a Project'.

The Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks.

In PRINCE2, the Project Board is chaired by the Executive (also known as the Senior Responsible Owner in many organizations). The Executive is ultimately accountable for the project's success, provides business justification, and ensures the project remains viable. The chairperson role is explicitly assigned to the Executive in the PRINCE2 management structure, not to the Senior Supplier, Senior User, or Project Manager.

In PRINCE2, a Request for Change (RFC) is a formal proposal to change any baselined product, while an Off-specification (Off-spec) is a product that has been identified as not meeting its agreed specification. Option D correctly captures this distinction: an RFC seeks a change to an agreed product, whereas an Off-spec reports a deviation from the specification. This is a fundamental difference in issue handling within PRINCE2's change control approach.

A Work Package includes the product description(s) to be produced and the reporting requirements (e.g., Checkpoint Reports). The Business Case is not part of a Work Package; it is a project-level document. The team's composition is defined in the Project Plan, not in the Work Package.

The Senior Supplier is responsible for providing supplier resources, ensuring the quality of supplier deliverables, and advising on design and feasibility. The Senior Supplier does not define user acceptance criteria (that's the Senior User) nor manage the project budget (that's the SRO/Executive).

The Project Manager should assess the situation and decide whether to escalate based on tolerance. If it's within tolerance, they can approve corrective action.

The Executive (Senior Responsible Owner) is responsible for the Business Case. The Project Manager develops and maintains it, but ultimately the Executive owns it.

Option C is correct because the Project Manager is responsible for preparing the Stage Plan for approval by the Project Board. This is a key task in the PRINCE2 'Planning' process, where the Project Manager develops detailed plans for each management stage based on the Project Plan and stage-level tolerances.

The Highlight Report is a regular report from the Project Manager to the Project Board, providing a summary of progress and exceptions for the last reporting period.

The Project Board is responsible for authorizing the project, providing direction, and making key decisions. Option A (approve stage plans) and Option C (authorize deviations from stage tolerances) are Board responsibilities. Option B (manage Work Packages) is Team Manager; Option D (prepare Highlight Reports) is PM; Option E (maintain the Business Case) is PM with SRO accountability.

The Quality Register is a log of all planned quality checks and their results.

The Team Manager should raise an issue to the Project Manager, who then decides on the appropriate action (e.g., Request for Change or Off-specification).

The Project Brief is the key output of SU. The PID is produced during IP.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets its stated requirements and user needs, not necessarily perfection.

Managing a Stage Boundary provides the Project Board with information to approve the next stage, review the Business Case, and update the project plan.

In PRINCE2, the Team Manager is responsible for managing the delivery of Work Packages and reporting progress to the Project Manager. This role ensures that the products defined in the Work Package are created to the required quality, within time and cost constraints, and provides regular progress reports to the Project Manager.