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

A key attribute for a Programme Manager is a good knowledge of project management approaches. This expertise enables the Programme Manager to oversee and coordinate multiple interrelated projects, ensuring they deliver outputs that collectively realize programme objectives.

The MSP Practitioner states: “Programme Manager should have good project management skills,” emphasizing that while strategic leadership and stakeholder engagement are important, the ability to manage the complexities of project delivery is fundamental to the Programme Manager role.

While change management skills and access to key stakeholders are important complementary abilities, the core responsibility of managing project delivery across a dossier of projects necessitates strong project management knowledge. The Programme Manager acts as the bridge between strategic programme objectives and tactical project execution, requiring detailed understanding of project methodologies, risk management, scheduling, resource coordination, and quality assurance.

This knowledge supports effective integration, issue resolution, and benefits delivery, positioning the Programme Manager as a central figure in programme success.

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.

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 encourages innovative and effective ways to facilitate learning and knowledge transfer. The framework recognizes that for complex organizational change to "stick," the people involved must not just receive information but actually engage with it and internalize it. Using interactive elements, such as gamification or collaborative workshops, is a recognized method for stimulating creativity and fostering a learning culture.

Option C is the correct answer. The CEngO’s request to remove the games based on a perception of them being "childish" ignores the psychological benefits of interactive learning. Games and simulations can help even highly experienced staff members explore new processes in a safe environment, share their own tacit knowledge, and identify potential flaws in the proposed future state. According to MSP guidance, the goal of knowledge management is to maximize the organization's capability to change. If the games are designed to help engineers "share ideas and experiences," they are serving a vital role in knowledge sharing. Removing them solely based on an assumption of the staff's reaction—without testing the effectiveness of the training—is contrary to the MSP's focus on evidence-based improvement and effective stakeholder engagement.

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

The 'Deal with ambiguity' principle in MSP 5th Edition recognizes that programmes operate in evolving environments where not all information is known at the outset. This principle requires programme teams to acknowledge uncertainty and proceed with the best available information, rather than waiting for absolute certainty, which may never come. Ambiguity often stems from external factors, such as potential regulatory changes, which are outside the programme’s direct control but can significantly affect its viability.

In this scenario, the potential for a "fair pricing policy" is a classic example of ambiguity during the 'Identify the programme' process. By including this information in the programme brief, the Programme Manager and SRO are surfacing a critical uncertainty early. Option A is the correct answer because the primary purpose of identifying such ambiguity at this stage is to enable the Sponsoring Group to make an informed "invest/no-invest" decision. The programme brief is designed to provide enough information to justify moving to the more detailed 'Design the programme' stage. If the Sponsoring Group is unaware of this potential impact on benefits, they cannot accurately assess the programme's value or risk profile. Ignoring the ambiguity until a formal risk process is established (Option C) would be a failure of this principle, as MSP encourages proactive transparency regarding what is unknown or uncertain from the very beginning of the transformational flow.

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:

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

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.

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 Project Brief is a key document that describes the purpose, cost, time, performance requirements, and constraints of a specific project. It acts as the initial detailed definition of a project within the programme context. The MSP Practitioner states: “Project brief describes purpose, cost, time, performance requirements and constraints of a project,” highlighting its role in defining project scope and parameters, which supports effective project delivery aligned to the programme objectives.

Both the Business Change Manager (BCM) and the Programme Manager share responsibility for aligning projects with benefits realization. The MSP Practitioner highlights that “Both roles are responsible for this task as projects are overseen by programme manager, and benefits are under BCM supervision.”

The Programme Manager ensures that project outputs are delivered on time, within scope, and aligned to programme objectives, while the BCM ensures that these outputs translate into tangible benefits once transitioned into operational use.

This dual responsibility ensures seamless coordination between delivery and realization functions, bridging the gap between project outputs and strategic outcomes. Without this collaboration, there is a risk of projects delivering outputs that fail to produce the intended business improvements.

Together, the Programme Manager and BCM form a critical partnership in MSP’s approach to ensuring benefits are fully realized, tracked, and maximized throughout and beyond the programme lifecycle.

The critical organizational elements in MSP include Corporate strategy, Delivery mechanisms for change, and the Business as usual environment. Delivery mechanisms for change refer to the structures and processes organizations use to implement and manage changes introduced by programmes. These elements are foundational to effective governance and ensure alignment with strategic objectives. Other options like Leading change and Stakeholder engagement are important but classified differently within MSP's framework.

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 dis-benefit is defined as a measurable decline resulting from an outcome perceived as negative. The MSP Practitioner clearly states: "Measurable decline resulting from outcome perceived as negative defines mis-benefit," highlighting the need to manage and mitigate dis-benefits as part of benefits management to ensure overall programme success.

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.

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

The 'Design the outcomes' process is where the high-level vision is translated into a detailed Target Operating Model (TOM) and a Benefit Framework. Once the vision is validated, the next logical step in the MSP transformational flow is to begin detailing the benefits that the new state will provide.

Option B is the correct answer because it focuses on quantifying the benefits—specifically the "increased customer numbers." Before scheduling resources (Option C) or refining risk registers (Option A), the Business Change Manager (BCM) and the Programme Manager must work with the business (the call centre managers) to define what success looks like in measurable terms. This involves creating Benefit Profiles. By holding a workshop to confirm these numbers, the BCM ensures that the benefits are realistic, owned by the business, and directly linked to the validated vision. This step is crucial for the Justification Theme, as it provides the evidence needed to build the detailed Business Case. In MSP 5th Edition, the "benefits-led" nature of programmes means that defining the measurable improvements is a top priority once the desired future state (the vision) is understood. Only after these benefits are clearly identified and documented can the programme effectively plan the delivery of the capabilities required to achieve them.

All the listed groups are valid stakeholders in a city-building programme. MSP recognizes that stakeholders can be diverse, including internal groups like employees, external political leadership, and the wider community such as potential residents.

The MSP Practitioner notes: “All are valid stakeholders in programme,” emphasizing the importance of identifying and engaging a broad spectrum of stakeholders to ensure programme success.

Inclusive stakeholder management supports better decision-making, risk mitigation, and benefits realization by addressing varied needs and expectations across the stakeholder landscape.

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

The 'Align with priorities' principle ensures that the programme structure and its resources remain focused on the current needs of the business as it moves through the transformational flow. The Organization Theme supports this by ensuring that the right people are in the right roles at the right time. Unlike project management roles, MSP roles—specifically the Business Change Manager (BCM)—can and should change as the programme moves between tranches.

In this scenario, Tranche 2 likely involves technical or systems-led changes (indicated by the appointment of the Chief Technology Officer as BCM). Option C is the correct answer because the BCM’s primary responsibility is to bridge the gap between the programme and the business operations to ensure that outcomes are delivered and benefits are realized. By changing the BCM to reflect the specific focus of Tranche 2, the programme ensures that the person with the most relevant operational authority and "priority" alignment is leading the transition. This flexibility is a core strength of the MSP framework, allowing the programme to adapt its leadership to the specific nature of the work being performed in different stages of the lifecycle.

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.

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

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.

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

The Design Theme in MSP 5th Edition focuses on defining the "future state" and the path to get there. This involves the Vision, the Benefit Map, and the Target Operating Model (TOM). However, the design is not fixed; it must be open to improvements that enhance the programme’s value. In risk management, a "risk" can be either a threat or an opportunity.

In this scenario, the new technology represents an opportunity—an uncertain event that would have a positive impact on objectives (reducing maintenance costs). Option A is correct because adding this opportunity to the risk register allows the programme to evaluate whether it should be "exploited" or "enhanced." This is a correct application of the Design Theme because it relates to a potential change in the technical design of the programme's output (the smart meters) to deliver better value. By recording it in the risk register, the programme manager ensures it is formally assessed for its impact on the TOM and the Business Case before being incorporated into the design.

The Programme Brief is developed from the Programme Mandate and serves as a foundational input to the Business Case. It contains the programme objectives and expected outcomes, which the Business Case further elaborates. The MSP Practitioner states: “Programme brief contains objectives and outcomes of programme which is further enhanced in Business case.” This positions the Programme Brief as a bridge between initial mandate and detailed justification for the programme.

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.

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.

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.

Basic governance arrangements, including programme controls, are established during the 'Identifying the Programme' phase. These initial controls set the foundation for how the programme will be governed, including accountability structures, reporting lines, and approval mechanisms.

The MSP Practitioner states: “Basic governance arrangements to be used in Defining a programme are prepared in identifying a programme,” emphasizing the importance of establishing governance early to guide subsequent programme phases effectively.

Establishing these controls upfront ensures clarity, reduces ambiguity, and provides a framework within which the programme can operate with discipline and alignment to strategic goals.

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

The Design Theme in MSP 5th Edition is not limited to the technical architecture of the solution; it also encompasses the design of the delivery approach and the path to the future state. According to the MSP 5th Edition guidance, during the 'Design the outcomes' process, the programme must determine the most effective lifecycle for its constituent projects and workstreams. This involves deciding whether a linear, iterative (agile), or hybrid approach is most suitable for the nature of the change.

In this scenario, UU's decision to trial an agile approach is a fundamental design choice. Option D is the correct answer because the Design Theme is responsible for defining how the programme will transition from the current state to the target operating model. By choosing an iterative approach, the programme is "designing" the work to allow for rapid feedback, flexibility, and incremental value delivery. While this decision involves a "choice" (Option B), the MSP framework specifically categorizes the selection of delivery methodologies and lifecycles under the Design Theme because it shapes the entire strategy for how the outcomes will be realized. This alignment ensures that the delivery method matches the complexity and uncertainty of the programme's objectives, which is a key requirement of the Design Theme's focus on creating a viable and effective blueprint for transformation.

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.

The Benefits Map is categorized as a Boundary document. Boundary documents define the programme’s scope, constraints, and interfaces with its environment, helping to establish what the programme will deliver and what lies outside its remit.

The MSP Practitioner explains: “Benefits Map is a Boundary document while others such as programme preparation plan, risk register, and stakeholder profiles are management documents.” The Benefits Map visually depicts how outputs connect to outcomes and benefits, defining the boundary between delivery and benefits realization.

Boundary documents provide critical clarity for managing expectations, preventing scope creep, and ensuring alignment with strategic objectives, forming a foundation for programme governance and control.

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 Programme Strategy is a high-level document that outlines how the programme will be directed and managed. One of its vital components is the Design Approach. This section defines how the programme will design its future state, which includes the development of the Vision Statement and the Target Operating Model (TOM). The design approach specifies the methods, tools, and consultative processes (such as workshops) that will be used to ensure the design is robust and meets the strategic objectives.

The statement regarding the facilitated workshop for developing and testing the vision statement is a procedural detail of the "design" phase of the programme. Option C is correct because the vision statement is the cornerstone of the programme's design; it describes the "post-transformation" world. Therefore, the methodology for creating it—including who is involved (senior officers) and who approves it (CEO)—belongs in the Design Approach. While this involves stakeholders (Option B) and decisions (Option D), those are broader themes. The specific activity of forming the vision is a design activity. The Design Approach ensures that there is a structured way to move from the initial mandate to a clear, agreed-upon vision that guides all subsequent tranches and projects.

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.

Designing the Projects Dossier is a key activity in the 'Defining a Programme' process. The Projects Dossier is a comprehensive document that defines all the projects within the programme, detailing their scope, objectives, interdependencies, and delivery approach.

The MSP Practitioner states: “Only project dossier is created in defining programme from available options,” emphasizing that managing transition, producing the Programme Brief, and aligning projects with benefits realization occur in later programme stages.

Developing a well-structured Projects Dossier is critical for effective programme planning, control, and coordination of project delivery to achieve overall programme benefits.

The Benefits Map is typically created during the 'Defining a Programme' phase of the transformational flow. This map visually links programme outputs to expected benefits and outcomes, providing a clear picture of how the programme’s work will realize its intended value.

The MSP Practitioner explains: “Benefits are identified and analyzed in Defining a programme,” which highlights that the Benefits Map is a key planning tool used to understand dependencies, confirm benefit ownership, and ensure alignment with strategic objectives before detailed delivery begins.

Creating the Benefits Map at this stage supports informed decision-making and prioritization, as well as effective communication with stakeholders about how change initiatives contribute to strategic goals. It also serves as a baseline for benefits realization planning and tracking throughout programme delivery.

By defining and mapping benefits early, the programme can mitigate risks of misalignment or overlooked benefits, thereby improving chances of successful transformation and measurable value creation.

The Sponsoring Group, not the SRO, is accountable for confirming the Programme Mandate. The MSP Practitioner clearly states: "The Sponsoring Group is accountable for confirming the mandate," which means the SRO oversees delivery but does not hold responsibility for initial mandate confirmation. Meanwhile, the Programme Manager has ownership of the Vision Statement and Blueprint, aligning with delivery responsibilities.

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

The 'Plan progressive delivery' process is where the detailed plans for the tranches and projects are finalized, and the financial requirements are clarified. This process bridges the gap between the initial design and the start of actual delivery. One of the final and most critical activities in this process (and indeed in most MSP processes) is 'Agree to proceed (or close)'.

In MSP 5th Edition, the Senior Responsible Owner (SRO) holds the ultimate authority to commit the organization to the investment. While the Programme Manager develops the recommendation for funding sources during the planning activities, the SRO must formally approve the entire package of plans, the budget, and the funding strategy before the programme can move into the delivery tranches. Option D is the correct answer because this specific activity represents the "gate" at the end of the planning process. By "agreeing to proceed," the SRO is providing the final authorization for the financial arrangements and the overall delivery strategy. This ensures that the SRO is fully satisfied with the justification and the resource commitments before any significant expenditure begins in Tranche 1. It is a fundamental governance checkpoint that ensures the SRO remains in control of the programme's viability and strategic alignment.