PROGRAMME MANAGEMENT AND BUSINESS PLANNING



Similar documents
DELIVERING THE HELP SCHEME TO CARE HOMES

Gateway review guidebook. for project owners and review teams

HARLOW COUNCIL PERFORMANCE MANAGEMENT FRAMEWORK

Network Rail Infrastructure Projects Joint Relationship Management Plan

Project Management Toolkit Version: 1.0 Last Updated: 23rd November- Formally agreed by the Transformation Programme Sub- Committee

CSP Core Services Summary

PROJECT MANAGEMENT FRAMEWORK

The Transport Business Cases

Programme Governance and Management Plan Version 2

Shona Morrison, OPCC Policy Development Manager. This is a Controlled Document

WHY DO I NEED A PROGRAM MANAGEMENT OFFICE (AND HOW DO I GET ONE)?

World Class Education and Training, for World Class Healthcare

Office of the Auditor General AUDIT OF IT GOVERNANCE. Tabled at Audit Committee March 12, 2015

Part B1: Business case developing the business case

Introduction to CiCS Agile Projects

Government Communication Professional Competency Framework

PEOPLE AND ORGANISATION DEVELOPMENT STRATEGIC FRAMEWORK FOR LOCAL GOVERNMENT IN NORTHERN IRELAND

Program and Budget Committee

Do not open this paper until instructed by the invigilator. Please note: This question paper must not be removed from the examination room.

AGENDA ITEM 5 AYRSHIRE SHARED SERVICE JOINT COMMITTEE 1 MAY 2015 AYRSHIRE ROADS ALLIANCE CUSTOMER SERVICE STRATEGY

Benefits realisation. Gate

OPERATIONAL PROJECT MANAGEMENT (USING MS PROJECT)

(1) To approve the proposals set out in paragraphs to ensure greater transparency of partnership board activity; and

Request for feedback on the revised Code of Governance for NHS Foundation Trusts

Managing ICT contracts in central government. An update

Middlesbrough Manager Competency Framework. Behaviours Business Skills Middlesbrough Manager

building and sustaining productive working relationships p u b l i c r e l a t i o n s a n d p r o c u r e m e n t

Digital Britain One: Shared infrastructure and services for government online

How PRINCE2 Can Complement PMBOK and Your PMP Jay M. Siegelaub Impact Strategies LLC. Abstract. About PRINCE2

Change and project management

Before starting it is worth considering what we mean by the term project - basically it can be defined as:

PORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3)

Department of the Environment and Local Government. Project Management. Public Private Partnership Guidance Note April 2000

Service Management and ICT Monitoring and Reporting Advisory and Implementation Services

Local Support Service for Universal Credit

Keys to a Successful Outsourcing Transition

Achieving efficiencies in public transport delivery: The role of Local Integrated Transport Services (LITS)

Retained Fire Fighters Union. Introduction to PRINCE2 Project Management

Verification of need. Assessment of options. Develop Procurement Strategy. Implement Procurement Strategy. Project Delivery. Post Project Review

Mobile Technology in Policing. Home Office and National Policing Improvement Agency REPORT BY THE COMPTROLLER AND AUDITOR GENERAL

Procurement Programmes & Projects P3M3 v2.1 Self-Assessment Instructions and Questionnaire. P3M3 Project Management Self-Assessment

Pol 24/15 Appendix 2. National Policing Fraud Protect Strategy

The STFC Project Management Framework

Confident in our Future, Risk Management Policy Statement and Strategy

Chapter 6 Implementation Planning

Part E: Contract management

LONDON GROWTH DEAL. Building London s skills base and supporting businesses; Helping Londoners into sustainable employment; and

Senior Project Manager A14 Cambridge to Huntingdon, Complex Infrastructure Programme Grade 6. Candidate Pack

DEVELOPING AN EFFECTIVE PERFORMANCE MANAGEMENT SYSTEM. Ross Fraser HouseMark

Project Management Guidebook

Information for schools ready to implement a learning management system and keen to secure MOE funding assistance with Ultranet

Project, Programme and Portfolio Management Delivery Plan 6

Best practice. Corporate Governance. Financial Reporting Council. July Audit Tenders. Notes on best practice

Health Business Services. Operational Plan 2015

Mencap s briefing on the draft care and support bill

CONTRACT MANAGEMENT POLICY

Customer Management Strategy ( )

How To Design A Project

Get in on the Act. The Care Act Corporate

The NHS Foundation Trust Code of Governance

Specification Document (11/1023)

Stakeholder management and. communication PROJECT ADVISORY. Leadership Series 3

TERMS OF REFERENCE - MAJOR EVENTS PANEL

How To Manage Change Projects In A Business Unit

External Audit BV Performance Report: Delivering Change Management and Financial Sustainability

P3M3 Portfolio Management Self-Assessment

IPL Service Definition - Project Management, Programme Management and Governance

Shropshire Highways Draft Asset Management and Communications Strategy and Implications of Department for Transport Incentivised funding

IIA POSITION PAPER: THE ROLE OF INTERNAL AUDITING IN ENTERPRISE-WIDE RISK MANAGEMENT

Financial Conduct Authority. The FCA Data Strategy - How we will manage and use the data we collect

Personalising the Housing Offer New Approaches to Housing with Support for People with Disabilities

Change Management Practitioner Competencies

Accelerating your financial close arrangements

THE APPLICATION OF A VALUE ASSURANCE SYSTEM TO OIL & GAS DEVELOPMENT PROJECTS (Guido Mattu, Franca Marini)

Taking Part Survey. Project Management and Governance

IT1T Integrated Recruitment Systems 2015

Specialist Cloud Services Lot 4 Cloud EDRM Consultancy Services

Communication Capability Review: Department for Business, Innovation & Skills

A responsible, sign. team up. front. Committing to where we re going and putting our hearts into what we do. We get engaged every day.

How To Be Accountable To The Health Department

Date of Trust Board 29 th January Title of Report Performance Management Strategy

London Borough of Bromley COMMISSIONING - PROPOSED TOTAL FACILITY MANAGEMENT CONTRACT

Prepared for: Prepared by:

Change Management for Digital Continuity SROs

Master Level Competency Model

A joint plan to foster a healthy and vibrant Healthcare IT market. Intellect & DH Informatics Directorate. Initial Issue

EXECUTIVE SUMMARY...5

Business Intelligence is a system that collects, integrates, analyses and presents business information to support better business decision making.

Performance Management and Service Improvement Framework

How are companies currently changing their facilities management delivery model...?

UNECE PPP Healthcare Standard

How To Write A Workforce Strategy

SCHEDULE 3. Milestones and Deliverables. Redacted Version

Connect Renfrewshire

White Paper. PPP Governance

PERFORMANCE MANAGEMENT STRATEGY

Specialist Cloud Services Lot 4 Cloud Printing and Imaging Consultancy Services

STRUCTURE AND PROSPECTS APPRAISALS. Further guidance to Further Education Colleges

Item 10 Appendix 1d Final Internal Audit Report Performance Management Greater London Authority April 2010

Transcription:

PROGRAMME MANAGEMENT AND BUSINESS PLANNING This paper describes what lessons were learned from the programme management and business planning which was done to support the operation of the Help Scheme through its various phases. 1

Introduction The Scheme Agreement 1 published in May 2007 set out the basis under which the BBC would provide assistance to eligible people in accordance with the Government s policy to operate a Help Scheme. The Scheme was part of the wider switchover programme coordinated by Digital UK. This paper will describe how the Help Scheme was planned and run from a programme management and business planning perspective. 1 Scheme Agreement. As subsequently revised: http://www.culture.gov.uk/publications/9126.aspx 2

What did we learn? 1 Strategic vision clear Management of the programme was aided by a clear and unambiguous strategic vision no one left behind which helped shape a culture based on risk aversion and quality of delivery. These principles filtered down from initial strategic intent into all areas of delivery, and aided the programme management function in ensuring that the programme outcomes were delivered on time and to the highest quality. 2 The critical importance of sponsorship The Help Scheme enjoyed strong sponsorship from the outset both from Government, and the BBC Trust and Executive. This was sustained throughout by very active management of these relationships, and close consultation and engagement. 3 Clear governance Re-enforcing this was the early groundwork done in clarifying governance and reporting, which was by no means straightforward in a complex, multi-faceted programme involving many partners and contractors. 4 Strong detailed design of management reporting, and robust communication channels The effort involved at the outset in designing and developing robust reporting systems was time well spent; these were refined periodically but stood the test of time. Based on these reporting systems, and the well-defined governance processes, communication channels were clear, which made for effective decision making. 5 Open and transparent culture Last but not least the Help Scheme programme benefited from a management culture that encouraged openness of emerging issues, a consultative approach to decision making, but at the same time short lines of command. This, together with an early warning approach to problems through formal and informal networks, all acted to encourage an atmosphere of mutual support and trust. 3

Programme and business management laying down the foundation From the outset in 2007 a small team of 2-3 people working to the Chief Executive was set up to create the programme structure. Its main activities are summarised in Chart 1 overleaf. It worked principally with three other groups of stakeholder: BBC executive management and the Trust, mainly through the Project Board in reporting on progress and issues on a monthly basis Digital switchover partners, DCMS and Digital UK, in the overall switchover programme The DSHS operations team and the main contractor, CES, in coordinating initiatives and receiving regular progress updates on key projects. 4

Governance reporting Chart 1 5

The operational phases of the Help Scheme How then did programme management evolve over the duration of the Help Scheme? The best way to see this is in the context of the five phases of the Help Scheme (see Chart 2 below). These phases were: Start up; Scale up; Review; Complete; and Close. Each phase reflected the overriding operational priorities at that time and involved quite different people, processes, reporting and risk management. We will therefore consider the approach taken to programme management in each phase. Chart 2 6

Context and business priorities Start up The essential aspects of setting up the Help Scheme programme were tackled in the first few weeks from May 2007 onwards, and established a framework which proved to be durable and adaptable. Rather than being wedded to strict programme management methodologies per se, it was deliberately more fluid and pragmatic in design, but aligned to the principles and best practice set out by the OGC 2. At the outset, some of the essential building blocks for a successful programme were in place but there was a lot still to be done in a fairly short period of time (with the Copeland pilot just months away): The purpose, scope and vision: The purpose and scope were quite well defined in the Scheme Agreement; the vision was also clear: that no one should be left behind Sponsorship: There was active support for this at the highest levels; the Scheme Agreement was agreed by the Secretary of State for Culture, Media and Sport and the BBC. Operationally, BBC Executive Board members were the Senior Responsible Officers (SROs) for respectively DSO overall and the Help Scheme specifically Business case and budget: The business case was based on the overall cost benefit analysis of switchover carried out by Government. The overall Help Scheme budget was agreed, as was the contract for Digital UK to supply services. The process for approving spend would be aligned with BBC Finance Committee requirements Benefits management: This was included in the Government cost benefit analysis of switchover The leadership: The top management was in place; the leadership team was starting to be recruited Other resources: These were still to be defined and would need to be supplemented by specialist consultants as required, especially in the short term Design and delivery: Only a prototype design existed at the start. This would emerge through the competitive dialogue process to select a contractor to run the Scheme 2 For example, Managing Successful Programmes, Office of Government Commerce, 2007 7

The detailed governance: This was being set up and agreed. The reporting content and structure to stakeholders was being developed The timetable: This was known and, crucially, unchangeable (determined by the wider switchover programme) The outcomes: The overall vision was broadly clear but the success measures were still to be agreed Risk management: The key risks and issues were yet to be captured. 8

Focus of the programme Therefore, given the above, a small team working to the Chief Executive acted essentially as a programme office to meet the programme management and reporting needs. The reporting cycle was monthly to the Project Board, chaired by the BBC but with observers from the principal stakeholders of DCMS, DWP, Digital UK, OGC (when the procurement was running), and the BBC Trust. A sample of the reporting which illustrates the scope of the programme activities is included below in Table 1. This is the Chief Executive s monthly Board report finalised a few months after the Scheme Agreement had been signed. The emphasis from the outset was to: Have a comprehensive plan in place which defined all key milestones, deliverables and inter-dependencies (see Item 4 in Table 1). This was monitored on a daily basis and formally updated monthly for the Board reporting cycle Capture overall delivery performance over time against plan. (Item 2). There were three clear priorities in this stage which were the focus of management effort: o Running a small scale pilot operation (Copeland) o Procuring a contractor for the Main Scheme o Designing and recruiting the Intelligent Client team Define the programme risks, assess their impact and develop and monitor appropriate mitigating actions (Item 3). It was very important to be completely realistic about risks. In the early stages of a programme with a large of number of uncertainties and limited prior experience a preponderance of amber and some red risks may look disconcerting but are completely to be expected Document the key decisions made by the Design Authority (whose role it was to put more flesh on the bones of the Scheme Agreement, when operating the Help Scheme on a day-to-day basis) (Item 5); and most importantly Summarise the key messages for all major stakeholders (Item 1). This acted as an early warning system for issues emerging and a means of alerting top management where support may be required such as in helping resolve issues, freeing up resources. 9

Table 1 Chief Executive s monthly Project Board Report (extracts) 3 Item 1 Stakeholder messages Item 2 Overall delivery performance 3 September 17 2007 10

Item 3 Key programme risks Item 4 Milestone performance Item 5 Design Authority Key Decisions 11

Scale up The period from 2008 to 2009 was characterised by a steady increase in activity as the Scheme became fully operational and began to service customers across a number of different regions simultaneously as switchover rolled out across the UK, in the build up to the very large single switchover in Granada (North West England) in Autumn 2009. In this period there was a steady refinement of the monthly reporting processes and information, and management of ad hoc projects and papers as required. Specifically, programme and business management was responsible for coordinating on behalf of the CEO initiatives such as: Rollout plans for each new region. Operationally, a plan had to be prepared and agreed with CES for each new region. The programme team reported on progress on this in the normal way (See Table 1 Item 2) Lessons learned as regions closed. Lessons learned were captured and presented as a Project Board paper, and key learnings consolidated into a Scheme-wide learning log Readiness for a multi-regional and high volume operation. This was an example of a specific project to assess the level of preparedness for the volumes of activity anticipated in late 2009, which was coordinated and reported on through programme management The first iteration of a Help Scheme business plan. The business plan was a major initiative and was tackled once CES had settled in as contractor and the ambition of the Scheme was taking shape. The senior management team took stock of the current state and future vision through a structured business planning process. In the light of the operating environment, and the purpose and scope of activities determined by the Scheme Agreement, the full ambition of the Scheme, the nature of the offer (where this could be influenced), KPIs, and critical success factors were all determined. The team then turned to look at how it should be delivering against this ambition, the role of partners and third parties, and people and financial resource implications. (See Table 2 below for Business Plan contents). 12

Table 2 Switchover Help Scheme business plan: constituent elements April 2009 Business Context what is the operating environment? Business rationale for the Help Scheme Political, economic, social and technological analysis Key business constraints Principal assumptions Business Drivers - what are our ambitions? Ambition of the Scheme Business products and services, and our key strategic initiatives Key performance indicators targets & measures Critical success factors Business implications how do we deliver against our ambition? Engage with people especially the hard to reach Building our reputation among all stakeholders Service eligible people with a simplicity agenda Key timescales Resources and capabilities Key partners and third parties Other initiatives Financial resources Risk management Governance 13

Review The comparatively lower levels of activity in 2010 (see Chart 2) afforded the opportunity to review all aspects of operations ahead of the very high levels anticipated in 2011. Specifically: Work was completed on a further iteration of the business plan A transformation project was launched to improve the customer journey The Making it Happen initiative got under way, designed to ensure that all aspects of the Scheme were fit for purpose to deal with the scope of activities in 2011 The Scheme s risk, issue, dependency and crisis management processes were all reviewed. The Making it Happen in 2011 programme provided project management support to prepare the Help Scheme for expected increased activity from Autumn 2010 and across 2011. It was a very important initiative run within the overall programme management framework, and designed to ensure that, as the Help Scheme entered 2011, it was operationally fit for purpose and ready to manage the increased activity whilst continuing to deliver its quality commitments to our customers. Making it Happen in 2011 was constructed from a number of integrated plans, developed across seven core workstreams, each with a designated Help Scheme lead: Direct Marketing, Contact Centre, Field Operations, Aftercare, Care Homes, Outreach, and Complaints. Progress on each of these workstreams and overall was reported monthly through the usual Project Board channel. This programme was instrumental both in ensuring that the Help Scheme was best placed for the challenges of 2011, but also by providing the timely information flows to reassure top management that this was so. 14

Complete With the Scheme operation in fully mature mode, the task of programme management was to assist management in maintaining focus and momentum. There were operational initiatives introduced in the period designed to do this which required programme coordination. One such was priority customer management. The aim of this was to improve the way the Scheme manages those people with whom it had difficulty communicating, by enabling front-line staff to flag someone as a priority customer through their customer journey. This highlights to everyone who deals with that person that they may need to give more time, attention, and offer other services that are available to assist them. A further customer management initiative, the multiple failure flag, was also introduced, designed to identify those, thankfully rare, instances where the Help Scheme failed repeatedly to provide a good experience for a customer. The visibility of the flag meant that extra attention was paid to resolving that person s issue. In addition to these new initiatives, the programme management function continued to oversee the completion of milestones and deliverables in each region, ensuring the continued timely implementation of what were by this point business as usual activities. 15

Close Whilst the final regional switchovers took place in 2012, for the Help Scheme in 2013 there remained service obligations such as aftercare to be carried out by the Scheme s principal contractor, Carillion, which would still need to be overseen by the BBC, meet the BBC Trust s success measures, and comply with the Code of Service Standards for customers. A much smaller team would clearly be required to manage Scheme duties in 2013. By the end of 2012 virtually all the DSHS management and staff would have left, together with many of the Carillion management team previously operating the Help Scheme service. Responsibilities were being transferred to elsewhere in the BBC, to ensure that the final aspects of service delivery were properly carried out. The closure plan was run as a separate programme comprising nine projects: I. DSHS people - retain and motivate people until their planned departure dates II. III. IV. Finance and legal - ensure there are sufficient funds, effective financial management Operational continuity - customer service quality of business as usual Communications - consumer PR, stakeholder communications, issue management V. Governance - appropriate decision-making processes in place in all phases VI. VII. VIII. IX. The tin box handover - key elements of Scheme for handover after switchover completed Information security - decommission all data and systems Carillion contract - handle end of contract smoothly Scheme legacy capture and communicate Scheme learning. The leader of each project - a member of DSHS management was charged with developing detailed terms of reference for their project, a set of deliverables, and project risks. This was reviewed and signed off by DSHS management and forms the backbone of closure planning. All the project plans were consolidated into a detailed programme plan, with responsibilities and milestones identified. The closure plan was independently reviewed by external consultants and judged to be comprehensive and fit for purpose. 16

Figure 3 below, the closure timeline, shows the 2012 regions to switch, the four phases as described, and the proposed stages in the TV Licensing handover. Whilst TV Licensing would not take over formal responsibility until the final switchover in Northern Ireland in October 2012, a gradual process of familiarisation and assimilation was planned. The current DSHS Chief Executive, who planned to relinquish formal Scheme responsibility in October 2012, would remain on the DSHS Board until he left the Scheme in December 2012. Figure 3 Help Scheme closure timeline DSHS Closedown Timeline 17

Conclusion Running the Switchover Help Scheme was new territory for the BBC. Operationally complex, with a multiplicity of stakeholders and a customer base difficult to access, the approach to programme management from the outset was to take what may appear to be an unlikely mix of rigour and pragmatism. Rigour certainly in: governance decision making and reporting; risk management; and demonstrating value for money. It was more pragmatic in its use of tools and techniques, not through scepticism or distrust - indeed in the course of such a long programme it is likely that every single tool and technique was considered if not used - but as a result of not wishing to be constrained by methodologies which may not be universally applicable. 18