MSP-Practitioner MSP Practitioner, 5th edition Exam Questions and Answers

Blueprint, Vision, and Quality Management Strategy are core parts of MSP’s Governance Themes. These documents set the strategic direction, define the future state, and establish quality control frameworks, respectively.

The MSP Practitioner notes: “Blueprint, Business Case, Vision, Quality management are governance themes,” though the Business Case and Programme Mandate also play governance roles, the listed group in option A is most directly related to governance themes that provide control and assurance.

These documents form the backbone of programme governance by setting expectations, standards, and guiding principles that ensure the programme remains aligned with corporate strategy and delivers value effectively.

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

The principle of 'Collaborate across boundaries' in MSP 5th Edition emphasizes that programmes are often cross-functional and involve a diverse range of stakeholders, both internal and external to the organization. This principle acknowledges that the outcomes and benefits of a programme are rarely achieved in isolation. To be successful, a programme must break down silos and engage with the broader ecosystem, which includes partners, suppliers, regulators, and even competitors where appropriate.

In this scenario, UU is proactively engaging with the external regulator (DOUO) and other water companies. This is a direct application of collaborating across boundaries because it seeks to build a collaborative environment to solve a shared industry challenge—ensuring fair competition. Option B is correct because the essence of this principle is about involving the "right stakeholders" to ensure that the environment in which the programme operates is supportive of its goals. By working with the regulator and other companies, UU is ensuring that the policies and solutions developed are practical and inclusive, rather than being imposed externally. This collaboration reduces the risk of future regulatory intervention that could derail the programme's success. While internal collaboration (Option D) is part of the principle, limiting it to internal departments would be an incorrect and narrow interpretation of the MSP framework, which specifically encourages looking outward to the wider context of the programme.

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.

The Issue Register is a Management document, which captures, categorizes, and tracks issues arising during programme delivery. Management documents guide day-to-day operational activities, providing information and control mechanisms necessary for managing programme progress and risks.

According to the MSP Practitioner, “All plans, issue register and Risk register are management documents.” The Programme Brief and Programme Mandate are boundary documents that set scope and governance parameters, while the Project Dossier is used to manage individual projects.

The Issue Register supports decision-making and issue resolution, helping maintain programme momentum and ensuring emerging problems are effectively addressed and escalated as required.

Media is classified as an influencer stakeholder type because it can shape public opinion and stakeholder perceptions, thus affecting programme success indirectly.

The MSP Practitioner notes: “Media can influence other stakeholders as well,” highlighting its role in communication and shaping the narrative around the programme.

Understanding and managing influencer stakeholders like media is critical for reputation management, gaining public support, and mitigating risks associated with negative publicity.

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 'Justification' and 'Benefits' themes emphasize that benefits must be measurable and expressed in a way that allows for objective assessment of the programme's value. When a CFO requests a Net Present Value (NPV) calculation, they are looking for a financial representation of the programme's worth. NPV is a financial metric used to represent the value of future cash flows in today's terms. Therefore, the benefits feeding into this calculation must be expressed in financial terms.

Option B is the correct answer because "cost savings" are tangible, financial benefits that can be directly used in an NPV calculation. In the context of the UU scenario, HR efficiencies leading to reduced staff costs provide a direct cash-flow impact. While Option C (additional sales) is also financial, it is often more speculative than cost savings. Option D uses a "cash proxy," which is a technique used in MSP to assign a monetary value to non-financial benefits (like customer satisfaction), but since the scenario specifically mentions HR efficiencies and cost-saving metrics are already available, a direct financial measure is preferred for a formal NPV. Option A is incorrect because non-financial measures (like brand reputation) cannot be directly included in an NPV formula without conversion. MSP 5th Edition stresses that the Business Case must be supported by a robust Benefit Realization Plan where financial benefits are clearly quantified to justify the investment.

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

MSP 5th Edition advocates for the use of different delivery life cycles depending on the nature of the work. While some projects are best suited to a "linear" (waterfall) approach, others benefit from incremental or continual improvement (agile) approaches. Continual improvement is particularly effective when the outcome can be delivered in stages, allowing for feedback and refinement at each step.

Option D is the correct answer because the physical rollout of smart meters is a repetitive process that provides numerous opportunities for learning. By "installing new water meters gradually," the programme can apply lessons learned from the first set of installations to the next, improving efficiency, customer communication, and technical reliability as the rollout progresses. This is the essence of the Plan-Do-Check-Act (PDCA) cycle within the transformational flow.

Option A (legal/contractual) usually requires a discrete, linear completion.

Option B (IT systems) often requires complex integration that might be incremental but is less about "continual improvement" of a repetitive rollout.

Option C is a R&D/product development activity.

Option D represents the best fit for an iterative, learning-based approach where the pace and quality of delivery are refined based on real-world operational feedback.

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.

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.

Action

Role

Provide expertise in UU's programme scheduling software

Programme office lead

Develop the process for procuring external trainers

Programme manager

Approve the process for assigning internal staff to the programme

Senior responsible owner

The Programme Office provides the technical "best practice" and tool expertise (scheduling software). The Programme Manager designs the management processes for delivery (procurement). The SRO approves the overarching governance and resource allocation rules.

The Business Change Manager (BCM) holds the primary responsibility for monitoring the progress of benefits realization against the plan. This role is focused on ensuring that the expected benefits from the programme’s outputs and outcomes are actually realized in the business environment. The BCM works closely with stakeholders, operational managers, and programme teams to track benefit achievement, resolve issues that might impede benefit delivery, and report progress.

According to the MSP Practitioner: “BCM is responsible for monitoring benefits.” This accountability includes validating that the changes introduced by the programme are embedded within business operations and are delivering measurable value as outlined in the Benefits Realization Plan. The BCM must maintain a clear line of sight on benefits, manage dependencies between projects and operational teams, and oversee any transition activities required to sustain benefits.

The Programme Manager and Senior Responsible Owner (SRO) have broader accountability for programme delivery and governance, but it is the BCM who acts as the day-to-day custodian of benefits. They translate strategic benefit objectives into operational terms and ensure the organisation adapts to new ways of working. This ensures that benefits do not remain theoretical but are tangibly realized, measured, and maximized over time.

Effective benefits monitoring by the BCM mitigates the risk of programmes delivering outputs that do not translate into business improvements or strategic value, reinforcing MSP’s emphasis on outcome-focused delivery.

Statement

Document

It is assumed that the Utility Oversight regulator will not introduce a policy that caps prices to reduce the overall profitability of the programme

Business case

For each option considered, an estimate of the initial cost of operation was calculated

Programme brief

10-15% increase in gas and electricity customers; assuming that market research analysis is indicative of future performance

Financial plan

Strategic assumptions that underpin the financial viability of the investment belong in the Business Case. High-level options analysis and initial costings are features of the Programme Brief developed during 'Identify the Programme'. Specific growth targets and their financial impact are managed within the Financial Plan

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.

Recruitment Policy is not considered a critical organizational element in MSP, whereas Delivery Mechanism for Change, Business as Usual, and Corporate Strategy are recognized as essential elements.

The MSP Practitioner states: “All other are critical organizational elements,” highlighting that MSP focuses on how organizations govern and implement change (delivery mechanisms), maintain ongoing operations (business as usual), and set strategic direction (corporate strategy).

Recruitment policies, while important HR tools, are not part of the critical organizational elements that MSP emphasizes in programme governance and transformational change management.

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

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 Assurance Theme is critical for providing the SRO and the Sponsoring Group with confidence that the programme is on track and being managed effectively. For assurance to be truly effective and reliable, it must adhere to several "success factors." One of the most vital factors is Independence.

Independence in assurance means that the person or team conducting the review is not directly involved in the delivery or management of the programme they are auditing. This lack of bias ensures that the findings are objective and that the "true" status of the programme is reported without fear of internal repercussions or a desire to hide failures. By recruiting an external consultant to perform the health check, the Programme Office Lead is ensuring that the review is conducted by an entity that is entirely separate from the programme’s internal politics and day-to-day operations. This satisfies the requirement for "third-line" assurance in the MSP framework. While internal audits (second-line) are valuable, external reviews provide the highest level of independence. This process gives the new SRO an impartial baseline of the programme’s health, enabling them to make informed decisions about future tranches without relying solely on potentially optimistic reports from the delivery team.

Decision Item

Document

Each project will have a change control authority... up to £5,000. Above this level... referred to a programme authority... over £10,000 to the CEO/CFO

Programme strategy: Decision-making approach

There is a low likelihood that legislation may be passed that allows customers to immediately switch utility providers without penalty

Risk register

'Return on investment' will be used at the programme level as the basis for calculating the profit or loss generated in relation to money invested

Decision register

Setting monetary thresholds for escalation and delegation is a "Decision-making approach" activity. Legislative uncertainty with a probability and impact is a Risk. Documenting the specific criteria or "basis" used for previous or current decisions belongs in the Decision Register.

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 Decisions Theme requires that all significant choices regarding the programme’s direction be made based on a structured analysis of options. This is particularly crucial during the 'Design the outcomes' process, where the Target Operating Model and technical solutions are defined. The framework dictates that for any major decision, the programme team must provide the decision-makers (usually the SRO or Programme Board) with a range of choices to ensure that the best balance of cost, risk, and benefit is achieved.

Option D is the correct answer because MSP 5th Edition explicitly states that an options analysis should typically include:

A "do-nothing" option: This provides a baseline to understand the impact of not proceeding or not changing the current path.

At least two other viable options: This ensures that the board is not "cornered" into a single recommendation (as seen in the scenario) but can weigh different trade-offs.

By only presenting the imported meter option, the R&D team is not allowing the SRO to evaluate whether internal development (despite being slower) might mitigate the security risks mentioned. Presenting multiple options is a safeguard against "groupthink" and ensures that the final decision is robust, well-justified, and aligned with the organization's risk appetite. Providing only one recommendation violates the transparency and rigor required by the MSP Decisions theme.

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 Knowledge Theme in MSP 5th Edition covers both explicit knowledge (documented data) and tacit knowledge (experience, insights, and "know-how"). A successful programme must capture tacit knowledge from those who are closest to the operational reality and convert it into a form that can improve the programme’s outputs. This is often achieved through collaborative techniques like workshops.

In this scenario, the Business Change Manager (BCM) is facilitating the transfer of tacit knowledge from the call centre managers to the supplier, Web ’n’ Go. Option A is the correct answer because this application of the knowledge theme ensures that the technical solution (the portal) is informed by real-world operational insights. By understanding common customer problems, the supplier can design features that directly address those pain points, thereby increasing the likelihood of customer adoption and the realization of benefits (such as reduced call volumes). This proactive knowledge sharing is a critical part of the Design Approach within the Knowledge theme, ensuring that what is "built" is fit for purpose. While sharing info with external companies (Option D) requires security protocols, the principle of using operational knowledge to drive design remains a core MSP best practice.

A vision-led programme is one that is undertaken to fulfil political ideas and priorities, such as electoral promises. These programmes are driven by a clear vision for change that aligns with political or societal goals rather than just compliance or operational needs. Public programmes started to fulfil electoral promises fit this definition of vision-led programmes as they reflect a vision for future societal outcomes.

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.

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

The 'Deploy diverse skills' principle in MSP 5th Edition emphasizes that programme management requires a specific set of capabilities that are different from project management or business-as-usual (BAU). This principle states that a programme must have access to the right people, with the right skills, at the right time. This often involves a blend of internal staff who understand the organizational culture and external experts who bring specialized knowledge or "best-in-class" technical skills that may not exist within the organization.

The SRO’s decision to use only internal staff purely to minimize costs, despite evidence that external experts would provide a higher quality solution and better adoption, is a violation of this principle. Option D is correct because MSP specifically guides that the focus should be on achieving the outcomes of benefit. If the lack of specialized skills leads to a lower quality solution or poor adoption, the programme's benefits are at risk. The principle of 'deploying diverse skills' encourages looking beyond cost to ensure the capability delivered is fit for purpose. While building internal skills (Option B) is a secondary benefit of programmes, it should not come at the expense of the programme's ability to successfully deliver its primary transformational objectives. The SRO's role is to ensure the programme is set up for success, which includes securing the necessary expertise to realize the vision.

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

The principle “Envisioning and communicating a better future” specifically addresses the need for creating a clear, compelling Vision. The MSP Practitioner states: “Envisioning and communicating a better future categorically takes the need of creating an effective Vision statement.” This principle ensures that the programme has a forward-looking, inspirational view of the outcomes and benefits, which guides all programme activities and stakeholder engagement efforts. The Vision helps to align everyone involved and drives commitment towards the desired future state.

The Vision document is prepared specifically to share with stakeholders to communicate the desired future state the programme aims to achieve. It is a clear, inspirational statement designed to create alignment, motivation, and understanding among all parties involved.

The MSP Practitioner states: “Vision's purpose is to share the idea of better future planned by programme with all stakeholders.” It conveys the strategic intent and overarching goals without delving into technical or detailed delivery plans.

Unlike the Business Case or Blueprint, which are more technical or internal management documents, the Vision serves as a powerful communication tool fostering stakeholder engagement and support from the outset.

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 principle of 'Align with priorities' in MSP 5th Edition dictates that a programme must remain consistent with the strategic direction of the organization, which is often subject to change due to internal or external factors. This principle ensures that the programme continues to deliver value and remains viable throughout its lifecycle. A critical component of this alignment is the Target Operating Model (TOM), which describes the future state of the organization once the programme's outcomes are embedded.

In this scenario, the CFO provides updated financial and market realities suggesting that previous growth targets were unrealistic. By updating the target operating model, the Programme Manager is ensuring that the vision of the "future state" remains realistic and aligned with the revised organizational priorities. According to MSP guidance, the TOM is not a static document created at the start and then shelved; it must be refined as the programme progresses and as the corporate context evolves. Option A is correct because it acknowledges the iterative nature of the TOM. While benefits (Options C and D) will certainly be affected, the question asks about the application of the principle to the TOM update. Ensuring the TOM reflects current strategic reality is a primary way to maintain alignment with organizational priorities, preventing the programme from delivering a future state that the business no longer desires or cannot sustain.

Analysis of the options available is not typically included in the Programme Brief but is developed during the preparation of the Business Case.

The MSP Practitioner clarifies: “Analysis of options starts while preparing business case,” meaning the Programme Brief sets out the scope, risks, costs, and key resources but does not contain detailed option appraisal.

This distinction helps ensure the Programme Brief remains a focused and concise document outlining programme intent and governance, while the Business Case undertakes the detailed financial and strategic evaluation required for decision-making.

Outcomes are defined as the new operational state achieved after the transition of capability into live operations. They represent the changes in the organization’s way of working resulting from the combined effect of project outputs.

The MSP Practitioner states: “Outcomes are combined outputs or projects to bring a new operational state in organization,” emphasizing that outcomes go beyond deliverables to reflect actual changes in operations and behaviours.

This distinction is critical in MSP’s focus on transformational change, ensuring programmes deliver real, sustainable benefits rather than just outputs.

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

The Plan-Do-Check-Act (PDCA) cycle is applied throughout MSP to ensure continuous improvement and effective risk management. In the context of risk management, the 'Plan' phase involves identifying and assessing risks, understanding the current environment, and designing the appropriate responses. It is the analytical stage where the programme team gathers data to understand the scale and proximity of a threat to the programme’s benefits.

In this scenario, the risk is a shift in market preference toward green energy. Option B is the correct activity for the 'Plan' phase because it involves research and analysis. Before a response can be designed (Do), the programme must understand the market trends and the potential impact on the cross-selling benefits. Analyzing how many customers competitors are gaining through green energy provides the evidence base needed to adjust the Business Case or the Benefit Profiles. In contrast, Option D represents the 'Do' phase (implementing a response), Option A represents the 'Check' phase (monitoring results), and Option C is also a 'Check' or 'Act' activity to verify the effectiveness of a response already taken. For the 'Plan' phase, the focus remains on understanding the uncertainty to enable informed decision-making.

The false statement here is that the SRO acts as the Project Executive on all the Project Boards. The MSP Practitioner explicitly clarifies that the SRO does not take on this project-level responsibility. Instead, the SRO’s role is to provide overall accountability for the programme and to ensure the programme delivers its intended outcomes and benefits.

The SRO holds a senior position with enough authority to make decisions and secure resources and is typically a peer of the Sponsoring Group to ensure alignment with corporate strategy. The Sponsoring Group appoints the SRO to oversee the programme’s governance and delivery effectively.

Project Executives, in contrast, represent individual projects within the programme and report to the SRO via the programme governance structure. They focus on delivering specific project outputs, while the SRO’s responsibility is to coordinate these efforts to achieve strategic benefits.

This distinction is vital to MSP’s governance architecture: it prevents the SRO from being burdened with operational project detail, allowing focus on strategic oversight, stakeholder engagement, and benefit realization.

The MSP Practitioner states: “SRO doesn’t act as a project representative,” underscoring the clear division between programme and project governance to maintain effective control and leadership throughout the programme lifecycle.

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 occurs at the end of each tranche (and continuously throughout) to assess whether the programme remains viable and aligned with its objectives. This process involves reviewing performance, risks, and external opportunities that could impact the business case or the target operating model.

In MSP 5th Edition, the Programme Manager is responsible for the setup and day-to-day management of the programme, which includes the analysis of factors that might require a change in direction. Option B is correct because the Programme Manager is tasked with evaluating the impact of such new information—in this case, a new supplier offering a faster, cheaper alternative—on the overall programme plan and the project delivery schedule. The Programme Manager performs the detailed analysis and then presents the findings and recommendations to the Senior Responsible Owner (SRO) for a final decision. While the SRO is the ultimate decision-maker, the responsibility for the evaluation of technical and management information resides with the Programme Manager. They must determine how this new "imported" solution affects dependencies, costs, and the realization of benefits before the SRO decides whether to pivot the strategy for Tranche 3.

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

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.