PRINCE2 Foundation (PRINCE2F) — Questions 751–825

Learn from Experience means seeking lessons from previous projects during initiation, maintaining a lessons log, and updating it throughout the project. Lessons should be applied at each stage boundary and used to improve the current project as well as future ones.

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

The PRINCE2 project management team structure includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optionally the Change Authority. The Project Sponsor is not a defined role in PRINCE2; instead, the Executive role fulfills the sponsorship responsibilities. Therefore, option A is correct as the role that does NOT exist in the PRINCE2 framework.

In PRINCE2, the risk actionee is the person responsible for implementing the risk response actions as defined in the risk response plan. The risk owner owns the risk and oversees the response, but the actual implementation is delegated to the risk actionee. This separation ensures clear accountability for execution versus ownership.

D is correct because PRINCE2 is explicitly defined as an integrated framework consisting of four core elements: principles, practices (formerly themes), processes, and tailoring. These four components are interwoven throughout the methodology, ensuring that every project applies the principles via the practices and processes, adapted through tailoring to the specific project environment. The PRINCE2 Foundation syllabus and official manual (Managing Successful Projects with PRINCE2) state that these four elements are the integrated building blocks of the method.

Directing a Project is the process owned by the Project Board that authorizes the project to proceed through each stage boundary, including authorizing initiation. The Project Board's 'authorize initiation' decision is made within Directing a Project, which then triggers Initiating a Project to begin.

Project Assurance is independent of the Project Manager and provides assurance to the Project Board that the project is being managed correctly and remains viable.

The Change Control Approach includes the scale of changes that require Project Board approval and the format and use of the Issue Register. These components define how changes are governed and recorded. Quality criteria, quality assurance roles, and risk tolerances belong to other strategies or documents, such as Product Descriptions, the Quality Management Strategy, and the Risk Management Approach.

The quality register is the PRINCE2 management product used to record all planned and completed quality activities, including quality inspections and test results. It provides a log of quality events throughout the project lifecycle, enabling traceability and auditability of quality efforts.

A Product Description is the document that defines a product's purpose, composition, derivation, quality criteria, and quality method. It is the reference for quality control activities on that specific product, so it is where the quality criteria for a product are documented.

The product-based planning approach in PRINCE2 ensures that the project's outputs (products) and their quality criteria are defined before planning the activities and dependencies. This prevents scope creep and rework by establishing clear acceptance standards upfront, aligning with PRINCE2's focus on management by product.

When an issue is forecast to exceed stage-level tolerance, PRINCE2 requires the Project Manager to raise an Exception Report and escalate to the Project Board, because tolerances are the delegated authority limits. The Board then decides whether to approve an Exception Plan, change the project, or stop it. This preserves the principle of Management by Exception.

The Project Plan is created during the Initiating a Project (IP) process and provides a high-level view of the entire project, including the project's scope, cost, timeline, and major deliverables. It is derived from the Project Brief and serves as the baseline against which the project's progress is measured. Because it covers the whole project at a high level, it is the correct answer.

In PRINCE2, threat response types are specific strategies for dealing with negative risks (threats). 'Avoid' (Option A) is a valid threat response that involves changing the plan to eliminate the threat or protect the project from its impact. 'Transfer' (Option C) shifts the financial impact of a threat to a third party, such as through insurance or a fixed-price contract. 'Accept' (Option E) acknowledges the threat and takes no proactive action, often with a contingency plan in place. These three are explicitly listed in the PRINCE2 risk management practice.

In PRINCE2, the project board is accountable for the overall success of the project. Its responsibilities include approving the project initiation documentation, which authorizes the project to proceed, and authorizing the closure of the project after verifying that objectives have been met. The board does not manage day-to-day activities, create detailed plans, or directly ensure benefits delivery; those are delegated to the project manager and other roles.

Project Assurance is a PRINCE2 role that provides independent oversight of the project on behalf of the Project Board. To ensure independence from the Project Manager, it must be performed by Project Board members or their delegates, who are not part of the project management team and can objectively assess the project's performance and compliance.

The Executive (Senior Responsible Owner, SRO) is the role accountable for the Business Case throughout the project in PRINCE2. This accountability includes ensuring that the Business Case remains viable and aligned with corporate objectives, and that the project continues to justify its investment. The Executive owns the Business Case from initiation through to project closure, making the final decision on whether to proceed based on its continued viability.

Project Assurance is the independent check that the project is being managed correctly, as defined in PRINCE2. It is a role separate from the Project Manager and Team Manager, ensuring that the project remains viable and compliant with the organization's policies and standards. The Project Board delegates this responsibility to Project Assurance, which provides objective oversight throughout the project lifecycle.

A Checkpoint Report is produced by the Team Manager and given to the Project Manager at the frequency defined in the Work Package. It reports progress, status, and any issues against the Work Package, enabling the Project Manager to monitor the stage. It is the standard mechanism for Team Manager-to-Project Manager progress communication.

The Business Case is the PID component that justifies the project by outlining expected benefits, costs, risks, and timescales. It is specifically designed to support the Project Board's decision to authorise the project. While other components like the Project Plan and management approaches provide supporting information, they do not offer the consolidated justification that the Board requires.

The Project Board is accountable for project success and approves the Project Initiation Documentation. It does not include the Project Manager, does not delegate all management, and is never optional. These responsibilities ensure proper governance and alignment with the Business Case.

The Project Manager must first manage the Work Package deviation within the stage tolerance. If corrective action cannot keep the stage within its tolerance, the Project Manager must escalate to the project board with an Exception Report, as the stage is in exception. Immediate escalation without corrective action or unilateral plan changes are not appropriate.

The investment appraisal must compare the project's costs and benefits against the 'do nothing' option to justify the investment. In this scenario, the cloud migration project must demonstrate that the benefits, such as cost savings and agility, outweigh the costs and risks compared to maintaining the legacy system.

The Project Brief is the primary output of the Starting up a Project process. It contains the outline business case, project definition, and project approach, providing enough information for the Project Board to decide whether to initiate the project. The other documents are outputs of later processes.

In PRINCE2, the Managing a Stage Boundary process requires the Project Manager to produce the End Stage Report and the next Stage Plan (B). These are the core outputs reviewed by the Project Board to authorize the next stage. The End Stage Report summarizes performance, and the Stage Plan details the next stage.

In PRINCE2, the Controlling a Stage process is responsible for authorizing Work Packages. This process manages the day-to-day activities within a stage, including assigning work to teams and ensuring it is completed according to the agreed tolerances. The Project Manager uses this process to issue Work Packages to the team manager or team members, formally delegating the work defined in the Stage Plan.

The 'Defined roles and responsibilities' principle ensures a clear organisational structure with accountable roles, while 'Manage by exception' establishes tolerances and delegates authority to appropriate levels. Together, they provide the framework for decision-making at the right level and clear accountability, which the project manager is emphasising.

The Organising practice defines the project management team structure, roles, and responsibilities, including the project board, project manager, and team manager roles. It establishes the project's organizational hierarchy and accountability lines, ensuring clear authority and communication paths.

The End Stage Report is produced during the Managing a Stage Boundary process to provide a formal summary of the stage's actual performance against the approved Stage Plan. Its primary purpose is to give the Project Board the information needed to review the completed stage and decide whether to authorize the next stage, including updated Business Case and project plan information. Option D correctly captures this dual purpose of reporting on the completed stage and seeking approval to proceed.

The Executive is accountable for the business case but may delegate day-to-day monitoring to Project Assurance. This role independently checks that the project remains aligned with the business case and that the project is on track to deliver the intended benefits. Project Assurance provides the continuous oversight the Executive cannot provide due to limited availability, ensuring the project stays on course.

The Business Case is the PRINCE2 document that justifies the project on economic grounds, and it must contain clearly defined benefits to enable ongoing viability assessment. If benefits are not clearly defined, the Business Case itself is incomplete and must be updated to ensure the project remains justified and aligned with organizational objectives.

The Executive is the single individual on the Project Board who has ultimate accountability for the project's business justification. They own the Business Case and must ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Project Manager manages the day-to-day work but does not own the Business Case; the Executive alone is responsible for its ongoing viability.

Separation ensures independence of assurance, preventing the Project Manager from making biased assessments of their own work.

Checkpoint Reports are produced by the Team Manager and provided to the Project Manager at a frequency defined in the Work Package, covering progress, issues, and next steps for that work package. Highlight Reports are produced by the Project Manager for the Project Board at a frequency defined in the Communication Management Strategy, summarizing stage progress, status, and any exceptions. This distinction in producer and audience is the core difference.

The Senior Supplier is the Project Board role accountable for the technical integrity of the project. They ensure that the supplier's proposed solution is feasible and that technical risks are understood and managed, providing confidence to the Project Board that the project can deliver the required products.

The project is taking proactive action to increase the probability of a positive opportunity (cost reduction via new technology). In PRINCE2, the 'Enhance' response is specifically used to increase the likelihood and/or impact of an opportunity. By allocating additional resources to boost the chance of the technology succeeding, the Project Manager is applying the Enhance response, not Exploit (which would assume the opportunity is already certain and seeks to maximize its benefits).

The Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress information on the work package assigned to the team, including achievements, next steps, and any issues or risks. This aligns with PRINCE2's principle of management by exception, where the Team Manager reports at intervals defined in the Work Package.

In PRINCE2, the Senior User is accountable for ensuring that the project's products will deliver the benefits defined in the Business Case. This role represents the user community and is responsible for specifying user needs and confirming that the solution meets those needs and realizes the expected benefits.

Continued business justification is the PRINCE2 principle that requires the project's business case to be reviewed and re-validated at every stage boundary and whenever a major change occurs. It ensures the project remains aligned with the organization's objectives and that the benefits still outweigh the costs and risks. If justification is lost, PRINCE2 mandates that the project be stopped rather than continued by inertia.

The Exception Plan is produced during the Managing a Stage Boundary process because this process is triggered when a stage is forecast to exceed its tolerances. The Project Manager creates the Exception Plan to replace the current Stage Plan and submit it to the Project Board for approval, ensuring continued control over the project.

The Project Board is responsible for ensuring that project assurance is independent of the Project Manager. This is because the Project Board provides overall governance and oversight, and project assurance is a key function that must be objective and separate from the day-to-day management activities of the Project Manager. The PRINCE2 principle of 'defined roles and responsibilities' explicitly assigns this accountability to the Project Board to maintain the integrity of the assurance function.

The Starting Up a Project (SU) process is the pre-project activity that produces the Project Brief, which defines the project's rationale, scope, and approach at a high level. The Initiating a Project (IP) process then takes that brief and produces the Project Initiation Documentation (PID), which includes the detailed Business Case, plans, controls, and role descriptions. The distinction is one of scope and timing: SU sets up the project, IP formally authorizes and plans it.

Controlling a Stage is the process where the Project Manager monitors work, handles issues, and escalates exceptions to the Project Board when tolerances are forecast to be exceeded. Escalating an exception is a core activity within Controlling a Stage, which triggers the Project Board via the 'Directing a Project' process through an Exception Report. The Project Manager owns this escalation activity within the Controlling a Stage process.

The Project Initiation Documentation is the key management product used by the project board at the end of the Initiation Stage to decide whether to authorize the next stage. It contains the business case, project plan, and other elements that provide the necessary information for the decision. Other reports like the End Stage Report or Highlight Report serve different purposes and are not the primary basis for this authorization.

The key difference is that Starting Up a Project (SU) is a pre-project process that occurs before the project is formally initiated, focusing on creating the Project Brief and appointing the Executive and Project Manager. Initiating a Project (IP) is the first process after the project is authorized, where the detailed Project Plan, Business Case, and Risk Register are developed, and the Project Initiation Documentation (PID) is created to establish the project baseline. Thus, SU sets the stage for IP, while IP formalizes the project's foundation.

The Project Brief is a high-level document that includes a summary of high-level risks and any known constraints. This gives the project board an early indication of potential challenges and supports the decision to proceed to the Initiating a Project process. Detailed risk management information, such as the risk management strategy or risk tolerance thresholds, is developed later.

The End Project Report is produced during Closing a Project and provides the Project Board with confirmation that the project has delivered what was expected, including a review of the Project Initiation Documentation and the Business Case. It summarizes performance against the project's baselines and confirms acceptance of the project product. This report is the formal mechanism for verifying delivery against expectations.

The Quality practice in PRINCE2 provides the guidance for defining the project's outputs and acceptance criteria. It ensures that the project product description includes the quality criteria, quality methods, and acceptance criteria that the product must meet to be accepted by the customer. This practice directly addresses how to specify and verify the project's deliverables.

The risk register is a PRINCE2 management product that formally records all identified risks, their status, and related information throughout the project. It is created during the Initiating a Project process and maintained as risks are identified, assessed, and responded to.

The Project Board is accountable for ensuring the project aligns with organisational policies and for approving key management products, including the communication management approach. These responsibilities ensure stakeholder engagement is planned and governed effectively. Operational tasks such as conducting interviews, maintaining the stakeholder register, and scheduling team meetings are delegated to the Project Manager or other team members.

During the Managing a Stage Boundary process, the Project Manager must update the Project Plan with actuals and forecasts to reflect the current stage's performance and provide a basis for planning the next stage. This ensures the Project Board has accurate information to authorize the next stage or take corrective action.

The Business Case must be updated whenever there are changes that affect its viability, such as increased costs. The Project Manager should reassess the justification and update the Business Case to ensure it remains accurate. This supports the continued viability of the project and informs the Project Board's decisions.

The Project Board authorizes the project to proceed with the initiation stage during the 'Directing a Project' process. This process covers the Project Board's decision-making responsibilities, including giving the authorization to start the initiation stage after reviewing the Project Brief and the Stage Plan for initiation. The specific management product used for this authorization is the 'Project Initiation Documentation' (PID) approval, but the decision itself is a key activity in the Directing a Project process.

The SB process provides the Project Board with information needed to review the current stage, approve the next stage Plan, and assess the continued viability of the project.

The Checkpoint Report is the correct product because it is specifically designed for the team manager to report progress on a work package to the project manager. It is a regular report that aligns with the Managing Product Delivery process. Other reports are used for different purposes and by different roles.

Closing a Project involves confirming that all products have been handed over, evaluating the project against its Business Case, and producing the End Project Report. These activities ensure the Project Board can confirm that the project's objectives have been met and that there are no outstanding issues before authorising closure.

The Executive is the single individual who owns the business case and is ultimately accountable for the project's justification. Throughout the project, the Executive must ensure that the business case remains viable, approving any changes that affect its justification. This is a core responsibility defined in the PRINCE2 Business Case theme.

The Directing a Project process is designed to enable the Project Board to make key decisions and exercise overall control over the project. It covers the board's responsibilities from project initiation through to closure, including authorizing the initiation, stage plans, and project closure, as well as providing ad hoc direction. This process does not involve detailed planning or day-to-day management, which are handled by other processes.

Transfer is the correct response because outsourcing shifts the ownership and financial/operational impact of the threat to a third party (e.g., a vendor, insurer, or outsourced provider). In PRINCE2 risk management, 'transfer' does not eliminate the threat — it moves the consequence to another party, typically via contract, insurance, or outsourcing agreement. This matches the scenario where the project decides to outsource the risky work.

Continued business justification is applied when the project manager ensures the project has a clear and agreed Business Case linked to the programme's benefits. This principle ensures the project remains aligned with strategic objectives and justifies its existence throughout its lifecycle, which is critical when the project is part of a larger programme.

The Team Manager executes the work and delivers the products within the Managing Product Delivery process. This process defines the interface between the Project Manager (who controls the stage) and the Team Manager (who accepts, executes, and delivers the Work Package). It contains the activities 'Accept a Work Package', 'Execute a Work Package', and 'Deliver a Work Package'.

PRINCE2 mandates clear, measurable project objectives through its Business Case and Project Product Description management products. Unclear objectives are a leading cause of project failure, as they prevent effective planning and control. PRINCE2's focus on continued business justification ensures objectives remain aligned with organizational goals.