MSP-Practitioner Sample Questions Answers

Gateway reviews are not part of delivering the capability but are governance checkpoints that occur at specific programme milestones, including the beginning of the programme, key decision points, and closure.

The MSP Practitioner explains: “Gateway reviews happen at beginning of programme, Key decision points of programme and closure of programme.” These reviews are formal assessments to validate readiness, progress, and compliance with governance before major transitions, tranche approvals, or programme closure.

Delivering the capability primarily involves initiating projects, managing their delivery under governance frameworks, and ensuring alignment between project outputs and benefit realization. Governance during delivery includes managing risks, issues, and quality controls to ensure outputs are produced to specification.

Gateway reviews are designed to provide independent assurance and decision points but are external to the ongoing activities of capability delivery. Recognizing this distinction helps maintain clarity of roles and processes within programme management, ensuring focused effort on delivery while maintaining appropriate oversight.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Risk Theme in MSP 5th Edition requires that all identified risks (both threats and opportunities) are assigned to an appropriate owner. A Risk Owner is someone who has the authority and resources to manage the risk and who is accountable for ensuring that the chosen response is implemented effectively. The seniority of the risk owner should be proportional to the level of risk exposure.

In this scenario, the risk—potential technological obsolescence or the opportunity for better technology—is categorized as high probability and high impact. This represents a significant exposure for the programme. Option A is the correct answer because MSP guidance states that high-priority risks that could fundamentally affect the programme's technical strategy or benefit realization should be owned by senior leaders. The Chief Technology Officer (CTO) is the ideal owner because they have the strategic oversight and technical authority to manage a risk related to "next-generation" smart meters. Appointing a senior executive ensures that the risk receives the necessary attention at the Programme Board level and that the phased roll-out strategy is technically sound and aligned with the organization's long-term technology roadmap. This demonstrates a mature application of risk management where accountability is placed at the level where the most impact can be made.

The Programme Manager is responsible for producing the Business Case. This document outlines the justification for the programme, including costs, benefits, risks, and options. The Programme Manager prepares the Business Case to ensure it is comprehensive, realistic, and aligned with the programme’s objectives.

The MSP Practitioner notes: “Programme manager prepares it as he is responsible for it,” emphasizing the role’s responsibility to articulate the strategic rationale and provide a sound basis for decision-making. The Business Case is then reviewed and approved by the SRO and other governance bodies.

The Programme Manager collaborates with other roles such as the Business Change Manager and SRO to ensure all aspects of the Business Case are valid and supported. This role is pivotal in maintaining the integrity and credibility of the programme justification throughout its lifecycle.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

In MSP 5th Edition, the Organization Theme defines the roles and responsibilities required to direct, manage, and deliver the programme. The most critical role is the Senior Responsible Owner (SRO). The SRO is ultimately accountable for the programme’s success and must be a senior individual with the authority to ensure the programme meets its objectives and delivers the projected benefits.

The appointment of a Chief Finance Officer (CFO) as the SRO is highly appropriate because the SRO must "own" the Business Case. Since the primary drivers of the Smart Meter Programme are financial (increasing customer numbers and reducing operational costs), the CFO is best positioned to monitor these outcomes. According to MSP, the SRO must provide strategic direction and ensure that the programme remains viable and focused on its benefits. Option A is correct because it highlights the SRO’s responsibility for benefit realization and financial accountability. While technical or industry knowledge (as mentioned in Options C and D) is helpful, the primary requirement for an SRO is the ability to lead the change and be accountable for the investment. The CEO (Option D) is usually part of the Sponsoring Group to whom the SRO reports, rather than being the SRO themselves, to maintain a layer of objective oversight.

Item of Information

Heading

The improvements in knowledge and opportunities will enhance engineers' self-fulfillment and careers

Key messages

Internal staff will be required to attend an initial company-wide presentation... followed by informal lunchtime sessions... and a monthly newsletter

Communication plan

The sponsoring group will be invited to a workshop to initially brainstorm likely stakeholders, and then the list will be grouped into categories and diagrams

Determining influence and interest

Key messages describe the "what" and "why" tailored to specific groups. The communication plan details the schedule and channels (newsletters, sessions). Categorizing and diagramming stakeholders is the core activity of determining their relative influence and interest.

The Risk Register is the key document where programmes establish the context for risk identification, assessment, and response planning. It captures all identified risks along with their evaluation and mitigation measures. The MSP Practitioner notes, "All the above information is part of Risk register," indicating that the Risk Register consolidates risk-related data essential for proactive management and decision-making throughout the programme lifecycle.

Levels of confidentiality and information security requirements are documented in the Information Management Strategy. This strategy sets out how information will be handled throughout the programme, covering aspects such as access rights, data classification, storage, and dissemination protocols to protect sensitive information.

The MSP Practitioner specifies: “Confidentiality details are defined in Information management strategy,” indicating that this document governs the secure management of programme data and communication. It is essential that confidentiality levels are clear to prevent unauthorized access to sensitive information, which could jeopardize the programme’s success or breach legal and regulatory obligations.

While Quality Management, Resource Management, and Benefits Management Strategies address different governance aspects such as assurance, resource allocation, and benefit realization, they do not primarily deal with confidentiality.

Information management is critical for stakeholder trust, compliance with legislation (e.g., GDPR), and safeguarding intellectual property or competitive advantage. Clear documentation in the Information Management Strategy ensures that all programme participants understand their responsibilities regarding confidentiality, promoting consistent and secure handling of data.

The Quality and Assurance Strategy is a governance document that outlines how quality management and assurance processes will be applied throughout the programme. Governance documents establish controls and frameworks for programme management, ensuring standards and compliance are maintained.

The MSP Practitioner clarifies that strategies—such as Quality Management Strategy—are integral governance documents that help define expectations, responsibilities, and quality assurance mechanisms. While the Blueprint and Project Dossier are boundary and management documents respectively, and the Risk Register is a management tool, governance documents like the Quality and Assurance Strategy provide oversight and control mechanisms essential for programme success.

This strategy ensures that quality is embedded in programme processes and deliverables, aligning with best practices and stakeholder expectations, which is vital for confidence and assurance in transformational change initiatives.

Design Action

Role

Show the vision statement to the engineering and maintenance staff and collect feedback from them

Business change manager

Facilitate the recruitment of a consultant to help the CTO assess new call centre technologies

Programme manager

Agree to the use of external consultants to help build the target operating model

Senior responsible owner

The BCM is responsible for the interface between the programme and the business (staff feedback). The Programme Manager handles the day-to-day operational facilitation and procurement support. The SRO has the ultimate authority to approve significant resource expenditures like external consultancies.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Senior Responsible Owner (SRO) is the individual with ultimate accountability for the programme, ensuring that it meets its objectives and delivers the projected benefits. According to MSP 5th Edition, the SRO must be a senior executive who can provide leadership, has the authority to make strategic decisions, and, crucially, "owns" the Business Case. The SRO is typically the person who represents the Sponsoring Group and has the greatest interest in the programme's success.

In the context of a utility company (UU) where the programme involves major financial investment, cross-selling services to increase revenue, and significant organizational transformation, the Chief Finance Officer (CFO) is the most likely candidate among the choices. While the CTO or CEngO (Options C and D) might lead specific technical projects or themes, the SRO role requires a broader view of the organizational benefits and financial viability. The CFO (Option A) is often positioned to bridge the gap between strategic corporate goals and the financial commitment required for a programme. They have the necessary seniority to hold the Programme Board accountable and to ensure that the programme remains aligned with the organization's overarching financial strategy. The SRO must be someone who can navigate the political landscape and secure the necessary resources, a role naturally suited to a C-suite executive like the CFO.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Justification Theme is the backbone of any MSP programme, ensuring that the investment of time, money, and effort is continually balanced against the expected benefits. This theme is most visible during the 'Evaluate new information' process at the end of a tranche, where the Business Case is formally reassessed.

Option B is the correct answer. When the programme office lead reports a budget overrun, it directly impacts the financial viability of the programme. The SRO’s recommendation to increase the budget to achieve the Target Operating Model (TOM) is a fundamental "Justification" activity. The SRO is arguing that the value of the benefits to be realized (the outcomes of the full TOM) still outweighs the increased cost of the investment. According to MSP 5th Edition, the justification must be maintained throughout the lifecycle; if the costs increase, the SRO must re-validate with the Sponsoring Group that the programme remains desirable and achievable. This application of the Justification theme ensures that the programme does not proceed blindly into a deficit but makes a conscious, governed decision to continue based on the remaining value. It protects the organization from "sunk cost fallacy" by forcing a transparent review of the investment's merit in light of the new financial data.

Capital costs are the costs of fixed assets and other tangible assets that are required for the programme. The MSP Practitioner states: “Cost of fixed assets and other assets that are found under 'Technology' head in blueprint is called Capital cost.” This typically includes equipment, buildings, and infrastructure necessary for the programme outputs.

The Benefit Realization Plan identifies milestones for benefit reviews. This plan details when and how benefits will be measured, reviewed, and managed to ensure they are achieved as expected.

The MSP Practitioner explains: “Benefits management plan identifies benefit reviews to increase likelihood of success.” Regular benefit reviews help detect issues early, enable corrective actions, and maintain stakeholder confidence.

This plan is crucial for monitoring benefit progress post-delivery, coordinating with business change activities, and ensuring benefits sustain over the long term. It aligns benefit tracking with programme stages and organizational priorities, enhancing accountability and transparency.

Approval to proceed at this stage authorizes work on all projects within the first tranche of the programme. The MSP Practitioner explains: "Approval to proceed is for first tranche, at end of that tranche, Go/No Go decision will be taken for next tranche," meaning that the programme is phased with controlled progression through tranches rather than approval for the entire programme upfront.

Among the options, "Remaining aligned with corporate strategy" is identified as a core MSP programme management principle. The principles underpin the mindset and behaviors needed for successful programmes. Other options, like Quality and assurance management and Leadership and stakeholder management, fall under governance themes or transformational flow rather than principles.

Providing regular progress updates to the Senior Responsible Owner (SRO) is the responsibility of the Programme Manager, not the Programme Office. The Programme Office supports by maintaining information repositories, tracking risks and issues, and ensuring control frameworks are implemented. The MSP Practitioner clarifies: “Programme manager provides regular updates to SRO,” distinguishing the oversight and reporting role of the Programme Manager from the administrative and support role of the Programme Office.

The four critical tests for benefits validation are Description, Observable outcomes, Attribution, and Measurement. "Attribution" assesses whether the programme is genuinely responsible for the benefit. The MSP Practitioner confirms, "Four tests of business validation are: Description, Observable outcomes, Attribution and Measurement," emphasizing the importance of validating benefits to ensure they result directly from programme activities.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The 'Identify the programme' process is the initial stage of the MSP transformational flow. Its primary purpose is to turn a vague idea or mandate into a clear programme brief that justifies further investment. During this process, the Senior Responsible Owner (SRO) is appointed to take personal accountability for the programme.

According to MSP 5th Edition, the SRO is the ultimate decision-maker at this stage. While the Programme Board (which may include the CEngO and other senior leads) provides advice and recommendations regarding resource feasibility and capacity, it is the SRO who must approve the way forward. Option A is correct because the SRO is responsible for ensuring the programme is viable and achievable. If the CEngO raises concerns about resource over-commitment, the SRO must weigh these concerns against the programme's strategic value and the Board's optimistic view. Ultimately, the SRO signs off on the programme brief and seeks authorization from the Sponsoring Group to move to the 'Design the outcomes' process. The Programme Manager (Option B) supports the process, but does not have the authority to approve the strategic direction or resource allocations of this magnitude. The SRO’s role is to provide the leadership and decision-making necessary to resolve such internal resource conflicts at the start of the journey.

In MSP, threats are negative risks that could impact the programme adversely. Valid responses to threats include Avoiding, Accepting, or Reducing the risk to mitigate potential harm. However, “Enhance” is not a valid response for a threat because it implies increasing the likelihood or impact, which is contrary to risk management objectives.

The MSP Practitioner states: “Threats should be minimized not enhanced,” reinforcing the principle that risk responses should focus on reducing negative effects or avoiding risks altogether. Accepting a risk might be chosen when mitigation is impractical or cost-prohibitive but still requires monitoring.

Understanding and applying appropriate risk responses is vital to effective programme risk management and maintaining control over uncertainties that could derail delivery.

All three—Governance, Boundary, and Management—are defined as Information Baselines in MSP. An Information Baseline refers to essential information repositories and frameworks that support programme control and management.

The MSP Practitioner states: “All are defined information baselines,” meaning that governance baselines set controls and accountability, boundary baselines define scope and limits, and management baselines cover operational details such as risks and issues.

Together, these baselines form a comprehensive information foundation, enabling effective oversight, coordination, and decision-making throughout the programme lifecycle.

Understanding and maintaining these baselines ensures transparency, consistency, and effective control over complex transformational programmes.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

In MSP 5th Edition, the Structure Theme is heavily reliant on the principle of 'Realize measurable benefits.' A core tenet of this principle is that benefits should not be "big bang" deliveries at the very end of a programme. Instead, MSP advocates for an incremental approach where the programme is broken down into tranches, each culminating in a landing point. A landing point is a point in time when a set of capabilities is transitioned into the business, allowing for the realization of intermediate benefits and the embedding of new ways of working.

The SRO’s request to delay all transitions until the end of the programme directly contradicts this principle. Option C is correct because MSP 5th Edition mandates that outcomes of benefit should be embedded at these intermediate landing points. By doing so, the programme provides early value to the organization, validates the "pathway to benefits," and reduces the overall risk of failure. Delaying all transitions to the end creates a high-risk environment where the business may be overwhelmed by a massive amount of change at once. Furthermore, the feedback loop from Tranche 1 (the customer complaints) should be used to improve the transition process for subsequent tranches, not to abandon the incremental delivery model altogether. The structure of a programme is specifically designed to provide these "safe harbors" where progress is assessed and benefits are consolidated before moving forward.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Decisions Theme in MSP 5th Edition defines how a programme maintains its integrity and remains aligned with strategic objectives through effective governance. A core part of this theme is the Decision-making Approach, which is a section within the Programme Strategy. This document outlines the levels of authority, the "delegation of power," and the escalation routes for issues and decisions that exceed the programme board's tolerance levels.

In this scenario, the workforce dissatisfaction is a significant issue that could derail the programme's benefits. The Programme Board needs to know if they have the authority to implement their proposals or if the strategic impact requires approval from the Sponsoring Group. Option C is the correct answer because the Decision-making Approach specifies the criteria for escalation. It answers the question: "Who has the authority to make this specific choice?" While the Issue Resolution Approach (Option A) tells you how to handle an issue, the Decision-making Approach tells you at what level the final call must be made. Consulting this document ensures that the programme respects the boundaries between operational management (the Board) and strategic ownership (the Sponsoring Group), thereby maintaining proper governance and accountability as defined in the MSP framework.

"Formally Approve" is not one of the MSP-defined levels of stakeholder engagement. MSP outlines levels such as Maintain Interest, Active Consultation, and Keep Informed to categorize the nature and intensity of stakeholder engagement.

The MSP Practitioner indicates: “Fourth option is face to face,” which means formal approval is a governance or decision-making activity rather than an engagement level.

Understanding and applying appropriate engagement levels ensures stakeholders receive relevant information and involvement suited to their influence and interest, facilitating support and minimizing resistance.

This categorization aids programme teams in managing communication and expectations effectively.

The POTI (Projects, Operations, Teams, and Infrastructure) model is part of the Blueprint governance theme. It defines the high-level scope and structure of the blueprint, outlining how projects, operational activities, teams, and infrastructure work together to deliver transformation.

The MSP Practitioner confirms: “POTI model defines scope blueprint,” situating it firmly within the Blueprint theme that describes the future state and the means to achieve it.

Understanding POTI helps in mapping and managing the components necessary for successful delivery of programme benefits within the defined future organizational state.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Knowledge Theme in MSP 5th Edition emphasizes the importance of managing information effectively to support decision-making and delivery. Information management ensures that data is reliable, accessible, and accurate. When a project team is dealing with "outdated" documentation that fails to reflect "current processes," the fundamental failure lies in the tracking of changes and the identification of the most recent authorized state of the information.

Option D, Version Control, is the specific aspect of information management designed to address this issue. Version control involves identifying different iterations of a document and ensuring that users are working with the correct, most up-to-date version. In a complex programme like UU’s, where processes are evolving across multiple projects and tranches, robust version control is essential to prevent rework and ensure that training materials (and other outputs) are aligned with the actual capabilities being delivered. While Integrity (Option B) is about the accuracy of the data itself, version control is the mechanism that manages the lifecycle of that data and prevents the use of obsolete information. Effective version control ensures that the "current processes" being developed are captured in a way that is visible and verifiable for all dependent projects, such as the Training Project.

Information

Section

The programme office will maintain master copies of all sections of the TOM. Requests for updates must be approved before being notified to the team

Version Control

All customer information... will be categorized as 'company confidential'. Anyone needing access must sign the standard company NDA

Privacy

At the end of the programme, all financial information will be transferred to the UU archive system... available on request

Retention

Controlling master copies and approving updates is the definition of Version Control. Handling sensitive personal data and NDAs falls under Privacy. Archiving and long-term availability post-programme is the focus of Retention

A key attribute for the Senior Responsible Owner (SRO) is having access to and credibility with key stakeholders because the SRO plays a pivotal role in stakeholder management and programme accountability. The MSP Practitioner notes, "This attribute is necessary as SRO is also involved in stakeholder management," emphasizing that SRO’s influence and stakeholder credibility are critical to programme success.

Good budgeting and resource allocation are typically the responsibilities of the Programme Manager or Project Managers, not senior leadership. Senior leadership focuses on strategic and cultural aspects such as vision creation and empowered decision-making. The MSP Practitioner clarifies, "Good budgeting and resource allocation skills ... is done by programme manager/project managers," distinguishing operational financial management from senior leadership duties.

The probability of success is higher when programme requirements are well-defined and clearly understood. MSP Practitioner states: “Probability is high when requirements are well defined and clearly understood. Clear specifications of output increases the probability of success.” Process changes affecting technology and structures typically have clearer specifications and boundaries, making successful delivery more likely compared to changes driven by complex behaviors or historical practices.

The Senior Responsible Owner (SRO) is accountable for confirming programme closure. This responsibility involves assessing whether the programme’s Business Case objectives and benefits have been satisfactorily met or if the programme is no longer viable.

The MSP Practitioner states: “SRO will confirm programme closure if business case is satisfied or unviable.” The SRO ensures that all closure criteria, including benefit realization, risk mitigation, and stakeholder expectations, are addressed before formally closing the programme.

While the Programme Manager manages the operational closure tasks and the Sponsoring Group provides governance oversight, ultimate closure accountability rests with the SRO to ensure a controlled and successful programme conclusion aligned to strategic goals.

The Business Change Manager (BCM) supports by confirming benefits status but does not hold closure authority.

This clarity in accountability prevents premature or inappropriate programme termination and ensures a thorough and accountable close-out process.

The Business Change Manager (BCM) reviews the Business Case to confirm that the plans for benefits realization are sound and achievable. The BCM ensures that the expected benefits are realistic, measurable, and aligned with the organization's strategic objectives.

The MSP Practitioner states: “BCMs will review it to confirm that benefit realizations have been handled correctly.” This review helps identify risks or gaps in benefit planning early, enabling corrective actions before programme progression.

While the SRO approves the Business Case and the Programme Manager produces it, the BCM’s critical role is to validate the benefits-related aspects, ensuring the programme can deliver its expected value effectively and sustainably.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Assurance Theme in MSP 5th Edition emphasizes that assurance should be risk-based and proportional. While independence is a success factor, the framework also recognizes that "internal" assurance—conducted by individuals with the right skills who are not the direct project managers—is a valid and necessary part of the assurance landscape.

In this scenario, the Programme Office Lead (who is a senior member of the portfolio office) is tasked with the health check. Option A is the correct answer because, within the MSP 5th Edition guidance, the Programme Office is responsible for providing standards, support, and "second-line" assurance. Even if the health check was not in the original Assurance Plan, MSP is designed to be flexible; an SRO has the authority to request ad-hoc assurance if they perceive a risk or need to understand the status of a transformation. The Programme Office Lead possesses the specialized knowledge of MSP processes and organizational standards to identify areas of concern. While an external auditor (third-line) offers more independence, the internal lead provides a cost-effective and immediate source of expertise to meet the SRO's needs. The key is that the person conducting the check must have the requisite skills to evaluate the programme against its defined governance and objectives, which a senior portfolio office member is expected to possess.

The Senior Responsible Owner (SRO) approves the Business Case and is accountable for ensuring it remains valid and aligned with strategic objectives.

The MSP Practitioner states: “SRO approves (as he is accountable for it).” This underscores the SRO’s critical role in governing programme justification and ensuring investment decisions remain sound.

While the Sponsoring Group may endorse or sponsor the programme, formal accountability and approval for the Business Case rest with the SRO, ensuring clear responsibility for delivery against agreed benefits.

This accountability helps maintain control and confidence in programme investment and delivery.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The 'Evaluate new information' process involves more than just checking budgets; it requires an assessment of the programme's "soft" elements, such as stakeholder engagement and the effectiveness of communication. The End-of-Tranche Report serves as a summary of the programme's health and readiness to proceed.

Option B is the correct answer. MSP 5th Edition emphasizes that for transformation to be successful, stakeholders must understand and accept the change. The fact that engineering staff view the changes as "minor" suggests a failure in the communication strategy or a lack of understanding of the Vision. By noting this in the end-of-tranche report, the Programme Manager is correctly identifying a weakness in the Knowledge Theme (specifically stakeholder communication) that occurred during Tranche 2. Evaluating the effectiveness of how information was shared and received is a key part of this process. This allows the programme to adjust its Stakeholder Engagement Approach for Tranche 3, ensuring that the engineering staff are properly prepared for the upcoming Training Project. Without this evaluation, the programme would risk low engagement and poor benefit realization in the next tranche. The report is the formal mechanism for capturing these "lessons learned" and turning them into actionable governance decisions for the future.

A Vision Statement is a succinct and compelling description of the desirable future state that the programme aims to achieve. It serves to inspire and align stakeholders around the intended outcomes and benefits. The MSP Practitioner outlines key characteristics of a Vision Statement, including that it must describe a desirable future and be concise to ensure clarity and focus.

Key benefits are often implicit within the Vision, providing a motivational overview without delving into detailed measurement or timelines.

However, the Vision Statement is NOT normally time-dependent. Time frames and milestones are introduced later in the programme planning stages, such as in the Business Case or Programme Plan. The MSP Practitioner explains: “Vision statement does not include time frames until programme is time bound in nature,” which means the Vision is more about 'what' will be achieved rather than 'when.'

This approach allows the Vision to remain stable even if timeframes or specific project plans evolve. The focus remains on the transformational goal, providing a constant reference point as the programme adapts to challenges and changes.

Therefore, including time-dependence in the Vision Statement could unnecessarily constrain the programme’s strategic focus or create misalignment if schedules shift.

Comprehensive and Detailed 200 to 250 words of Explanation From Exact Extract of project-programme-and-portfolio-management of 5th Edition MSP:

The Structure Theme in MSP 5th Edition defines how the programme is organized into tranches to manage the delivery of capability and the realization of benefits. While tranches provide a natural "step-by-step" progression, MSP 5th Edition is designed to be more flexible and agile than previous versions. It explicitly recognizes that tranches do not always have to be strictly sequential.

Option B is the correct answer. The guidance states that tranches can overlap if there is a clear business reason to do so—such as a change in priority or the early availability of resources—and if the risks of doing so are managed. Overlapping tranches allows the programme to "bring pace and value" (an MSP Principle) by initiating work as soon as it is feasible. While Option D raises a valid point about risk, MSP does not forbid overlapping; it simply requires that the risks be assessed. If the resources from the Customer Processes Project are now free, using them to start the Training Project early is a sensible management decision that accelerates the delivery of capability. The end-of-tranche review (Option C) still occurs for Tranche 2, but it does not prevent work from a future tranche from beginning if the SRO approves the deviation from the initial plan to maximize efficiency.