Explanation:

✅ Option B (Correct)

This is an appropriate application of the ‘ensure continued business justification’ principle. PRINCE2 requires that a project’s business justification, documented in the Business Case, remains valid throughout its lifecycle. This includes continuously reviewing and assessing risks that could impact the achievement of the project’s objectives and benefits. The potential negative impact on protected species and the environment is a significant risk that could jeopardize the project’s ability to meet Louistown’s ‘green town’ status and sustainability targets, which are core to its business objectives. Reassessing this risk proactively during stage 2, before site preparation in stage 3, ensures that the project’s viability and desirability are continually re-evaluated.

❌ Why the other choices are incorrect:

• Option A is incorrect: The ‘ensure continued business justification’ principle primarily refers to the project’s justification for the commissioning organization, not the supplier’s internal business case for their own operations.
• Option C is incorrect: While the Business Case is baselined at initiation, PRINCE2’s ‘ensure continued business justification’ principle mandates that it is a living document, requiring continuous review and update throughout the project, especially regarding significant risks and benefits. It is not a one-time activity.
• Option D is incorrect: The ‘ensure continued business justification’ principle applies to the project itself. While the supplier (BuildyBrick) may have its own business case, the project’s business justification must be maintained. Furthermore, it is perfectly appropriate for a supplier with relevant expertise (environmental protection experts) to assess risks that directly impact the project’s ability to deliver its objectives.

Explanation:

✅ Option D (Correct)
Reasoning: The scenario describes the project manager asking the Sustainability Manager to present sustainability data from a previous initiative (‘greentown’ award) to the project team. This is a clear application of the PRINCE2 principle ‘Learn from experience’. This principle dictates that project teams should actively seek out and apply lessons from previous projects or initiatives, as well as continuously learn throughout the current project. Using the ‘greentown’ award data provides helpful insights for the LouisShopping project’s sustainability requirements.

❌ Why the other choices are incorrect:

• Option A is incorrect: ‘Manage by stages’ is a principle focused on segmenting a project into manageable stages for planning, monitoring, and control, providing decision points. While the action occurs during a stage, using past data is not the primary illustration of this principle.
• Option B is incorrect: Similar to A, ‘Manage by stages’ relates to control points, not specifically to using previous data, nor does it inherently mean more shorter stages for tighter control, though that can be a benefit. The key action here is leveraging past knowledge.
• Option C is incorrect: While the ‘Learn from experience’ principle does involve continuous learning throughout a project, option D’s reasoning better fits the specific scenario described, which is about proactively bringing previous project experience and data to inform the current project’s planning, particularly at the initiation stage before significant work commences.

Explanation:

✅ Option C (Correct)

The PRINCE2 principle ‘define roles and responsibilities and relationships’ stipulates that a clear and appropriate project management team structure must be in place, with defined roles and responsibilities. A key responsibility of the Project Executive is to maintain the project’s business justification throughout its lifecycle. When the LouisShopping Project is combined into a modernization programme, this represents a significant change in its strategic context. The Project Executive, therefore, has a critical responsibility to review the project’s business justification to ensure it remains valid, viable, and aligned with the overarching programme objectives. If this review is not conducted, or not conducted appropriately, it constitutes a failure in the application of the Project Executive’s defined responsibilities under the ‘define roles and responsibilities and relationships’ principle.

❌ Why the other choices are incorrect:

• Option A is incorrect: While it is true that a key project within a programme should receive support from the programme team, this option does not address the core issue of the appropriateness of combining the Project Executive and Business Change Manager roles, nor does it provide a reason for an *inappropriate* application of the principle.
• Option B is incorrect: While alignment of responsibilities between a project and programme is generally desirable, it should not come at the cost of creating a conflict of interest or compromising the independence required for key governance roles. The Project Executive’s primary accountability for the project’s business justification requires a degree of objectivity that can be challenged by simultaneously holding a role deeply vested in programme benefits realization. This option also does not explain why the current application is *inappropriate*.
• Option D is incorrect: PRINCE2 strongly advises against combining the Project Executive role with other Project Board roles (Senior User, Senior Supplier) or the Project Manager, due to inherent conflicts of interest. While combining the Project Executive role (project level) with the Business Change Manager role (programme level) also carries a significant risk of conflict of interest (where the PE might struggle to objectively assess the project’s viability if it conflicts with their BCM role in achieving programme benefits), option C provides a more direct and specific reason related to a critical Project Executive responsibility in the given scenario, aligning with the expected audit outcome.

Explanation: The ‘manage by stages’ principle in PRINCE2 emphasizes breaking down a project into manageable stages to maintain control and allow for regular review and adaptation. While formal authorization for a new stage occurs at stage boundaries, the Project Board can make decisions and adjust its composition proactively within a stage if it helps to maintain control over the project’s objectives and resources. In this scenario, the LOB portfolio team mandated a new recycling company for Stage 3 during Stage 2. By inviting this new supplier to join the Project Board as Senior Supplier during Stage 2, the project is proactively integrating a key resource and stakeholder. This allows for their input during the detailed planning for Stage 3 (which likely occurs in Stage 2) and ensures the Project Board has direct oversight and control over this new resource from the moment its involvement is decided. This action directly contributes to ‘providing control over resources’ for the upcoming stage, aligning with the intent of managing by stages to ensure project viability and controlled progress. Therefore, this appointment is an appropriate application of the principle.

Explanation:

✅ Option C (Correct)
Reasoning: The ‘Focus on products’ principle emphasizes that a project defines and delivers its products, rather than simply undertaking activities. The Project Product Description (PPD) is a key management product that provides a precise definition of the project’s main output, including its quality requirements. When a significant change in requirements occurs (e.g., increasing parking capacity from 4,000-5,000 to 10,000 vehicles), it directly alters the definition of this main product. By escalating this change to the Project Board before updating the project product description, the Project Manager is ensuring that the PPD remains a controlled and authoritative document. This action underscores that the PPD is critical for effectively managing the project, as any fundamental changes to the product must be formally approved at the appropriate governance level to maintain a clear and agreed product focus. Thus, the PPD is actively used to support the management of the project by providing a stable, approved product scope.

❌ Why the other choices are incorrect:

• Option A is incorrect: While the significant increase in parking capacity would almost certainly exceed tolerances (e.g., cost, time, scope) and therefore necessitate escalation under the ‘Manage by exception’ principle, the specific phrasing ‘before updating the project product description’ puts a direct emphasis on the importance and controlled nature of the PPD itself. While ‘Manage by exception’ is likely being applied, ‘Focus on products’ provides a more direct and comprehensive explanation given the explicit mention of the PPD.
• Option B is incorrect: While the Project Board’s overall responsibility includes ensuring benefits outweigh costs and risks (part of ‘Continued business justification’), this option misrepresents the ‘why’ for ‘Manage by exception’ in this context. The core of ‘Manage by exception’ in this scenario is about escalating a deviation from agreed tolerances, not solely about the Project Board’s broader benefit-cost analysis role.
• Option D is incorrect: ‘Focus on products’ is about defining and delivering the required products, not directly about the benefits those products will achieve. Benefits are primarily associated with the ‘Continued business justification’ principle. While increased parking might lead to increased customer numbers (a benefit), this is not the reason the ‘Focus on products’ principle is being applied by escalating the PPD change.

Explanation:

The correct option is C: ‘Focus on products’, because the project manager should escalate to the project board changes to make the shopping centre be self-service that exceed tolerances.

The ‘Focus on products’ principle emphasizes defining the project’s products in terms of their requirements and quality criteria. Documenting the requirement for customer-facing self-service systems in the Project Product Description (PPD) directly aligns with this principle, as the PPD details the main product the project will deliver.

Furthermore, the scenario states that the Project Product Description was ‘initially baselined’. Baselining a product description means it is formally approved and placed under change control. If a new requirement (like self-service systems) is added to a baselined PPD, it constitutes a change. If this change causes a deviation that exceeds the project’s agreed tolerances (e.g., on cost, time, scope, quality, risk, or benefits), then the project manager must escalate the issue to the Project Board, applying the ‘Manage by Exception’ principle. Option C correctly links the ‘Focus on products’ principle (through the documentation of requirements in the PPD) with the necessary control mechanism (escalation for tolerance deviations).

Why other options are incorrect:

• Option A is incorrect: ‘Tailor to suit the project’ is about adapting the PRINCE2 method itself to the project’s specific environment, not about managing specific product requirements or their baselining in this context. While controlling documents is part of tailoring, the principle’s primary application is not to the act of documenting a specific product feature.
• Option B is incorrect: Similar to option A, ‘Tailor to suit the project’ refers to adapting the PRINCE2 method. Requirements are defined and managed, not ‘tailored’ in the sense of adapting the method. The justification for the requirement (making the shopping centre attractive) is a business benefit, not an application of the ‘Tailor to suit the project’ principle.
• Option D is incorrect: While ‘Focus on products’ is the correct principle, the reason provided, ‘because documenting the need for shopping centre to self-service at the start should ensure user acceptance when the shopping centre is complete’, is not the primary or most complete explanation. While clear product definition aids user acceptance, the core ‘why’ for documenting requirements in a baselined PPD in PRINCE2 is to provide a clear, agreed-upon definition of what is to be delivered, enabling effective management, control, and, if necessary, escalation when deviations occur.

Explanation:

✅ Option C (Correct)
Reasoning: The principle ‘Define roles, responsibilities, and relationships’ ensures a clear organizational structure with defined accountabilities and stakeholder engagement. In this scenario, the project manager is documenting the architects’ iterative-incremental approach for Stage 2 (design) and adapting controls. Crucially, the case study also highlights that BuildyBrick, the main contractor for Stage 3 (construction), will use a traditional delivery approach. This creates a hybrid project environment. To manage such a project effectively, it is essential to clearly define the distinct working methods of different parties (architects vs. BuildyBrick) and how their roles, responsibilities, and interfaces are established and integrated into the overall project structure. Documenting these different approaches and adapting controls ensures clarity for all involved, which is a direct application of defining roles, responsibilities, and relationships in a hybrid context.

❌ Why the other choices are incorrect:

• Option A is incorrect: While ‘Tailor to suit the project’ is a principle being applied by adapting controls, option C provides a more fundamental reason directly tied to the organizational complexity of managing different delivery approaches by different parties within the same project. Tailoring is the action, but the reason for that specific action, in this context, underpins the need for clear roles and relationships across diverse methodologies.
• Option B is incorrect: The architect’s delivery approach is specific to Stage 2 (design). It should not drive the controls used by the project manager across the entire project lifecycle, especially since the overall project has an established requirement for a traditional delivery approach for later stages, such as construction by BuildyBrick.
• Option D is incorrect: While it is true that the project manager is responsible for documenting tailoring proactively in the Project Initiation Documentation (PID), this option describes a general duty of the project manager rather than explaining why the ‘Define roles, responsibilities, and relationships’ principle is being applied specifically due to the differing delivery approaches in the scenario. The principle’s application is about the clarity of the organizational structure and interactions, not just the act of documentation.

Explanation:

✅ Option B (Correct)
Reasoning: The PRINCE2 ‘people’ element emphasizes effective communication and collaboration to build trust and resolve differences within project teams. Regular meetings between the architect and the Chief Technology Officer’s team directly facilitate information sharing and mutual understanding, which is crucial for integrating diverse expertise and building trust when disagreements arise over technical requirements.

❌ Why the other choices are incorrect:

• Option A is incorrect: While meetings can provide progress updates, the primary issue is disagreement and lack of technological awareness, not just progress tracking. Building trust and resolving technical differences are more pertinent.
• Option C is incorrect: Regular team meetings are vital for day-to-day coordination and problem-solving, not solely for reporting progress to the Project Board. This misrepresents the purpose of internal team communication.
• Option D is incorrect: Relying solely on natural self-organization for information sharing is insufficient when a clear knowledge gap and disagreement exist. Proactive facilitation by the Project Manager is appropriate for ensuring effective collaboration and resolution in such situations.

Explanation:

The Project Manager’s decision to reject the Chief Engineer for being ‘too senior’ for a work package is inappropriate according to the ‘people’ element in PRINCE2. PRINCE2 emphasizes that project roles are temporary and distinct from an individual’s permanent organizational seniority. The primary focus of ‘leading successful teams’ is to assign work to individuals with the necessary skills and experience to ensure quality and technical integrity. A Chief Engineer, especially from the main contractor, would possess critical expertise for checking design integrity. It is common for specialists, even those more senior in their functional organization than the Project Manager, to perform specific work packages. Rejecting expertise based on perceived seniority for a work package undermines effective team leadership and risks project quality.

Explanation:

✅

Option D (Correct)

The scenario explicitly states that the issue management procedure is "too complicated" and, as a result, "people have not been following" it. In PRINCE2 7, particularly under the ‘people’ element, effective leadership involves understanding and adapting to the team’s needs and how they work. Simply issuing a reminder to follow a dysfunctional procedure is not ‘leading successful change’. Instead, the project manager should investigate the reasons for the complexity and non-adherence, then work with the team to realign or simplify the procedure so it becomes practical and usable within the project’s emerging culture. This proactive approach addresses the root cause of the problem and fosters true adoption, rather than just forcing compliance.

❌ Why the other choices are incorrect:

• Option A is incorrect: While the project manager should ensure procedures are followed, rigidly enforcing a procedure that is openly identified as "too complicated" and not being followed by the team demonstrates a lack of adaptability and understanding of the ‘people’ element. Co-creation is valuable, but if the outcome is impractical, it requires further adjustment.

• Option B is incorrect: This option contradicts the problem statement. The scenario clearly states that the procedure is not ensuring changes are dealt with in a responsive or controlled way because it’s too complicated and not being followed. Believing it should ensure this, despite evidence to the contrary, is an unrealistic expectation.

• Option C is incorrect: Establishing whether pending change requests are following the approved procedure (which is known to be too complicated) is a reactive step that does not address the underlying problem. It focuses on compliance rather than resolving the fundamental usability issue of the procedure itself, which is crucial for ‘leading successful change’.

Explanation: The project manager’s action is appropriate because the City Planning Officer is a critical external stakeholder who needs to approve the design of the LouisShopping centre and has expressed uncertainty about achieving project goals. Engaging proactively with a new incumbent in such a key role, especially one ‘taking an active interest’, is fundamental to ‘leading successful change’ according to the PRINCE2 ‘people’ element. This initial meeting provides a vital opportunity to build rapport, share information (designs, issue management procedure), and, most importantly, gather feedback from this key influencer. This feedback is crucial for understanding their perspective, addressing potential concerns, and facilitating future approvals, thereby promoting alignment and project success.

Why the other choices are incorrect:

• B is incorrect: While the City Planning Officer eventually approves designs, the primary purpose of an introductory meeting with a *new* officer for ‘leading successful change’ is broader than just approving or rejecting ‘pending requests to change the design’. It’s about engagement, understanding, and feedback.
• C is incorrect: PRINCE2 emphasizes comprehensive stakeholder management, not just internal team members. The City Planning Officer is a high-influence external stakeholder whose engagement is essential for the project’s success and reputation.
• D is incorrect: Explaining the issue management procedure to a key external stakeholder like the City Planning Officer is good practice. It promotes transparency, clarifies how concerns will be handled, and allows them to understand the project’s governance, which can facilitate smoother future interactions and ‘leading successful change’.

Explanation:

✅ Option B (Correct)
Reasoning: PRINCE2 emphasizes proactive and appropriate stakeholder engagement, especially for groups likely to be negatively impacted or resistant. Arranging a dedicated meeting allows the project manager to explain the project’s approach, demonstrate empathy for the society’s concerns, and, crucially, to listen to their feelings and identify their key concerns. This two-way communication fosters understanding, builds trust, and provides valuable input for potentially adjusting plans or developing mitigation strategies, aligning with the Communication Management Approach.

❌ Why the other choices are incorrect:
* Option A is incorrect: Minimizing communication with an unhappy stakeholder group is counterproductive and goes against PRINCE2 principles. It can lead to increased resentment, negative publicity, and potential escalation, making it harder to manage the project successfully.
* Option C is incorrect: While transparency is good, inviting society members to a Project Board meeting is generally not the best forum for this type of detailed, potentially emotional discussion. Project Board meetings are for strategic direction and decision-making, and this setting might not allow the society members to fully express their concerns or for the project manager to effectively address them. A dedicated meeting is more appropriate.
* Option D is incorrect: Simply explaining a process for raising changes is a reactive approach. The project manager’s primary responsibility is to proactively engage and manage stakeholder expectations and concerns, rather than waiting for them to initiate contact through a formal process. The problem statement indicates they are unlikely to be happy, so a proactive engagement is necessary.

Explanation:

The Communication Management Approach details how, when, and to whom project information will be communicated. The scenario describes a specific, recurring communication event: the Heritage Director speaking every three months about the project’s impact on heritage. This falls directly under the ‘Communications schedule and procedure(s)’ section of the Communication Management Approach, which outlines the frequency, content, and responsibilities for specific communications.

Why the other choices are incorrect:

• A: Stakeholder analysis is an input to the Communication Management Approach, identifying who the stakeholders are and their interests, but not the detailed schedule of communications.
• C: Supporting tools and techniques would list the methods or platforms used for communication (e.g., presentations, newsletters, specific software), not the content or frequency of a particular communication event.
• D: Resources refers to the personnel, budget, and other assets required to perform the communication activities, not the schedule or content of the communication itself.

Explanation:

This question requires matching statements to the correct section of a PRINCE2 Business Case. The analysis is as follows, referencing the statements from top to bottom:

✅ Statement 1: ‘Funding has already been secured from the local council’ matches with -> E. Costs
Reasoning: The ‘Costs’ section of the Business Case details the project’s finances, including the source of funding. Confirming that funds are secured is a critical element of the financial appraisal and is documented here.

✅ Statement 2: ‘The local council has been criticized for the lack of investment in the local area’ matches with -> A. Reasons
Reasoning: The ‘Reasons’ section provides the justification for the project, explaining the problem or opportunity it addresses. The council’s criticism is the direct driver or rationale for initiating this investment project.

✅ Statement 3: ‘20% of local businesses will be unable to afford to relocate…’ matches with -> C. Expected benefits and dis-benefits
Reasoning: This statement describes a negative outcome for a stakeholder group. In PRINCE2, such undesirable outcomes are termed ‘dis-benefits’ and must be identified, quantified, and weighed against the expected benefits in this section of the Business Case.

Explanation:

✅ Option B (Correct)

Reasoning: This is an appropriate application of the ‘business case’ practice. In PRINCE2, the business case provides the justification for the project and must remain viable. A key principle is ‘learn from experience’. By consulting the team from the Huntsville parking project, the project manager can gather valuable lessons, particularly regarding the challenges and failures (over-runs, budget excess, disruption). This information is crucial for developing a more realistic and robust business justification for LouisShopping, informing risk assessments, cost estimates, and strategies to minimize disruption.

❌ Why the other choices are incorrect:

• Option A is incorrect: While minimizing disruption is important, this option describes a desired outcome or risk mitigation, not the fundamental reason why meeting with the Huntsville team appropriately applies the ‘business case’ practice. The meeting’s purpose is to gather information to inform the business case, including strategies to minimize disruption.
• Option C is incorrect: The project team from Huntsville, while not direct stakeholders in LouisShopping, are a valuable source of lessons learned. PRINCE2 emphasizes learning from past projects to improve current ones, regardless of direct stakeholder status.
• Option D is incorrect: Consulting BuildyBrick’s experts for detailed estimates is certainly a valid and necessary step. However, learning from past project failures (like Huntsville) is a critical input for the overall business justification, risk assessment, and viability, which are core elements of the business case, especially during its preparation in Stage 1. This action is complementary, not an alternative that negates the value of learning from Huntsville.

Explanation:

✅ Option A (Correct)The PRINCE2 ‘business case’ practice mandates that the business justification for a project is established, maintained, and continually assessed. Risks, particularly those impacting project cost and time, directly influence the project’s viability and expected benefits, which are core components of the business case. Holding a workshop with the Project Board (who are accountable for the project’s justification) and key suppliers like BuildyBrick’s CEO to identify and discuss such potential threats is an appropriate and proactive way to ensure the full business case is robust and reflects the project’s overall risk profile.

❌ Why the other choices are incorrect:

• Option B is incorrect: While the Project Board should review the full business case when authorizing the project at the end of the initiation stage, this option describes an action of the Project Board, not the reason why the Project Manager’s activity of discussing risks for the business case is an appropriate application of the ‘business case’ practice itself. Option A provides the fundamental PRINCE2 principle for this activity.
• Option C is incorrect: While BuildyBrick’s CEO (as the Senior Supplier) has responsibility for managing risks within their scope of delivery, the ultimate accountability for the project’s overall business justification and strategic risks lies with the Project Board. The Project Manager’s role is to facilitate this discussion, ensuring the business case considers all relevant threats.
• Option D is incorrect: The scenario describes ‘events that might cause‘ delays or overspend, which are risks. Risks are managed through the risk register. Issues are events that have already occurred or are certain to occur. While issues can impact the business justification, proactively identifying potential threats to cost and time as part of preparing the business case falls under risk management, which directly informs the business case, not primarily the issue register.

Explanation:

This solution correctly maps the individuals to the PRINCE2 project roles based on their likely responsibilities and authority levels within a corporate structure.

✅ Step 1: Head of Portfolio Office matches with -> Project support Reasoning: Project support functions, such as administration, guidance, and tool support, are typically provided by a Project Management Office (PMO) or a portfolio office. The Head of Portfolio Office is the most appropriate individual to be responsible for providing these services.

✅ Step 2: Regeneration Manager matches with -> Business project assurance Reasoning: Business project assurance ensures the project remains aligned with the business case and user needs. A Regeneration Manager is a business-focused role, making them well-suited to verify that the project continues to meet business objectives and deliver value from a user perspective.

✅ Step 3: Portfolio Director matches with -> Project executive Reasoning: The Project Executive is ultimately accountable for the project’s success and must have sufficient authority. A Portfolio Director oversees a collection of projects and programmes, possessing the seniority, strategic view, and decision-making authority required to champion the project and ensure its continued business justification.

Explanation: The ‘Organization’ practice in PRINCE2 mandates that a project must have a defined and accountable structure, with a single point of accountability for the project’s overall success and continued business justification. This role is fulfilled by the Executive on the Project Board.

The Heritage Director’s primary responsibility, as described in the scenario, is ‘to ensure a focus on preserving the city’s history and tourist revenue from the 20,000 annual visitors to its historic sites’. While this is a critical aspect of the LouisShopping project, it represents a specific stakeholder interest (user interest) rather than the holistic business justification of the entire project. The project has diverse goals, including modernization, business opportunities, sustainability, and technology, all of which contribute to its overall business case.

Assigning the Heritage Director as the single point of accountability (Executive) would incorrectly narrow the focus of overall project justification to just heritage. The Executive must balance all stakeholder interests (business, user, supplier) and ensure the project remains viable for the wider organization.

Therefore, the Heritage Director is not appropriate for the Executive role; they would be better suited as a Senior User representing the heritage and tourism interests.

Explanation:

The ‘organization’ practice in PRINCE2 defines clear responsibilities. The CEO of BuildyBrick, as the head of the main contractor providing specialist resources and expertise for the entire project (design, construction, demobilization), is appropriately positioned to fulfil the Senior Supplier role. This role represents the interests of those providing the products and is a member of the Project Board, accountable for the quality of supplier deliverables throughout the project duration. Appointing the CEO as a Team Manager for a single stage, responsible for day-to-day team activities, is an underutilization of their strategic position and an inappropriate application of PRINCE2 roles, as a Team Manager operates at a lower management level, reporting to the Project Manager.

Explanation:

The matching of cost estimates to techniques is as follows:

✅ Step 1: ‘Cost of flooring – based on cost per unit, calculated using the size of the shopping centre floorplan’ matches with -> D. Parametric
Reasoning: This is a textbook example of parametric estimating. It uses a known parameter (cost per unit) and multiplies it by a project variable (the size of the floorplan) to derive a total cost.

✅ Step 2: ‘Cost of escalator stair systems – based on those supplied to similar sized shopping centres’ matches with -> C. Comparative
Reasoning: This estimate uses historical data from a similar, previous project as its basis. This method is also known as analogous estimating, which falls under the comparative technique in PRINCE2.

✅ Step 3: ‘Cost of resources – based on collecting opinions on the costs from a group of architects through several rounds of questions’ matches with -> E. Data analytics
Reasoning: This description perfectly aligns with the Delphi technique. Within the provided options, this is likely classified under ‘Data analytics’, where expert opinions are treated as data points gathered and refined through an analytical, iterative process to forecast an outcome.

Explanation:

The Senior Supplier (A) is responsible for providing the necessary resources and specialist skills to produce the project’s products, and for ensuring their technical integrity and quality. The Chief Technology Officer and BuildyBrick’s CEO represent the supplier interests for technology and construction, respectively. The addition of technology compliance audits directly relates to ensuring the quality, standards, and regulatory adherence of the products and services provided by these suppliers.

The Senior User (B) represents the interests of those who will use the products. The Project Executive (C) is accountable for the project overall and ensuring value for money from a business perspective, but delegates day-to-day approval of supplier-specific activities for stage plans to the Senior Supplier. Business layer (D) is not a defined PRINCE2 role.

Explanation:

The ‘plans’ practice in PRINCE2 emphasizes that a Project Plan must provide a high-level overview of the entire project, including all stages up to closure. The scenario states that ‘demobilization planning is rushed in order to hit the project end date,’ which indicates a deficiency in the initial Project Plan’s foresight or allocation for Stage 5 activities. If the Project Plan had been adequately detailed at its level to cover demobilization of contractors and equipment, the problem of rushed planning for this stage should not arise. The Project Executive’s instruction to prematurely prepare a detailed Stage 5 plan is a reaction to this underlying issue, rather than a proper application of the ‘plans’ practice, which would demand the Project Plan itself provide sufficient high-level detail for all stages from the outset. While PRINCE2 advocates for detailed planning one stage at a time (making option C also seem plausible), option D identifies a more fundamental deficiency in the overall project planning that leads to the scenario’s problem.

Explanation:

✅ Option A (Correct)
Reasoning: In PRINCE2, the ‘plans’ practice emphasizes that plans are not static documents but are iteratively refined. At the end of each management stage, the Project Board reviews the current stage’s performance, considers the plan for the next stage (Stage 3 in this case), and, critically, re-examines the Project Plan (high-level project plan) and the Business Case. This is to ensure the project remains viable and aligned with the organization’s strategic objectives (the Council’s strategy for the ‘Louistown is Open for Business’ portfolio). The changes in estimated time and cost directly impact the project’s business justification, making it essential to update the high-level plan and re-evaluate.

❌ Why the other choices are incorrect:

• Option B is incorrect: While organizing the project lifecycle into stages to manage planning horizon problems is a core principle of PRINCE2 (‘manage by stages’), it doesn’t fully explain why updating the high-level project plan and using it for justification at this point is appropriate. Option A provides a more direct and complete justification aligned with the purpose of stage boundaries and business justification.
• Option C is incorrect: The Project Plan indeed describes the ‘what, where, when, how, and by whom’ for the project as a whole. However, this description does not negate the need to update it as new information becomes available or conditions change. Plans are refined and updated at the end of stages to maintain their relevance and accuracy for decision-making.
• Option D is incorrect: The Project Plan is baselined, typically at the end of the initiation stage, but it is not immutable. PRINCE2 advocates for regularly reviewing and, if necessary, updating the Project Plan at the end of each management stage to reflect current realities and reconfirm continued business justification. Stating it should ‘not be updated’ is contrary to PRINCE2’s iterative planning approach and the principle of continued business justification.