PRINCE2 Foundation (PRINCE2F) — Questions 601–675

In PRINCE2, the Team Manager works within the boundaries of an agreed Work Package and reports to the Project Manager, not directly to the Project Board. When a product cannot meet its quality criteria due to an unforeseen technical limitation, this is an issue that threatens the Work Package's tolerances and must be escalated to the Project Manager. The Project Manager then decides whether to resolve it at their level or escalate to the Project Board if project-level tolerances are threatened.

Managing a Stage Boundary reviews the completed stage and prepares for the next. Its activities include producing the End Stage Report, updating the Project Plan and Business Case, producing the next Stage Plan, and reporting stage end to the Project Board. Appointing the Project Manager, authorising work packages, and confirming end-of-project product handover belong to other processes.

Follow-on action recommendations are logged in the Quality Register so they remain visible and can be actioned, and any that affect agreed baselines are managed as Issues under change control. Rejecting the Work Package, escalating as an Exception, or only recording a lesson all fail to put the recommendation in the right place. The Controlling a Stage process expects the Project Manager to review returned work and route findings appropriately.

In PRINCE2, the Project Manager is responsible for maintaining the Business Case throughout the project. This includes monitoring the project's viability against the Business Case, updating it with actual costs and benefits, and escalating any deviations to the Project Board. The Project Manager ensures the Business Case remains a living document that reflects the current justification for the project.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports to inform the Project Manager about progress, status, and issues within a Work Package. Checkpoint Reports are the routine progress communication from the team level up to the project management level, typically at frequency defined in the Work Package's tolerances.

The Progress practice is used to monitor and compare actual achievements against planned performance, and to assess the impact of deviations. When a work package takes longer than expected, the project manager uses Progress to evaluate the effect on the schedule and decide whether to escalate to the project board. This aligns with PRINCE2's principle of managing by stages and using tolerances to control deviations.

The Highlight Report is a progress report that provides the Project Board with a summary of the project's status at a management stage level. According to PRINCE2, the Project Manager is responsible for producing the Highlight Report at intervals defined in the Communication Management Strategy, typically on a regular basis such as weekly or monthly.

Project Assurance provides an independent check on the project's progress and compliance, reporting to the Project Board.

The Project Initiation Documentation contains the project management team structure and role descriptions, which record the project's organization, the people filling PRINCE2 roles, and their responsibilities. This allows the Executive and Project Board to confirm that direction, management, and delivery responsibilities are clearly allocated.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process in PRINCE2. It consolidates the Business Case, Project Plan, project controls, and other baseline documents, and is used to gain project board approval to proceed. The PID is the primary deliverable that defines the project's baseline.

The End Stage Report is produced during Managing a Stage Boundary and provides a summary of the stage's performance against its tolerances, including progress, issues, and risks. It is used by the Project Board to assess whether the stage was successful and to decide on the next stage.

The 'Controlling a Stage' process is the day-to-day management of a stage by the Project Manager. It involves authorizing work packages, monitoring progress, dealing with issues, and reporting to the Project Board. This process ensures the stage stays on track and within tolerances.

The Project Initiation Documentation is the consolidated baseline assembled during Initiating a Project, combining the Project Plan, Business Case, benefits, risks, and control approaches. The Project Brief precedes it, a Stage Plan is a lower-level control document, and the End Project Report evaluates the project at closure. Only the Project Initiation Documentation serves as the single baseline for Board authorisation.

Management by Exception is the PRINCE2 principle that defines tolerances for each management level and empowers the level below to act autonomously within those tolerances, escalating only when a forecast breach occurs. This is precisely the mechanism by which the Project Board delegates decision-making to the Project Manager within agreed boundaries.

The Senior Supplier is the Project Board role accountable for the technical integrity of the project's products and for providing the necessary technical expertise. The other roles focus on user interests, independent assurance, or team-level production, and therefore do not satisfy the requirement for supplier-side technical accountability.

The Starting up a Project process ensures that the prerequisites for initiating a project are in place, starting with appointing key roles, then learning from past projects, building the team, developing the outline business case, and finally selecting the approach.

The Project Board is performing the 'Directing a Project' process because this process is specifically responsible for high-level decision-making and oversight, including reviewing End Stage Reports and next Stage Plans at stage boundaries. In PRINCE2, the Project Board authorizes the next stage and reviews progress through the 'Directing a Project' activities, such as 'Authorize a Stage or Exception Plan' and 'Give Ad Hoc Direction'. The other processes are operational and do not involve the Project Board's collective decision-making in this context.

The Project Manager authorizes work by issuing a Work Package to the Team Manager.

The Project Board is responsible for ensuring that project assurance is carried out independently of the Project Manager. Project assurance provides the board with confidence that the project is being run correctly, and independence is essential so that assurance is not compromised by the Project Manager's own interests. The board appoints assurance roles and ensures they have the authority and access needed.

Separating Project Manager from Project Assurance ensures objectivity and independence of assurance activities. The Project Manager is responsible for day-to-day management and cannot objectively assess their own work.

The Issue Register is the PRINCE2 document specifically designed to capture, track, and manage all requests for change, including off-specifications, problems, and concerns. Since the project is experiencing many changes due to evolving requirements, the Project Manager must log each change request in the Issue Register to ensure proper impact analysis, decision-making, and audit trail. This aligns with the PRINCE2 practice of managing issues and changes through a controlled process.

The business case in PRINCE2 includes the reasons why the project is needed and the expected benefits and dis-benefits. These elements are essential for justifying the project and for enabling the Project Board to make informed decisions about its continuation. Other components such as organization structure, communication plan, and risk management approach are documented elsewhere in the PID, not in the business case itself.

A project is a temporary organization created to deliver one or more business products according to an agreed Business Case. The finite lifespan and the defined products answer why the initiative cannot be treated as ongoing operational work. The other options describe practices or roles that may appear in projects but do not define them, so they do not justify a project approach.

In PRINCE2, an Off-specification is the correct record when a product fails to meet its agreed specification or quality criteria. The Project Manager logs this in the Issue Register as a type of issue, not a risk, change, or lesson, because the product already exists and does not conform to its defined requirements.

The Project Product Description is the management product that defines the project's final product, including its quality criteria and acceptance criteria. It is used to ensure that the project delivers what the user needs and that acceptance is based on agreed criteria. The other PID components address different aspects of the project.

The Highlight Report is provided by the Project Manager to the Project Board at the end of each reporting period to summarize progress.

The Business Case is the correct management product because it documents the justification for the project, including costs, benefits, and risks. A change in external regulations directly impacts the project's viability, which is a fundamental aspect of the Business Case. PRINCE2 requires the Business Case to be updated whenever there is a change that could affect the project's continued justification.

When the Business Case becomes unviable, the Project Manager must escalate to the Project Board, which is responsible for authorising the project. Requesting an early end to the Initiation Stage enables the Board to decide whether to proceed, change, or stop the project based on updated information.

In PRINCE2, the Project Board is collectively responsible for authorizing the initiation of a project. This decision is made during the 'Directing a Project' process, where the Project Board reviews the Project Brief and decides whether to proceed to the Initiation Stage. The Project Board's authority is derived from the corporate or programme management, but the actual authorization to initiate is a board-level responsibility.

The Project Board consists of three roles: the Executive (Senior Responsible Owner), Senior User(s), and Senior Supplier(s). In this question, the two roles from the Project Board that are listed are Senior User (Option A) and Executive (Option E). Team Manager, Project Manager, and Project Support are not Project Board roles.

In PRINCE2, the Checkpoint Report is the formal progress report provided by a Team Manager to the Project Manager on a regular basis. It details progress against the Work Package, including achievements, next steps, and any issues or risks, enabling the Project Manager to monitor work at the team level.

The Business Case practice is responsible for establishing and maintaining the justification for the project, including the link between objectives and expected benefits. During the Initiating a Project process, the Business Case must be refined to ensure that all benefits are clearly traceable to the project's objectives, as this alignment is critical for ongoing viability decisions. The project manager should use the Business Case practice to address this gap by updating the Business Case to explicitly map each benefit to a specific project objective.

The End Stage Report provides a summary of performance against the Stage Plan, which contains the stage's baselines and tolerances. The Project Manager uses the Stage Plan to compare actual versus planned performance, enabling the Project Board to decide whether to authorize the next stage.

Controlling a Stage covers the Project Manager's day-to-day management of a stage. Its activities include authorising Work Packages, monitoring and reporting progress, managing risks and issues, taking corrective action, and reporting through Highlight Reports. Appointing the Project Management Team and producing the Project Brief belong to Starting Up a Project, while the End Stage Report belongs to Managing a Stage Boundary.

The Team Manager should raise an Issue Report to the Project Manager (D). In PRINCE2, when a product fails quality inspection, it is considered an issue. The Team Manager is responsible for raising issues to the Project Manager, who will then decide on the appropriate action, such as requesting a change or exception.

The Product Description is the PRINCE2 management product that defines the quality criteria, quality methods, and acceptance methods for a specific product. It is created during the Initiating a Project process and is used to ensure that the product meets its required quality standards before it is approved.

In PRINCE2, the Project Board should meet at the end of each stage and when exceptions occur. This is because the Board is responsible for stage boundary decisions and for handling exceptions that threaten the project's tolerances. Regular meetings are not prescribed; the frequency is driven by stage boundaries and exception events.

The Benefits Management Approach is first produced during the Initiating a Project process. This document defines how the project will manage and measure benefits, and it is created as part of the project initiation documentation. It is later reviewed and updated at stage boundaries and used in Closing a Project to assess benefits realization.

The two PRINCE2 principles that focus on the project's justification and organizational structure are continued business justification and defined roles and responsibilities. Continued business justification ensures the project remains viable and aligned with business objectives, while defined roles and responsibilities establishes a clear organizational structure with accountability. These directly address the areas highlighted in the question.

Directing a Project is the process owned by the Project Board, running from project start to closure, where the Board makes key decisions such as authorizing initiation, authorizing the project, authorizing stage boundaries, giving ad hoc direction, and authorizing project closure. It is the only process in which the Project Board has decision-making authority; all other processes are the responsibility of the Project Manager or Team Manager.

In PRINCE2, the Project Manager receives Highlight Reports from Team Managers during the Controlling a Stage process. The Project Manager should review the report, update the Stage Plan with actual progress, and then produce the next Highlight Report for the Project Board. This ensures the Project Board is informed of progress and any issues.

The Quality Management Approach is the project-level document that defines the quality management system, including the verification and acceptance procedures and the responsibilities for carrying them out. The Quality Register logs quality activities, and Product Descriptions record individual product criteria, but only the Quality Management Approach describes how verification will be performed. The PID references it but does not itself define the approach.

During the Closing a Project process, the Lessons Report is produced to capture lessons learned for future projects. It summarizes the lessons from the Lessons Log and other sources, providing recommendations for future projects. The Lessons Report is included in the End Project Report or as a separate document, depending on the project's approach.

The Quality Management Approach describes the project's quality standards, quality criteria, quality methods (e.g., reviews, tests), roles and responsibilities for quality, and the tools and techniques to be used. It is the overarching document that defines how quality will be managed across the project, including the quality register and product descriptions.

Avoid is the correct risk response when the project team eliminates the threat entirely by changing the project approach — for example, removing a risky technology, changing scope, or taking a different route. In PRINCE2's risk response framework (aligned with ISO 31000), Avoid means the threat no longer exists because the activity or condition that created it has been removed. This is distinct from Reduce (mitigate), which lowers probability or impact but keeps the risk.

Team plans are created by the team manager during the Managing Product Delivery process.

In PRINCE2, the Team Manager produces a Checkpoint Report during the Managing Product Delivery process to inform the Project Manager of progress at a regular, predefined frequency. This report provides a snapshot of actual progress against the Work Package plan, including achievements, next steps, and any issues or risks. It is the primary mechanism for the Team Manager to communicate status to the Project Manager within this process.

The Team Manager is executing the 'Managing Product Delivery' process because this process controls the work of the team, including the creation and delivery of products. A key activity within this process is the production of Checkpoint Reports, which provide the Project Manager with progress updates on the work assigned to the team. The Checkpoint Report is a formal PRINCE2 management product that is specifically defined as an output of the 'Managing Product Delivery' process.

In PRINCE2, risk responses for opportunities (positive risks) include Enhance, Exploit, and Share. Enhance is the correct response because it involves proactively increasing the probability and/or impact of an opportunity to maximize its potential benefits. Transfer and Avoid are responses for threats (negative risks), while Fallback is a response for a threat when the primary response fails.

In PRINCE2, the Lessons Report is produced during Closing a Project and is explicitly intended to be shared with the wider organization so future projects can benefit from the experience. The correct destination is the organization's lessons database or equivalent repository, where it becomes part of corporate knowledge. Filing it away or restricting it defeats the purpose of the Lessons Learned practice.

PRINCE2 is tailorable to the project's context, and projects may sit within programmes that supply strategic context and benefits for the Business Case. Rigid application is contrary to the tailoring principle, the Executive rather than the Senior Supplier chairs the board and owns the Business Case, and standalone projects are permitted, so only the tailoring and programme-context statements are correct.

The clearest distinction is the primary output: Starting Up a Project (SU) produces the Project Brief, which justifies the project and defines the outline business case, while Initiating a Project (IP) produces the Project Initiation Documentation (PID), which contains the detailed business case, plans, controls, and strategies. SU is the pre-project gate; IP is the first stage of the actual project. This output-based distinction is the defining difference.

The 'managing a stage boundary' process provides the Project Board with a key decision point at the end of each management stage. It allows them to review the stage's performance, confirm the Business Case remains valid, and approve the next Stage Plan. This ensures the project is still viable and aligned with business objectives before further investment, which is essential when external suppliers are involved.

The Project Initiation Documentation (PID) is the definitive output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and Project Plan into a single, controlled document that defines the project's scope, objectives, and governance. PRINCE2 mandates that the PID is created and approved during this process to provide a firm foundation for the project.

In PRINCE2, the Project Board is the ultimate decision-making body responsible for approving key project documentation, including the Project Initiation Documentation (PID). The Project Manager prepares the PID, but it must be formally approved by the Project Board to authorize the project to proceed to the next stage. This ensures that the business case, risks, and plans are accepted at the appropriate governance level.

After the Project Board authorizes the project and the first stage, the Project Manager uses the Controlling a Stage process to assign work, monitor progress, handle issues, and report to the Board throughout the stage. This process governs the day-to-day management of the stage and ensures it stays within tolerance.

The Risk Management Strategy defines the project's approach to risk management, and the Change Control Approach defines the project's approach to change control. Both are management products within the Project Initiation Documentation and directly address the project board's request. The other products serve different purposes and do not define these management approaches.

The Highlight Report is a progress report produced by the Project Manager for the Project Board during the Controlling a Stage process. It is created at regular intervals (typically monthly or as defined in the Communication Management Strategy) to summarize stage progress, status, and any issues or risks. This is a core activity within Controlling a Stage, where the Project Manager monitors and reports on stage performance.

The Checkpoint Report is produced by the Team Manager during the Managing Product Delivery process. It provides the Project Manager with regular updates on the progress of a Work Package. The Team Manager is responsible for executing the Work Package and reporting progress via Checkpoint Reports.

In PRINCE2 the Project Manager is responsible for maintaining the Business Case throughout the project, updating it at each stage boundary and whenever a change or exception affects justification. The Executive owns and is accountable for the Business Case, but the day-to-day maintenance is delegated to the Project Manager.

In PRINCE2, the End Project Report is a key management product that provides a summary of the project's performance and is used to gain approval to close the project. The Project Board is responsible for approving this report because it holds the ultimate decision-making authority and accountability for the project's outcomes. The Project Manager prepares the report, but the Board approves it.

Project Assurance is a role defined in PRINCE2, responsible for ensuring the project remains viable and compliant with its business justification, while a quality review is a technique used to assess the quality of a product or deliverable. The key difference is that Project Assurance is an ongoing role performed by individuals independent of the Project Manager, whereas a quality review is a specific, time-boxed event or technique for inspecting deliverables. Option A correctly identifies this fundamental distinction between a role and a technique.

The Business Case is the single PRINCE2 product that captures the justification for the project, including costs, benefits, risks, and the investment appraisal. When external criteria change, the project manager must reassess that justification and provide the board with enough information to decide whether to continue, change, or stop the project. Other products do not contain the required viability information.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It consolidates the business case, project plan, risk register, and other baselines, and is approved by the Project Board to authorize the project. The PID provides the baseline against which the project's progress and performance are measured.

Tailoring is the PRINCE2 principle that requires the project management approach to be adapted to the project's size, complexity, and environment. For a globally dispersed team, tailoring communication methods, meeting schedules, and collaboration tools ensures that the team can work effectively together. The other principles address governance, product focus, and learning, but not the specific need to adapt to the team's context.

When a project is forecast to exceed its cost tolerance at the project level, the Project Manager must first escalate the deviation to the Project Board by raising an Exception Report. This is because the Project Board holds the authority to approve changes to tolerances or authorize corrective actions, and the Project Manager cannot unilaterally revise the plan or close the project. The Exception Report provides the Board with the necessary information to make an informed decision on how to proceed.

The Team Manager is responsible for managing the team on a day-to-day basis and ensuring that products are produced to the required quality criteria. These responsibilities are defined in the Work Package and are essential for the successful delivery of the project's products.