GCS Programme Proposed New Governance Approach

1
GCS Programme Proposed New Governance Approach
eHealth Programme Board 12 November 2007 Lynda G
Lawson David Paton Version 1.0
2
Version History
3
Introduction

• This presentation outlines the actions taken in
  response to the ISIS Review of Generic Clinical
  System Toolset that confirmed a number of
  requested changes to GCS arrangements.
• The findings of the ISIS report can be summarised
  as falling into the following broad categories
• Programme Governance
• Technical Strategy and,
• Change Benefits Management.
• This presentation provides an initial overview of
  all actions being undertaken by the Programme and
  then focuses on the proposed new Programme
  Governance model, for your approval.

4
GCS ProgrammeAction Plan
Define
Define Review
Define Agree
Processes Resource
Define Release
Technical Viability
Establish Repository
Deliverables Available
Proposal Agreed
Proposal Agreed
Defined Agreed
Roll-out to all projects
Approach Agreed
1st Draft
Negotiation Strategy Agreed
Company Review
Strategy Agreed
Implementation
Approach Defined
Approach
Reviews
Action Plan
Review
Implement
Approach Defined
Define Review
Implementation
Define Agree Approach
5
Technical Strategy

• GCS Review Recommendations can be summarised as
• a clear strategy on the use, hosting, costing and
  joint development of the GCS Toolkit
• the need for revised contractual arrangements
  with Axsys, AOA and potentially a third party
  support and/or development partner to be put in
  place and,
• agreement on the above across the Boards.
• In response, a plan is being actioned that is
  bringing together Boards, Suppliers, eHealth
  Architecture and Design Authority and the central
  GCS team to establish a clear technical strategy
  for the GCS Toolkit. Once available this strategy
  will inform the contractual redefinition process,
  where applicable.

6
Communications and Benefits Mgmt

• GCS Review Recommendations can be summarised as
• re-invigoration of communications on GCS
• revision of the benefits realisation approach
  and,
• review of the original Business Case to assess
  the key drivers and costs for future development
  of the GCS Toolkit.
• In response, a plan is being actioned to address
  each of these recommendations. The initial focus
  of this plan is on supporting the new Programme
  Board through the delivery of a revised
  Communications Strategy and Benefits Management
  approach, which is consistent with the approach
  being adopted by the eHealth Programme.

7
Programme Governance Recommendations

• 2.2 It is essential for the success of any
  programme to create governance structures that
  enable clear and effective decision making to
  ensure that correct decisions are made swiftly,
  in line with business strategy and tied to
  business benefits. It is also essential to ensure
  the programme has dedicated, ring-fenced,
  funding, overseen by the Programme Board.
• 2.3 The Review Team believes that there is some
  confusion over the role, responsibilities and
  remit of the existing project board. While each
  application development constitutes a separate
  project, governance should more appropriately be
  carried out by a programme board.

8
GCS Programme Governance Model
9
GCS Programme
GCS Programme Board
GCS Project Boards
GCS External Suppliers
GCS Programme Management Team
Clinical Advisory Group
Technical Advisory Group

• Key Responsibilities
• Report on Programme performance
• Oversight of Significant /Major Projects
• Lead Benefits Mgmt and Change Control processes
• Manage Project Prioritisation process
• Lead external supplier management process
• Controls GCS Programme finances
• Escalates issues to Prog. Board, as required

• Key Responsibilities
• Agree of Technical Strategy (Solution
  Architecture)
• Agree GCS Release plan
• Deliver Technical Benefits
• Monitor external supplier delivery
• Contribute to Project prioritisation process
• Contribute to Change Control process
• Advise GCSPB on Technical matters
• Liaison with eHealth ADA

• Key Responsibilities
• Agree GCS Release plan
• Monitor Clinical Benefits delivery
• Lead the Project Prioritisation process
• Contribute to Change Control process
• Advise GCSPB on clinical matters

Contractual Negotiations
Communications
Drive GCS Utilisation Standardisation
10
GCS Key Responsibilities
GCS Programme Board
GCS External Suppliers
GCS Project Boards

• Key Responsibilities
• Ensure adherence to eHealth Programme goals
• Promote GCS usage standardisation
• Govern the Project Portfolio Prioritisation
  process
• Govern Change Control process
• Govern Supplier Management process
• Govern GCS Benefits Delivery process
• Approve GCS Programme communications
• Review Budgetary requirements
• Review Risks and Issues

• Key Responsibilities
• Contribute to Change Control process
• Contribute to Project Prioritisation process
• Contribute to Benefits Delivery
• Accountable for supplier performance reporting
• Deliver supplier release plan (frequency tbc)
• Ensure compliance with contractual frameworks

• Key Responsibilities
• Report on Project progress
• Promote GCS usage standardisation
• Accountable for Project Benefits Delivery
• Monitor external supplier delivery
• Note these are the responsibilities of the
  Project Boards with respect to their relationship
  with the Programme

11
GCS Programme BoardProposed Membership

• In Attendance
• Axsys
• Lynda Lawson
• Ernest Beattie
• Solution Architect
• PMO
• Project Managers, as required
• Change Lead
• GCS Project Clinicians, as required

• Proposed Programme Board
• Gareth Davies - Chair
• Ron Anderson
• Angela Mitchell
• Val Baker CAG Chair
• Robin Wright
• FD/Operations Director (TBC)
• Alistair Robertson
• Ian Fenton TAG Chair

12
GCS Central Programme Support

• The following slide which, at this time, is
  presented for information only and not for
  approval, outlines the roles that will be
  required to support the GCS Programme in the
  future as the Toolkit becomes more widely
  adopted.
• These roles will be clarified and further defined
  to permit a resource plan to be created along
  with a supporting business case for approval.

13
GCS Central Programme Roles (Incl. potential
Project Delivery Roles)
3rd Party denotes potential for these roles to
fulfilled from outwith the NSS Team
14
In Summary

• Implementing the new Programme Governance Model
  is critical to the future success of GCS Toolkit.
• Without the appropriate Governance, including the
  necessary delegated authority from the eHealth
  Programme, the successful implementation of other
  recommendations such as the Technical Strategy or
  the Contract re-negotiations will be compromised.
• Your approval is therefore sought to permit the
  new Programme Board and other related bodies to
  proceed as outlined, with a first meeting of the
  new Board in late November 2007.