3.2 Senior Responsible Owner (SRO) & Programme Manager
Key Takeaways
- The Senior Responsible Owner (SRO) holds single-point accountability for the ultimate success or failure of the programme.
- The SRO owns the Programme Business Case throughout its entire lifecycle and is personally answerable for ensuring benefits realization.
- The Programme Manager provides operational leadership for programme delivery, coordinating the delivery plan, managing dependencies, and controlling schedule and cost tolerances.
- Accountability cannot be delegated: while the SRO delegates operational management authority to the Programme Manager, the SRO remains solely answerable to the Sponsoring Group.
- Effective collaboration between the SRO and Programme Manager requires transparent reporting, mutual trust, and clear exception escalation protocols.
3.2 Senior Responsible Owner (SRO) & Programme Manager
[!NOTE] Core Leadership Principle: In Managing Successful Programmes (MSP), leadership is structured around a clear distinction between accountability and responsibility. The Senior Responsible Owner (SRO) is solely accountable for whether the programme delivers its strategic objectives and projected benefits. The Programme Manager is responsible for the operational direction and day-to-day management of delivery.
The leadership tandem of the SRO and the Programme Manager is the critical axis around which all transformational activity revolves. If the SRO is absent or disengaged, the programme loses its strategic anchor and political protection. If the Programme Manager lacks delivery rigor, projects fall out of alignment, budgets hemorrhage, and dependencies collapse. Understanding their distinct boundaries, authorities, and collaborative workflows is vital for the MSP Foundation examination.
The Senior Responsible Owner (SRO): Single-Point Accountability
The Senior Responsible Owner (SRO) is the individual who holds ultimate, non-negotiable accountability for the programme. Appointed directly by the Sponsoring Group, the SRO is typically a high-level corporate director or executive with the organizational standing to drive enterprise-wide reform.
+-------------------------------------------------------------------------+
| Core Accountabilities of the SRO |
+-------------------------------------------------------------------------+
| • Single-point accountability for programme success or failure |
| • Formal owner of the Programme Business Case (from inception to end) |
| • Securing and protecting financial investment and capital allocations |
| • Chairing the Programme Board and setting strategic direction |
| • Appointing the Programme Manager, BCMs, and Programme Office Lead |
| • Setting delegated tolerances and authorizing tranche transitions |
| • Maintaining continuous alignment with corporate enterprise strategy |
+-------------------------------------------------------------------------+
Business Case Ownership and Value Realization
In MSP, the SRO owns the Business Case. This is not a ceremonial responsibility. The SRO must continuously ensure that:
- The investment remains commercially viable and affordable.
- Risks to benefits realization are actively mitigated.
- Strategic justification is validated at every tranche boundary review.
- If an external market disruption or strategic pivot renders the programme unviable, the SRO possesses the duty and authority to recommend early termination to the Sponsoring Group.
Governance Leadership and Key Appointments
The SRO does not manage daily project schedules. Instead, the SRO leads the governance machinery by:
- Appointing the Programme Manager, ensuring they possess the technical, commercial, and leadership capabilities required to coordinate the delivery plan.
- Appointing the Business Change Managers (BCMs), ensuring they command operational line authority in their respective business units.
- Appointing the Programme Office Lead, establishing an objective centre of control and governance support.
- Serving as the vital communication bridge between the executive Sponsoring Group and the delivery team.
The Programme Manager: Operational Delivery Leadership
The Programme Manager is appointed by the SRO to take operational leadership of programme delivery. While the SRO looks "outward and upward" to the corporate board, regulators, and strategic stakeholders, the Programme Manager looks "inward and downward" across the delivery plan, work streams, and programme team.
Core Responsibilities of the Programme Manager
- Planning and Scheduling Delivery: Formulates and maintains the overall Delivery Plan, integrating project schedules, quality checkpoints, transition gates, and tranche boundaries into a coherent timeline.
- Orchestrating the Delivery Plan: Directs, coordinates, and aligns multiple related projects. Allocates resources, resolves priority conflicts between project managers, and monitors project outputs.
- Managing Inter-Project Dependencies: Identifies and tracks critical cross-project dependencies (e.g., Project B cannot begin user acceptance testing until Project A delivers the core enterprise database schema).
- Controlling Schedule and Cost Tolerances: Tracks expenditure, burn rates, and milestone delivery against agreed baseline plans and delegated tolerances.
- Risk and Issue Management: Actively manages programme-level risks, maintains the Programme Risk Register, and drives mitigation strategies across all delivery workstreams.
- Leading the Programme Team: Establishes high-performance delivery standards, provides operational direction to Project Managers, and oversees internal and external supplier contracts.
- Highlight and Exception Reporting: Submits regular, objective Highlight Reports to the SRO, and promptly prepares Exception Reports whenever delivery tolerances are breached or forecast to be breached.
Contrasting Strategic Accountability vs. Operational Authority
A detailed comparison reveals the clear demarcation between the strategic role of the SRO and the operational execution role of the Programme Manager:
| Dimension | Senior Responsible Owner (SRO) | Programme Manager |
|---|---|---|
| Core Mandate | Champion the strategic vision, secure funding, and ensure organizational value creation | Deliver the new capabilities described in the Target Operating Model (TOM) |
| Accountability vs. Responsibility | Accountable for the overall success/failure of the programme and ROI | Responsible for the operational management, day-to-day coordination, and delivery of capabilities |
| Business Case | Owns the Business Case; signs off on all financial commitments and revisions | Inputs operational data (costs, timelines, technical risks) into the Business Case |
| Focus | Outward and upward (corporate strategy, executive board, enterprise politics) | Inward and downward (delivery plan, work package schedules, technical dependencies) |
| Decision Scope | Authorizes tranche transitions, approves scope re-baselines, approves major financial shifts | Allocates project resources, manages technical trade-offs, resolves cross-project scheduling conflicts |
| Programme Board Role | Chairs the Board; makes final executive determinations | Executive delivery member; presents progress, risks, and forecasts |
| Escalation Point | Escalates enterprise issues and tolerance breaches to the Sponsoring Group | Escalates operational breaches and cross-project deadlocks to the SRO |
| Time Horizon | Entire programme lifecycle plus long-term benefits tracking post-closure | Delivery tranches and current release horizon |
Collaborative Dynamics and Escalation Protocols
The relationship between the SRO and the Programme Manager cannot function as a rigid master-servant contract; it must be an active, high-trust partnership.
[ SRO: Strategic Direction ]
│ ▲
Delegated Authority Exception Reports &
& Resources Highlight Reports
▼ │
[ Programme Manager: Operational Delivery ]
The Trust and Transparency Imperative
- Psychological Safety and Bad News: The SRO must cultivate an environment where bad news travels quickly. If project delays, technical failures, or vendor disputes are hidden because of a punitive culture, the SRO cannot protect the Business Case.
- Avoiding Micromanagement: The SRO must respect the delegated tolerances granted to the Programme Manager. If the SRO interferes in daily project meetings or bypasses the Programme Manager to give direct instructions to Project Managers, the delivery chain breaks down.
- Formal Escalation Triggers: The Programme Manager must never "sit on" a looming crisis. As soon as empirical tracking indicates that project costs, milestone completion dates, or technical performance will breach agreed operational tolerances, an Exception Report must be submitted to the SRO with clear impact analyses and recommended options.
Real-World Scenario: Global Retail Banking Core Modernization
A multinational retail bank initiates a $320M Core Banking Modernization Programme to replace 30-year-old legacy mainframe accounts with a modern, real-time cloud architecture across 800 branches and digital channels.
- The SRO (Executive Vice President of Retail Banking): Secures board-level capital against intense shareholder scrutiny. Defends the multi-year Business Case during an economic downturn, securing continued investment by demonstrating that cloud migration will lower transaction processing costs by 45%. Appoints the Programme Manager and three operational BCMs (Branch Operations, Digital Channels, Compliance & Audit). When a cyber-security audit demands an unanticipated £15M encryption infrastructure upgrade, the SRO negotiates additional capital directly with the Sponsoring Group.
- The Programme Manager (Senior Director of Delivery): Leads 14 concurrent project teams (cloud infrastructure, database migration, API gateway, mobile app redesign, automated reconciliations). Coordinates critical dependencies—ensuring the cloud data lake is fully validated before the branch core engine switches over. When the core software vendor falls 8 weeks behind schedule, threatening the Tranche 2 release tolerance, the Programme Manager drafts an Exception Report outlining two recovery options (descoping legacy batch features vs. injecting specialist systems integration contractors) and presents it to the SRO for strategic decision.
Exam Tips & Common Traps
[!TIP] Business Case Ownership: A staple question on the MSP Foundation exam asks: "Who owns the Programme Business Case?" The correct answer is always the Senior Responsible Owner (SRO). The Programme Manager and BCM provide critical cost and operational data, but ownership and accountability remain solely with the SRO.
[!CAUTION] Common Exam Trap — The "Co-SRO" Fallacy: Exam scenarios may propose appointing two SROs (e.g., a Chief Technology Officer and a Chief Operating Officer) to share accountability on large technical programmes. In MSP, this is strictly forbidden. Accountability cannot be shared; there must be exactly one SRO to preserve single-point accountability.
[!WARNING] Common Exam Trap — Programme Manager Authority Over BAU: The Programme Manager's authority is confined to the delivery of capabilities within the programme. The Programme Manager does not possess line authority over operational business units and cannot force operational staff to change their daily working practices. That responsibility belongs strictly to the Business Change Manager (BCM).
In Managing Successful Programmes (MSP), who holds ultimate single-point accountability for ensuring that the programme meets its strategic objectives and delivers its projected business benefits?
Which specific responsibility falls directly within the remit of the Programme Manager rather than the Senior Responsible Owner (SRO)?
During a major enterprise transformation, a primary software integration vendor informs the delivery team that unexpected complexities will cause project costs to exceed agreed programme budget tolerances. What is the required course of action?