PRINCE2 Foundation (PRINCE2F) — Questions 601–675

The Business Case practice in PRINCE2 provides a mechanism to judge whether the project is desirable (benefits outweigh costs), viable (achievable within constraints), and achievable (feasible with available resources). It is the central justification for initiating and continuing the project, ensuring ongoing business justification throughout the project lifecycle.

Projects are temporary, produce unique outputs, and require cross-functional teams.

The Controlling a Stage process includes the activity of authorising Work Packages, which are formal agreements to produce products. The Project Manager assigns work packages to the Team Manager.

The purpose is to provide the Project Board with information to review current stage, approve next stage plan, and update the Business Case.

The Project Initiation Documentation (PID) is the key output of Initiating a Project. Option D is correct.

The Executive (Senior Responsible Owner) owns the Business Case and is ultimately responsible for its maintenance. The Project Manager may assist but is not the owner.

The Starting Up a Project process outputs the Project Brief, Daily Log, initiation Stage Plan, and appoints the Executive and Project Manager. The Risk Management Approach is developed later in Initiating a Project.

Option B (Team Manager) is correct because PRINCE2 defines the Team Manager role as the person responsible for the team's work and for delivering the products within the team plan. This role is distinct from the Project Manager and is formally defined in the PRINCE2 management structure.

The Project Board provides overall direction, approves stage plans, and authorizes stage boundaries. Day-to-day management and work package authorization are PM responsibilities.

An RFC is a proposal for a change to a baselined product, while an Off-spec is a deviation from the specification found during quality inspection.

The Risk Register is the repository for all risk management information throughout the project.

Continued Business Justification is one of the seven PRINCE2 principles, ensuring the project remains viable throughout.

According to PRINCE2, when a Team Manager reports that a Work Package is likely to exceed its tolerances, the Project Manager must first assess the situation and consider corrective actions within the stage tolerance. This is because the Project Manager has delegated authority to manage the stage within the agreed stage tolerances, and only if the forecast exceeds those tolerances should an Exception Report be raised to the Project Board. The correct first step is always to evaluate whether the issue can be resolved within the existing tolerance limits before escalating.

The PID includes the Business Case, Project Plan, and Risk Register. The Project Brief is a predecessor document, and the Benefits Review Plan is a separate document.

Project Assurance is an independent role that provides ongoing assurance to the Project Board, while a quality review is a specific technique for reviewing products. Option B is correct.

Fallback is used when a response plan is implemented only if the risk occurs, often after other responses have failed or are not feasible.

The risk management procedure starts with 'Identify' risks, followed by Assess, Plan, Implement, and Communicate.

The Team Manager is responsible for accepting and delivering Work Packages, ensuring that products meet quality criteria.

PRINCE2 defines quality as 'fit for purpose', meaning the product must meet its stated requirements and satisfy user needs.

The End Stage Report is produced to report on the current stage's performance.

The Project Manager is responsible for maintaining the Business Case as part of day-to-day management. The Executive (SRO) owns and approves it.

Managing a Stage Boundary is the process where the PM presents an End Stage Report and next Stage Plan to the Board for approval.

Project Assurance is an independent role from the Project Board, responsible for monitoring compliance with standards and providing objective oversight.

The purpose is to provide the Project Board with information to review the current stage and authorize the next stage.

PRINCE2 separates the Project Manager role from Project Assurance to ensure independent oversight and avoid conflicts of interest. The Project Manager is responsible for day-to-day management and decision-making, while Project Assurance provides an objective check that the project remains aligned with business, user, and supplier interests. This separation prevents the Project Manager from being the sole judge of their own work, which could compromise governance and control.

The PID includes the Project Plan, Business Case, and Risk Register (among others).

The Board authorizes the project after reviewing the PID, which is produced in IP. This is the 'authorize the project' activity in DP.

In the Managing Product Delivery process, the Team Manager is responsible for producing the Checkpoint Report. This report provides the Project Manager with progress information on the work packages assigned to the team, including any issues such as quality problems. The Checkpoint Report is a key control document that the Team Manager uses to communicate status at regular intervals, typically weekly.

In PRINCE2, the classification of acceptance criteria (e.g., 'Must', 'Should', 'Could') is a customer decision. When a criterion classified as 'Should' is discovered during a quality review, the correct action is to seek confirmation from the customer that the classification is acceptable, as only the customer can decide whether a desirable criterion can be downgraded or reclassified. This ensures the project remains aligned with customer expectations and avoids unauthorized changes to the Project Product Description.

Management by Exception means that deviations within tolerance are handled by the PM, but deviations forecast to exceed tolerance are escalated to the Board.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report to seek direction.

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

Project Assurance provides independent oversight to the Project Board, ensuring the project is on track without being influenced by the Project Manager's day-to-day perspective.

The Project Plan is approved by the Project Board, as it sets the baseline for the project's scope, schedule, and cost.

The Quality Management Approach defines how quality will be managed, including quality methods, tools, and responsibilities.

Managing a Stage Boundary provides the Project Board with sufficient information to review the current stage and plan the next stage, and to decide whether to continue the project.

PRINCE2 defines six threat responses: Avoid, Reduce, Fallback, Transfer, Accept, and Share. Options A, C, and D are correct; Exploit and Enhance are opportunity responses.

Closure is authorised by the Project Board in the Directing a Project process, based on the End Project Report and closure recommendation from the PM.

PRINCE2 recommends product-based planning, which includes creating a Product Breakdown Structure (PBS) and Product Flow Diagram.

Project Assurance is independent, performed by Project Board members or delegates, and covers all aspects of the project.

In PRINCE2, the Project Manager is responsible for maintaining the Business Case throughout the project. This includes monitoring actual costs and benefits against the Business Case, updating it with any changes, and ensuring it remains viable. The Project Manager does not create the Business Case (that is the Executive's role) but is accountable for its ongoing maintenance and reporting.

The Starting Up a Project process ensures that there is a viable and worthwhile project before the initiation stage begins.

SB produces the End Stage Report, updated Project Plan, next Stage Plan (or Exception Plan), and Lessons Report. The Highlight Report is from CS, and the Project Brief is from SU.

The Executive is the single individual responsible for the Business Case throughout the project in PRINCE2. They own the Business Case and must ensure it remains viable, justified, and aligned with organizational strategy, approving any changes to it. The Project Manager only maintains the Business Case document but does not have authority to update its justification or approve changes.

Option B is correct because the Project Manager is responsible for managing the day-to-day activities of the project within the tolerances set by the Project Board. This includes monitoring progress, resolving issues, and escalating deviations that exceed tolerances. PRINCE2 defines this as a core duty to ensure the project remains on track without requiring constant Board intervention.

In PRINCE2, the project board is responsible for making decisions about project viability, including closure. During the Initiating a Project process, if the business case becomes unviable, the project manager must escalate this to the project board, who then decides whether to close the project. Option C correctly reflects this by advising the board and recommending closure, aligning with the 'continued business justification' principle.

In PRINCE2, the risk owner is accountable for the overall management of a risk, including monitoring and ensuring that appropriate responses are implemented. The risk actionee, on the other hand, is responsible for performing specific actions or tasks assigned as part of the risk response plan. Option C correctly captures this distinction between accountability and execution.

Avoid and Reduce are threat responses. Exploit and Share are opportunity responses, and Reject is also an opportunity response.

Directing a Project is the process used by the Project Board to make key decisions and provide overall direction and control, including authorization of stages and closure.

PRINCE2 defines specific roles: Project Manager, Team Manager, Project Assurance, Project Support, and the Project Board (Executive, Senior User, Senior Supplier). 'Risk Manager' and 'Quality Manager' are not standard roles in PRINCE2; their responsibilities are typically covered by Project Assurance or delegated within the team.

Product-based planning focuses on defining products first, then activities. It includes Product Breakdown Structure, Product Flow Diagram, and Product Descriptions.

The Senior User represents the users and ensures that the products meet their needs. The PM manages delivery but the Senior User defines requirements.

Closing a Project includes handing over products and producing the Lessons Report. The End Stage Report is from SB, and the Project Brief is from SU.

The PRINCE2 project management team includes the Executive, Senior User, Senior Supplier, Project Manager, Team Manager, Project Assurance, and Project Support. The Project Board consists of the Executive, Senior User, and Senior Supplier. 'Project Sponsor' is not a PRINCE2 role; 'Steering Committee' is not a PRINCE2 term.

Closing a Project ensures controlled closure, handover of products, and confirmation that the project is complete. It does not manage benefits realization; that happens post-project.

Managing a Stage Boundary (SB) is the process for reporting on the current stage and planning the next stage, producing both the End Stage Report and the next Stage Plan.

Directing a Project ensures the Project Board provides direction and makes key decisions, including authorising initiation, stage plans, and closure.

The PRINCE2 principle 'Manage by stages' requires that the project be divided into management stages, each with its own plan and tolerances. This allows the Project Board to review progress and viability at key decision points before committing further resources, ensuring ongoing business justification and control.

Since the change budget is exhausted, the project manager cannot approve further changes within their delegated authority. Therefore, they must escalate to the Project Board via an Exception Report.

In PRINCE2, the Benefits Management Approach is a living document that must be updated with actual results during the Closing a Project process, even if benefits are not yet fully realized. Since the business case has not been fully realized, the project manager should record the actual benefits achieved and recommend a follow-on action plan for the remaining benefits to be managed post-project. This ensures that the expected benefits are not lost and that the organization can continue to pursue them.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a baseline for the project.

The Starting Up a Project process is responsible for appointing the Executive and the Project Manager because it occurs before the project is formally initiated. During this process, the project mandate is reviewed, and key roles are assigned to ensure the project has the necessary leadership to proceed to the initiation stage. This is defined in PRINCE2 as the point where the project board is established and the Project Manager is selected.

The Business Case practice is the correct answer because it is the PRINCE2 practice that specifically defines the reasons for initiating a project and ensures that the project remains desirable, viable, and achievable throughout its lifecycle. It provides the justification for continued investment by requiring regular review and update of the business justification, which is documented in the Business Case. Without a valid Business Case, the project should be stopped.