PRINCE2 Foundation (PRINCE2F) — Questions 76–150

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.

Tailoring is the principle that allows PRINCE2 to be adapted to the specific needs of a project. By combining processes and reducing documentation, the project manager is applying tailoring to ensure the method is proportionate to the project's scale and risk. This is consistent with PRINCE2's flexibility, provided the principles are still met.

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 Work Package is the formal agreement authorising a Team Manager to produce defined products within agreed tolerances and reporting requirements. A Stage Plan operates at the management-stage level, a Team Plan is the Team Manager's own detailed plan, and a Product Description covers only a single product. Only the Work Package bundles the scope, tolerances, and reporting needed for delegated authorisation.

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

The principle of 'Manage by exception' is applied when the Project Manager escalates an issue that exceeds the stage tolerance. This principle establishes that each management level (e.g., Project Manager, Project Board) has defined tolerances (e.g., time, cost, quality) for their delegated authority; if a forecast or actual deviation goes beyond those tolerances, the issue must be escalated to the next management level for a decision. By escalating the out-of-tolerance issue, the Project Manager is following the exception-based control mechanism that is core to PRINCE2.

The Business Case within the Project Initiation Documentation directly supports the Continued Business Justification principle, which requires a project to have a valid and ongoing justification. It provides the rationale for the project and is reviewed at each stage boundary to ensure the project remains viable. Other principles like Manage by Stages or Learn from Experience are addressed through other elements of the PID.

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

The End Stage Report is produced at the end of each stage and summarizes performance against the stage plan, business case, and risks, giving the Project Board the information it needs to decide whether to authorize the next stage. It is the formal input to the 'Authorize a Stage' activity.

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.

In the Controlling a Stage process, the Project Manager is responsible for taking corrective action to keep the stage within its tolerances. Since the stage tolerance is not forecast to be exceeded, the issue remains within the Project Manager's delegated authority, so they should take corrective action without escalating. Escalation is only required when tolerances are forecast to be breached.

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.

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 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.

In PRINCE2, the Executive is the single individual on the Project Board ultimately accountable for the project's business case. The Executive owns the Business Case and is responsible for ensuring it remains viable throughout the project — monitoring benefits, costs, risks, and alignment with corporate strategy. If the business case ceases to be viable, the Executive can recommend project closure.

In PRINCE2, the Project Plan is produced during the Initiating a Project process. It provides the overall project timeline, costs, and resource requirements at the project level, and it is a key output of the Initiating a Project process along with the business case and project initiation documentation.

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.

Continued business justification is the PRINCE2 principle that requires a project to have a justifiable reason to start and to remain valid throughout. It is explicitly about the Business Case and the decision to continue, change, or stop the project. The other principles address control, learning, and tailoring, not the ongoing justification of the project.

The End Project Report includes a 'Review of Products' section that specifically documents the handover and acceptance of products. This section confirms that products meet their quality criteria and have been accepted by the customer or user, which directly addresses the project board's request for confirmation of handover and acceptance.

PRINCE2 allows the Team Manager and Project Support roles to be combined with the Project Manager role in appropriate circumstances, such as smaller projects. However, roles that require independence or represent different interests cannot be combined. Project Assurance must remain independent, and Project Board roles such as Senior User and Executive must be separate from the Project Manager to ensure proper governance and accountability.

In PRINCE2, during the Controlling a Stage process, the Project Manager is responsible for monitoring work and taking corrective action within the stage tolerances. If a Work Package is behind schedule but still within tolerance, the Project Manager should first review the situation and, if within tolerance, approve corrective action. This is part of the 'Take corrective action' activity.

The Business Case is the component of the Project Initiation Documentation that provides the business justification for the project. It captures the reasons, benefits, costs, risks, and timescales, and is reviewed throughout the project to confirm continued viability. The Project Plan, Benefits Review Plan, and Risk Management Approach support delivery and control but do not replace the Business Case.

Initiating a Project requires the Project Brief as its primary input. The Project Brief, produced in Starting Up a Project, contains the project definition, outline business case, and other foundational information needed to develop the Project Initiation Documentation. Other documents like End Stage Reports or Highlight Reports belong to later processes and are not available at this point.

In PRINCE2, the Quality Register is the document used to record quality activities, including quality inspections, tests, and their results. It provides a log of all quality-related actions planned and completed throughout the project, and it is maintained by the Project Manager. The Quality Register is distinct from the Quality Management Strategy, which defines the approach, and the Product Description, which defines quality criteria for a product.

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.

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.

Closing a Project includes preparing planned closure, which confirms products are delivered and accepted, and evaluating the project, which assesses benefits and captures lessons. These activities ensure the project is properly closed and that the organisation learns from it. Authorising stages, raising Exception Reports, or creating new Stage Plans belong to other processes.

Managing Product Delivery ensures that products are delivered according to the Work Package, meeting quality criteria.

The End Project Report is the document that formally confirms the project's products have been accepted. It is produced during the Closing a Project process and includes a summary of the project's achievements, including product acceptance records, to provide a formal basis for project closure.

The Project Brief is created during the Starting Up a Project process. This process is triggered before the project is formally initiated and produces the Project Brief as a key output, which includes the project mandate, outline business case, and project approach. It provides the foundation for the Initiating a Project process.

The 'Managing a Stage Boundary' process in PRINCE2 is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and confirm continued business justification. This process ensures that the project remains viable and that the Project Board can make informed go/no-go decisions before committing resources to the next stage.

The Stage Plan is the correct answer because it provides the detailed, time-boxed plan for the current management stage, which the Project Manager uses for day-to-day control. PRINCE2 mandates that each stage has its own Stage Plan, derived from the Project Plan, and it includes the specific product descriptions, activities, and resource allocations needed for that stage. This plan is the basis for monitoring progress, managing issues, and making corrective decisions within the stage.

Managing a Stage Boundary is the process that prepares for the next stage by producing an End Stage Report, updating the Business Case and Project Plan, and creating the next Stage Plan. The Project Board then reviews these documents and decides whether to authorise the next stage. This process is distinct from Controlling a Stage, which manages the current stage, and from Closing a Project, which ends the project.

The Closing a Project process is specifically designed to ensure that all project products are formally accepted, the project is evaluated, and resources are released in a controlled manner. It triggers the final stage of the project lifecycle, confirming that the project's objectives have been met and that the project can be closed in an orderly fashion.

In PRINCE2's risk management procedure, the 'Assess' step is where each risk is evaluated for its probability and impact, and then its overall severity is determined. This step combines the earlier 'Identify' outputs with a structured assessment to prioritize risks for subsequent planning and implementation. The Assess step is explicitly defined in the PRINCE2 risk management procedure as the point where probability and impact are estimated.

The 'Continued business justification' principle requires that the Business Case is reviewed and updated regularly to ensure the project remains desirable, viable, and achievable.

The PRINCE2 Project Board is composed of three mandatory roles: the Executive (Senior Responsible Owner), the Senior Supplier, and the Senior User. The Project Manager is not a member of the Project Board; instead, the Project Manager reports to the Project Board and manages the project on a day-to-day basis. Therefore, the Project Manager is NOT a mandatory role on the Project Board.

Separation ensures independent and objective assurance that the project is running correctly, free from the biases or conflicts of day-to-day management.

The Product Flow Diagram in PRINCE2 product-based planning shows the sequence in which products are developed and the dependencies between them. It is a key technique for identifying the order of creation and the relationships among products, which is essential for planning the project's activities and stages.

Managing Product Delivery (D) is the correct process because it governs the acceptance, execution, and delivery of work packages by the team manager. In the delivery stage, the team manager receives a work package from the project manager (via Controlling a Stage) and is responsible for producing the products, reporting progress, and delivering completed work back to the project manager. This process directly controls the team manager's activities in building the products.

In PRINCE2, the Project Manager is responsible for authorizing work packages to be executed by the team. This is because the Project Manager manages the day-to-day activities and has the authority to assign work to team members or Team Managers, ensuring that the work packages align with the project plan and stage tolerances. The Project Board provides overall direction and approves stage plans, but the authorization of individual work packages is delegated to the Project Manager.

Team Managers produce Checkpoint Reports to inform the Project Manager of progress against work packages.

The Project Board in PRINCE2 is designed to be an exception-driven body; it convenes only when decisions are required, such as approving stage plans or exception plans, rather than on a fixed schedule. This aligns with the PRINCE2 principle of management by exception, where the board delegates day-to-day management to the Project Manager and escalates only when tolerances are forecast to be exceeded.

Project Assurance is independent of the Project Manager and reports to the Project Board. Business assurance is one aspect of Project Assurance.

Manage by Stages means dividing the project into management stages, with a minimum of initiation and at least one delivery stage. Each management stage is authorized by the project board, which reviews the business case and approves the next stage plan. Stages may vary in length and are tailored to the project.

In PRINCE2, the Project Manager is authorized to manage risks and issues within the stage tolerance defined in the Stage Plan. If the risk is within tolerance, the Project Manager should update the Risk Register, take appropriate management action, and continue managing the stage without escalating to the Project Board.

The End Project Report is used to evaluate the project's performance against the Business Case and provide lessons for future projects.

When a change is proposed, PRINCE2 requires that the project's business justification remains valid. The principle of continued business justification ensures that any new requirement is assessed against the business case, and if it no longer aligns, the project may need to be stopped or revised. This principle is fundamental to maintaining project viability.

The Change Authority is the correct role to decide on low-impact changes when the Project Board has delegated that authority. The Project Manager assesses the change but does not decide, and the Project Board only gets involved if the change exceeds the delegated limits.

PRINCE2 explicitly defines a project as 'a temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case.' This definition emphasizes the temporary nature, the focus on outputs (business products), and the governance through a Business Case, which justifies the project's initiation and continuation.

The Change Authority role exists specifically to allow the Project Board to delegate authority for approving or rejecting changes. Project Assurance, Project Support, and Team Manager do not have the mandate to make change control decisions on behalf of the Project Board. When the Project Board is too busy to handle all change requests, appointing a Change Authority with defined limits is the correct PRINCE2 approach.

Continued business justification and learn from experience are two of the seven PRINCE2 principles that must be applied for a project to be considered a PRINCE2 project. Continued business justification ensures the project remains viable, and learn from experience ensures lessons are captured and applied. The other options are not PRINCE2 principles; they are either terms from other methodologies or optional tools and techniques.

During the Managing a Stage Boundary process, the Project Manager updates the Project Plan to incorporate the actual performance of the completed stage and to revise forecasts for the remaining stages. This ensures the Project Plan remains accurate and reflects the current reality, which is essential for continued business justification and decision-making.

The Product Description defines the product's purpose, composition, quality criteria, and quality methods.

The project controls section of the Project Initiation Documentation defines the mechanisms for controlling the project, including tolerance levels and escalation procedures. It is the appropriate place to describe how the project manager will escalate issues to the project board and how the project will be monitored and controlled. This directly answers the project board chair's question.

In PRINCE2, the Directing a Project (DP) process is owned by the Project Board and includes the activity 'Authorise a Stage or Exception Plan.' The Project Board uses DP to authorize the start of each new stage after reviewing the End Stage Report and Next Stage Plan produced by Managing a Stage Boundary. This is the governance checkpoint where the Board commits resources to the next stage.

The Project Plan is the high-level plan produced during Initiating a Project that describes how the project will deliver its products and is part of the Project Initiation Documentation (PID). It provides the baseline against which progress is monitored and is approved by the Project Board at the end of the initiation stage.

The Highlight Report is the PRINCE2 progress document produced by the Project Manager and sent to the Project Board at regular, agreed intervals (typically weekly or monthly) throughout a stage. It summarises stage status, including achievements, issues, risks, and forecasts, giving the Board ongoing visibility without waiting for stage boundaries. This matches the question's description of a regular-interval summary during a stage.

PRINCE2 characterizes a project as a temporary organization created to deliver one or more business products according to an agreed Business Case. The portal redesign has a finite duration, specific products, and requires justification, so it satisfies this definition. The other options describe permanent operational structures or indefinite work, which lack the temporary, product-driven nature of a project.

In PRINCE2's Managing Product Delivery process, the Team Manager works under the authority of the Project Manager and must escalate any issue that could affect product quality. The correct action is to inform the Project Manager via the Checkpoint Report (for routine progress) or by raising an issue if the problem is significant. The Team Manager does not have authority to change the product, the contract, or the project plan without Project Manager approval.

In PRINCE2, the Managing Product Delivery process focuses on the work required to create project products. The Team Manager's primary responsibility is to accept Work Packages from the Project Manager and then deliver them by coordinating the team's work, ensuring the products meet the required quality criteria. This directly aligns with option A, as accepting and delivering Work Packages is the core function of the Team Manager within this process.

The tailoring principle requires that PRINCE2 be adapted to the project's specific environment, scale, complexity, importance, capability, and risk. It ensures the method is proportionate and fit for purpose while the seven principles remain mandatory. Adapting processes and themes, not abandoning them, is the correct interpretation.

In PRINCE2, the Change Authority is a body to which the Project Board delegates responsibility for making decisions on change requests and off-specifications, within defined limits. This allows the board to focus on strategic oversight while empowering a separate group to handle change control efficiently. The Change Authority is formally defined in the 'Organize' process and its authority is documented in the Project Initiation Documentation.

The Product Breakdown Structure (PBS) is a hierarchical decomposition that identifies all the products the project must produce, breaking the final product into its component products and sub-products. It answers 'what' will be produced, not 'how' or 'in what order'.