PRINCE2 Foundation (PRINCE2F) — Questions 301–375

Any off-specification must be formally documented as an issue. The team should not have implemented a workaround without approval. The Project Manager should raise an Issue Report and investigate the impact.

The End Stage Report provides the current stage's performance, which feeds into the Business Case update. The Benefits Management Approach and other documents are also considered, but the End Stage Report is key for performance data.

The Project Board uses the Directing a Project process to authorise closure, based on the recommendation from CP.

Independence ensures objective oversight, reduces conflict of interest, and helps identify issues early. It does not speed up decisions (that may be slower) nor reduce costs (it adds overhead).

When stage tolerances are forecast to be exceeded, the Project Manager raises an Exception Report and the Managing a Stage Boundary process is used to plan the response. The Project Board may approve an Exception Plan via this process.

The Executive is the single person accountable for the project and has the authority to authorize the initiation stage. According to PRINCE2, only the Executive can give the approval to proceed from the Starting Up a Project process to the Initiation Stage, as they own the business case and are responsible for the project's overall justification.

The Project Board is the PRINCE2 management layer responsible for overall project direction and key decision-making. The Senior User is a mandatory Project Board role representing the interests of those who will use the project's products, ensuring the project delivers the required benefits. The Executive is also a mandatory Project Board role, acting as the project's ultimate decision-maker and owner of the business case.

The Change Authority in PRINCE2 is a role that is delegated by the Project Board to approve requests for change within a specific, agreed-upon limit (e.g., cost or time). This allows for efficient decision-making without requiring the full Project Board to convene for every minor change, while still maintaining control over the project's scope and budget.

Checkpoint Reports are prepared by the Team Manager and sent to the Project Manager as part of Managing Product Delivery. They inform the Project Manager of progress on Work Packages.

Option C is correct because PRINCE2's Communication Management Strategy is the formal mechanism for defining roles, responsibilities, and information flows. By revisiting it, the Project Manager can clarify the business analysts' and developers' roles in decision-making and requirements specification, directly addressing the root cause of misunderstandings. This aligns with the 'Manage by Stages' and 'Defined Roles and Responsibilities' principles, ensuring the team collaborates effectively without unnecessary escalation or personnel changes.

The Business Case is part of the Project Initiation Documentation because it provides the justification for the project and is developed during the Initiating a Project process. The Project Plan is also part of the PID as it defines the project-level plan, including costs, timescales, and controls, and is created during initiation. Both are mandatory components of the PID as per PRINCE2.

PRINCE2 defines three types of issue: Request for Change (RFC), Off-specification (Off-spec), and Problem/Concern. Risk is a separate concept.

The Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. Major risks and expected benefits are two of these.

The Project Manager produces the End Stage Report during the Managing a Stage Boundary process.

The Team Manager is responsible for the delivery of one or more Work Packages and reports to the Project Manager.

The Project Manager is responsible for maintaining the Business Case on a day-to-day basis, while the Executive (SRO) owns it and is ultimately accountable for its justification.

In PRINCE2, the Project Board is a decision-making body that manages by exception. It does not meet on a fixed schedule like weekly or daily; instead, it convenes only when a deviation from the plan (an exception) requires its intervention, such as when a stage plan exceeds tolerance levels. This exception-driven approach ensures the Board focuses on strategic oversight rather than operational details.

The Project Initiation Documentation (PID) is the definitive document that defines the project's organization structure and roles, including the project management team structure, role descriptions, and responsibilities. It is created during the Initiating a Project process and provides a baseline for how the project will be managed and controlled.

The Initiating a Project process is where the project's foundations are solidified, and its key output is the Project Initiation Documentation (PID). The PID consolidates all the planning and analysis from the initiation stage into a single, comprehensive document that defines the project's scope, objectives, business justification, risks, and management controls, serving as the baseline for the project board's authorization to proceed.

The Project Manager (PM) maintains the Business Case on a day-to-day basis, but the Executive owns it and is accountable for it. The PM ensures it is updated and reviewed.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two recognized types of issue are 'Off-specification' (something that should be provided but is not) and 'Request for Change' (a proposal for a change to a product's specification). These are formally defined in the PRINCE2 manual as the only issue types.

The End Stage Report is sent to the Project Board, who then decides whether to authorize the next stage (or, if the project is in the final stage, to close the project).

The Project Manager is responsible for producing and maintaining the Project Plan, as defined in PRINCE2's management products. This includes defining the project's stages, activities, dependencies, and resource estimates, and ensuring the plan aligns with the Business Case. The Project Manager owns the planning process and is accountable for the plan's accuracy and updates throughout the project.

In SB, the PM produces the End Stage Report, updates the Project Plan, and produces a Stage Plan for the next stage. Authorizing work packages is done in CS. Producing Highlight Reports is done in CS.

The separation ensures independent oversight. The Project Manager is responsible for day-to-day management, while Project Assurance provides an impartial view to the Project Board to avoid conflicts of interest.

A Highlight Report is sent from the Project Manager to the Project Board regularly, while a Checkpoint Report is sent from the Team Manager to the Project Manager more frequently.

PRINCE2 provides a common language and improves communication, and it ensures a focus on business justification through the Business Case. It does not eliminate the need for project managers nor guarantee successful delivery.

The End Stage Report in PRINCE2 serves a dual purpose: it summarizes the current stage's performance against the plan and requests authorization to proceed to the next stage. This aligns with the PRINCE2 principle of managing by stages, where each stage ends with a formal review and decision point. The report provides the Project Board with the necessary information to approve continued investment.

When an Exception Plan is approved, the project moves to a new stage, and the Managing a Stage Boundary process is used to set up the new stage.

Managing Product Delivery involves accepting the work package, executing the work, delivering the products, obtaining approval, and then reporting completion.

An RFC is a proposal for a modification (change) to the project's products, while an Off-specification is a situation where a product does not meet its specification (a deviation).

Manage by stages is the most important principle because it requires the project to be planned, monitored, and controlled in discrete stages, with each stage authorizing the next only after a formal review. In a highly regulated environment, this creates clear, auditable decision points (e.g., stage boundary approvals) that external auditors can trace. The project manager can document stage plans, exception reports, and end-stage assessments as explicit evidence of governance.

The Risk practice in PRINCE2 is specifically designed to identify, assess, and control uncertainties that could affect the project's objectives. During the initiation stage, the project manager applies this practice to systematically identify major risks, evaluate their probability and impact, and plan appropriate responses, ensuring proactive management of threats and opportunities.

The Starting up a Project (SU) process in PRINCE2 is the pre-project phase where the project is evaluated before any detailed planning begins. During SU, the Project Brief is created to outline the project's scope, objectives, and approach, and the Business Case is developed at a high level to justify the project's viability. Both documents are essential for the Project Board to decide whether to proceed to the Initiation Stage.

Project Assurance is an independent check that the project is running correctly, while Project Support provides administrative services.

The Business Case is the document that justifies the project by providing the justification, costs, benefits, and risks. During the initiation stage, the project manager develops the Business Case to confirm that the project is viable and aligns with corporate objectives. The Project Board then reviews and approves it to authorize the project to proceed.

The risk owner is accountable for managing the risk, while the risk actionee carries out specific actions to respond to the risk.

According to PRINCE2's management by exception principle, the Project Manager must escalate to the Project Board via an Exception Report when a tolerance is forecast to be exceeded.

The Project Board authorizes Exception Plans during the Directing a Project process, which includes decisions on stage plans and exceptions.

Directing a Project includes authorizing initiation, authorizing stages, giving ad-hoc direction, and authorizing closure. Producing Highlight Reports is for the PM during Controlling a Stage. Appointing the Project Manager is during Starting Up a Project.

The Business Case includes reasons, expected benefits, costs, timescale, etc.

The seven PRINCE2 principles are these five plus 'Focus on Products' and 'Tailor to Suit the Project Environment'.

Project Assurance is the Project Board's responsibility, but it can be delegated to individuals or teams independent of the Project Manager.

The Product Flow Diagram shows the order in which products will be developed and the dependencies between them, which helps in planning the sequence of activities.

Option A is correct. The Lessons Report is produced in CP to document lessons learned for future benefit.

The Project Board uses the Directing a Project process throughout the project, including authorising closure. Closing a Project is the process that produces the recommendation, but the decision to close is taken by the Project Board via Directing a Project.

Project Assurance is independent of the Project Manager and provides objective oversight, while Project Support provides administrative and planning support to the Project Manager.

The Team Manager is responsible for delivering one or more Work Packages as defined in the Stage Plan. This role focuses on the technical delivery of products within the constraints agreed with the Project Manager, ensuring quality, time, and cost targets are met for those specific work packages.

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

A Request for Change is a proposal for a change that would modify agreed baselines or requirements. An Off-specification is something that should be provided but is not currently present (or is incorrect).

The Project Board is responsible for approving the PID, monitoring progress via Highlight Reports, and providing resources. Options B, C, and D are correct.

The Team Manager produces Checkpoint Reports to inform the Project Manager of progress within a Work Package.

SU is a pre-project process to decide whether to initiate; IP formally establishes the project with detailed planning and PID.

The Project Initiation Documentation (PID) is the key output of IP. It provides the foundation for the project.

Option B is correct because Project Assurance is an independent oversight function, performed on behalf of the Project Board, to ensure that the project is being conducted correctly and remains viable. Project Support, in contrast, is a set of administrative and advisory services provided to the Project Manager to help them manage the project effectively. This distinction is fundamental to PRINCE2's separation of 'doing' from 'checking'.

The PBS provides a hierarchical decomposition of all products to be created, showing their relationships.

The Business Case includes: reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The Quality Register is a separate document used for tracking quality activities.

Option A is correct because the Project Board is responsible for authorizing the movement from one stage to the next, which includes approving the Stage Plan for the next stage and reviewing the current stage's completion. This is a key control point in PRINCE2's stage-gate management approach, ensuring that the project only proceeds when the Board is satisfied with progress and the business case remains viable.

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager as part of Managing Product Delivery.

Project Assurance is a role within the PRINCE2 management structure, responsible for ensuring that the project remains viable and compliant with the business case, while a quality review is a technique used to assess the quality of a product. Option D correctly distinguishes between these two concepts: Project Assurance is a role, and quality review is a technique. This aligns with PRINCE2's separation of management responsibilities from quality control activities.

The End Stage Report is produced during the Managing a Stage Boundary process to summarize the current stage's performance and inform the Project Board's decision to authorize the next stage.

The Initiating a Project process is where the project's scope, objectives, and approach are fully defined and documented. Its key output is the Project Initiation Documentation (PID), which consolidates all the baseline plans and strategies needed to justify and manage the project. The PID replaces the Project Brief, which is created earlier in the Starting Up a Project process.

When a work package tolerance is forecast to be exceeded, the team manager should inform the Project Manager via a Checkpoint Report so the PM can assess impact.

When the Project Board authorizes a stage plan, the next process to execute is Controlling a Stage, where the Project Manager manages the work of that stage.

The Project Manager maintains the Business Case on behalf of the Executive, who owns it.

Option A is correct because the Starting Up a Project (SU) process is designed to evaluate the project's viability by creating the Project Brief and checking if the project is worthwhile, while the Initiating a Project (IP) process focuses on establishing a solid management foundation by creating the Project Initiation Documentation (PID) and detailed plans for how the project will be managed and controlled.

The three issue types are: Request for Change, Off-specification, and Problem/Concern. Options A and B are correct. Options C, D, and E are not official issue types.

The Project Board, through the Directing a Project process, authorises initiation, the project itself, stage plans, and closure. The Project Manager recommends but does not authorise. The Senior User and Senior Supplier are members of the Project Board.

The Team Manager must escalate the issue to the Project Manager promptly, as they cannot exceed Work Package tolerances without authorization. The Project Manager will then handle the escalation.

The Project Manager manages day-to-day activities, produces Highlight Reports for the board, and updates the Business Case as needed. The PM does not chair the board or perform assurance.