Outline the corporate aspirations, setting out the business intent and benefits being sought.
Present overview of the state as it is now.
What are the business needs that the organization is aiming to achieve? The needs should be clear and specific, not generic aspirations.
How would the future look when the programme is delivered and the benefits achieved? This can be represented quantitatively and or qualitatively.
Include known and foreseeable constraints or exclusions that may apply and any other outcome that will be necessary but not within the programme.
Provide an overview of the scope of the programme, outputs and deliverables and list of projects, if possible.
Use this section to set out the drivers that have created the need for this programme. This will include how the programme contributes to the organisation’s strategic objectives and fits with other initiatives.
Briefly articulate the outcomes that the programme is expected to achieve. Specify if there are any constraints (e.g. must be achieved by x).
List the activities, time and resources required to complete the programme brief and programme delivery plan.
The programme mandate needs to be signed off by the sponsoring board who will commit the resources to develop the programme brief and programme delivery plan.
Describe a compelling picture of the future that this programme will enable. This should include the new and/or improved services and how they will look and feel and be experienced in the future.
Describe the measurable improvements that the programme will achieve.
Describe other benefits that will arise from this programme which are not easily measured.
Describe the negative results of undertaking this programme.
Describe the project and programme activities identified so far that will be required to deliver the programme benefits, with estimates of what they will cost and how long it will take to complete the work.
State what business activities should start, be done differently or cease, in order to achieve quick wins.
List the potential threats (risks) and current issues to the benefits of the programme as they are currently understood. If there is one, use the corporate approach to risk and issues management. This section should be structured according to the corporate guidance.
Describe any known constraints that apply to the programme.
Describe any assumptions made that underpin the justification for the programme.
Describe how the organisation will provide the necessary programme management resources and capability required to carry out the proposed programme successfully.
This section should be signed by a representative of the sponsoring group to confirm acceptance of the brief. Use the version and authority sign-off on the front page.
An executive summary indicates what decision is being sought and what is the basis of the recommendation.
The strategic case summarises the vision and the strategic drivers for this investment, with particular reference to supporting strategies, programmes and plans.
Contents of this section may include the following:-
The case for change summarise the business needs for this investment, with particular reference to existing difficulties and the need for service improvement. This should clearly set out the investment objectives and the related benefit aspirations. Contents may include these elements:-
The economic case should include the options appraised and the outcomes, including the critical success factors. Contents may include the following:-
A commercial case may include the delivery model, risks and contingency options. Appropriate indices may be used to represent non-quantifiable risks and benefits. Contents may include the following:-
The financial case should demonstrate the affordability model, where the scheme requires the support and approval of external parties, and indicate that this is committed and forthcoming. A letter of support should be attached as an appendix. Contents of this section may include the following:-
The management case should include the management arrangements, including delivery, benefits realisation and risk management. Contents of this section may include these elements:-
Explanation of RAG Status:
Note: The distinction between capital and revenue is only relevant to public sector programmes
Prepare a benefits profile for each benefit. Benefits profiles describe benefits in more detail and record information to:
The benefits profiles should be signed-off by the PrgS (or BCM on their behalf) to confirm acceptance of the benefit profiles.
Use this section to outline the history of the programme, a few paragraphs that include why it was needed, when it started and the reason for its closure.
Outline how much of the programme has been implemented. If not all of its components have been created, outline the reasons for the shortfall; if the partially changed state of the organisation requires any further activities, where does the responsibility for those activities now lie.
Using the table below, for each benefit list the benefit measures that have been captured to show how well the business case has been achieved. The first three columns are copied from the benefit profile.
For any benefit that has yet to be fully realised, list who is the new owner of the benefit realisation activities and whether this responsibility has been formally handed over and accepted.
List all outstanding risks and where the ownership now lies.
List all outstanding issues and where the ownership now lies.
Normally, all projects will be closed at the end of the programme. In the case of premature closure, there may be some projects that will still be valuable. List the existing projects that will still be useful to the organisation and where the new ownership now lies.
Highlight key lessons learned (positive and negative) that should be passed to on-going and future programmes. Consider the following:
The closure review needs to be signed off by the PrgS, who will report to the PrgSB in order to gain approval for the formal closure of the programme.
Use the version and authority sign-off on the front page.
Leading others
Managing people and performance
Project and programme management
Financial management
Key communicator recognises that the role of programme manager demands regular contact and negotiation with the team, clients, consultants, contractors and other stakeholders. Focus on customer satisfaction is paramount.
Essential skill is to be able to see the big picture; recognise the detail of projects and how they could contribute the success or otherwise of the programme.
Business skills include cost funding reconciliation reporting, HR management and leadership skills, budget information and control, including forecasting, payment processes and so on.
Project and programme management skills
The business change manager (BCM) role is mainly benefits focused. The BCM is responsible, on behalf of the programme sponsor, for defining the benefits, assessing progress towards realisation and achieving measured improvements. The BCM role is associated mainly with programmes that tend to be more benefits focused than projects, although projects that deliver benefits in their own right may warrant the creation of a BCM role.
The BCM role must be the ‘business side' in order to bridge the programme and business operations. Where the programme affects a wide range of business operations, more than one BCM may be appointed, each with a specific area of the business to focus on.
The BCM is responsible for the following:
The individual appointed as BCM should be drawn from the relevant business areas wherever practicable. Their participation in the programme should be an integral part of their normal responsibilities to enable changes resulting from the programme to be firmly embedded in the organisation.
BCMs require detailed knowledge of the business environment and direct business experience. In particular, they need an understanding of the management structures, politics and culture of the organisation owning the programme. They need effective marketing and communication skills to sell the programme vision to staff at all levels of the business, and BCMs ideally should have some knowledge of relevant management and business change techniques such as business process modelling and re-engineering.
The benefits realisation manager role is responsible for identifying, base-lining, profiling, planning, tracking and reporting the benefits. The role involves developing and then managing the processes and management systems needed to support and govern effective benefits enablement and realisation to ensure the programme meets its objectives and realises its target financial savings
The role is responsible for embedding and aligning the concept and principles of benefits realisation and contributes to a change in culture and behaviour across the programme in respect of benefits management and trains, educates and mentors, where appropriate, those staff directly involved in the delivery of business benefits.
Leading others
Project and programme management
Analysis and use of evidence
The skills, competence and key criteria for the roles outline are for the guidance purposes only. The specific will vary depending on the individual requirements and context of each role and programme.
London’s successful bid for the 2012 Olympic and Paralympic Games created the need for a major regeneration and construction programme to provide the venues and infrastructure needed to stage the Olympic Games.2 The programme of construction was extensive and technically and politically challenging. It was also up against a fixed deadline of the Opening Ceremony of the Games in July 2012. Turning the vision of the Olympic bid into the reality of roads, bridges and stadia was the job of the Olympic Delivery Authority (ODA), a new, publicly funded body established by an Act of Parliament in April 2006.
Vision statement: “We will use the power of the Games to inspire change.”
Programme goal: “To host an inspirational, safe and inclusive Olympic Games and Paralympic Games and leave a sustainable legacy for London and the UK.”
The programme scope, broadly, was to procure and deliver £6 billion of major construction works, comprising:
The ODA budget was set at £8 bn in 2007 including a £2bn of contingency, with the overall delivery budget of approximately £9.298 bn.
The timeline for the programme and the individual phases is summarised below:-
Although delivery responsibility was cascaded down to project level, all key policies and processes were determined and implemented at a programme level. All projects followed a standard approach for governance, control and reporting mechanisms.
Responsibility for preparing and delivering the Olympic and Paralympic Games and their Legacy resides with the lead delivery stakeholders, namely LOCOG (London Organising Committee of the Olympic Games and Paralympic Games Ltd.), ODA (Olympic Delivery Authority), GLA (Greater London Authority), LDA (London Development Agency), BOA (British Olympic Association), BPA (British Paralympic Association), OPLC (Olympic Park Legacy Company), OSD (Olympic Safety and Security Directorate) and HMG (Her Majesty’s Government - GOE [Government Olympic Executive]).
From the outset, ODA instituted processes and systems, meeting structures and delegations to ensure strategic direction, performance management and value for money. The delivery partner (a private sector consortium CLM comprising a partnership from the three parent companies of CH2M, Laing O’Rourke and Mace) was fully integrated into all aspects of governance and was appointed to be the ODA’s overall programme management partner, as well as have the responsibility of project manager for the major construction projects: this was preferred over the alternative approach of separating project and programme management, as it was judged that there were clear benefits of having a common programme and project manager and that the potential conflicts of interests could be managed by having ODA in an overall assurance role.
Delivery Partner (DP) was responsible for leading programme and project delivery review meetings; stakeholder meetings were also held on every project. For each priority theme, dedicated boards were formed to assure that at a programme level the priority themes were achieving the targets, and where shortfalls were forecast, appropriate measures were put in place to enable delivery.
There were several aspects to managing integration across the programme – these included dependency management, design management, physical integration and change management. Across all aspects of managing integration, the two key elements were issues identification and issues resolution; at project level these were managed within the project governance, and at programme level additional processes were required to manage cross-project interfaces to ensure that consequential impacts were identified and programme priorities applied in resolution.
Where escalation was required, this was assessed in context of the overall impact – both from delivery and consequential issues, a key element of managing this having been the integrated programme schedule. Decisions were prioritised and options assessed in the programme (as opposed to an individual project) context.
The majority of benefits generated by the ODA Programme delivering venues and infrastructure are to be realised after the transformation from Games format to legacy, through future sporting and regeneration uses. The management of the direct benefits obtained from hosting the London 2012 Games was a responsibility of LOCOG and HM Government (DCMS-GOE). The legacy benefits are to be delivered by other agencies, such as the Lea Valley Regional Park Authority (LVRPA) and the Olympic Park Legacy Company (OPLC).
The project business cases contain a summary of the anticipated benefits for each of the projects. At the close-out stage, ODA reported on any benefits achieved and identified owners from other stakeholder organisations for the realisation of future benefits. The process for transferring the benefits was managed by the GOE through the Evaluation Steering Group.
In addition to the benefits identified in individual business cases, London 2012 also appeared to have delivered a number of unintended benefits. These include benefits obtained through coordination exercises (particularly in context of organisations who normally would not work together), communication benefits (in terms of a variety of partnerships working together) and enhanced delivery capacity for participating organisations.
A report by the Department for Culture, Media and Sport3 identified that the Games have enabled a number of lessons to be learned about how to maximise the benefits to the host country and city from the staging of mega-events. These include:
Following the introduction of a new-generation design of display unitary and finishes for the retail floor space of a franchised high street retailer, a board level directive required that 100 stores of the group’s 550 store portfolio were to be re-branded by the end of that financial year – a period of just 5 months. The retail organisation had an existing, experienced in-house project management team structure but it was already committed to delivering existing projects. With relative low technological complexity, the challenge of this undertaking was the severely limited time for delivery, the number of projects to be executed and the organisational complexity created by the number of interested stakeholders. The successful solution was the adoption of programme management to provide centralised strategic direction and control mechanisms.
Vision statement – To increase sales turnover by enhancing the attractiveness of the customer store experience.
Programme goal: To effectively re-brand 100 stores within a 5 month period.
Strategic objectives
The site works comprised the execution of the following activities at each of the 100 premises:
Prior to these works being implemented, an exercise was required to determine in which 100 stores the work could most effectively be carried out. In addition to the necessary statutory consents, there was an extensive range of internal approval processes, such as individual brand design sign-off on a store-by store basis, financial approvals, landlords’ consents and so on.
Within the overall 5 month period for completion of the works, typical timescales for individual projects were:
Overall sponsorship and governance of the programme was provided at an executive level within the retailer’s organisation together with joint venture partners who supplied all funding for the works. While programme strategic direction, policies and processes was controlled at the programme level, actual implementation was delegated down to the project level. All projects followed a standard approach for governance, control and reporting mechanisms.
Key Stakeholders
External Parties
In this case study the early stages of the programme life cycle relating to inception, initiation and definition had been developed at an executive level in the retailer’s organisation. At the end of Stage C the definition of what the programme needed to achieve and the expected benefits were passed to a newly appointed programme manager for implementation.
During a rapid review of potential delivery strategies, it was concluded the only realistic way of achieving the objectives within the required timescale was to adopt a programme management approach to provide centralised direction, control and monitoring of the 100 projects and to embrace a partnering arrangement with existing contractors who were given extended responsibilities and autonomy for project delivery. Contractors were given responsibility for confirming the store layout design, drawing production, site management and supervision, determining project duration and cost, self-snagging and agreeing sign-off with the store.
The process required little induction or training of either the approved contractors, designers or project teams as their historical knowledge and experience of working with the clients was extensive. However their delivery teams were clearly briefed on each aspect of the fit-out to eliminate any doubt as to how the finished product would look. Upon completion of the first two sites for each of the contractors, a quality control inspection was carried out with both the client’s lead project manager and contractor’s project manager and site supervisors present to ensure all parties understood the acceptable parameters with regard to the finishes and to discuss the general project delivery. To finalise the whole process, a joint meeting with all of the contractors was held upon completion of five stores each. The final agreed process was then passed over to the PMO who had responsibility to ensure this process was rolled out across all the 100 projects. The PMO monitored the progress of each project against this process and ensured any issues preventing contractors from proceeding were rapidly escalated to the programme manager for resolution.
The principal and expected benefits that were anticipated from adopting the programme management approach were:
The 100 projects were very cost effective, with minimum variations, and the overhead cost to the franchisees and the main group was minimal. The turnaround of the sites successfully met the board’s target of 100 stores by the required date, and as a result a further 150 stores were added to the programme.
No major dis-benefits were found. There were unintended benefits that resulted from the programme:
Implementation of this programme of works identified a number of factors that were considered important to the successful delivery of further similar programmes or projects:
Highways England (prior to 2015 known as the Highways Agency) is the government body with responsibility for operating, maintaining and modernising the strategic road network in England; all motorways and major A roads totalling 4,300 miles and carrying a third of national traffic. In common with all public bodies, Highways England was required to obtain funding for new capital works by bidding to HM Treasury on a project by project basis with monies being released on an annualised basis. Although a 4 year rolling plan of schemes was put in place, the release of annual funding necessary to achieve this was not secure as often changing priorities of other categories of transport regularly caused peaks and troughs in availability of funds. This lack of certainty of funding created substantial inefficiencies in the delivery of new schemes.
Coinciding with the new coalition government beginning to instigate their austerity programme, Highways England had carried out a strategic business review of their delivery requirements and processes and on the basis of the findings approached HM Treasury with a unique proposal. They made an offer that if HM Treasury would allow them to adopt a programme approach and if they would guarantee availability of funds for this 5 year programme of 14 schemes without the restrictions of annualisation, Highways England would offer a 20% reduction to the cost of delivering the schemes.
The success of the adoption of programme management has resulted in HE promoting a ‘programmatic approach’ as an organisational culture that they apply to their capital delivery and change management activities.
Programme goal: To undertake their 2010–2014 Delivery Plan with a 20% reduction in cost.
Highways England had a number of strategic objectives:
The programme comprised the delivery of 14 major roadway schemes of a total estimated cost of £1.78 billion.
The overall programme of works was to complete within a 5 year period with flexibility in the order and timing of individual projects.
On HM Treasury’s acceptance of their offer, HE established a programme management organisation headed by a programme director (at divisional director level within HE), with a delivery hub acting as a programme management office as the central driving force of programme delivery.
Key roles and participants comprised the following:
Key external stakeholders consisted of the following:
Key internal stakeholders consisted of the following:
Whereas previously the methodology for carrying out schemes followed a traditional contractual arrangement of having two teams each with its own stage, one for design and one for construction, on adoption of the programme approach a new process involving three stages was introduced.
Product Development
This first stage was focused on understanding the general requirement and features of each scheme, highlighting potential risks and problems, identifying any potential negative/positive interfaces between schemes and consideration of any critical operational characteristics.
Key outputs from this stage were:
This stage highlighted the significant benefits gained from being able to discuss programme-wide requirements and demands with the supply chain rather than being restricted to only being able to consider each scheme independently.
Construction
To take full advantage of the ability to adopt a programme approach it was decided to promote an open, collaborative culture; a framework arrangement with four delivery partners was established for the construction works. Partners were invited to share in both the pain and the gain of the programme. Incentives were introduced whereby a third of any savings to the target cost on a project were retained by the contractor with the rest going into a programme pot. Contractors were therefore directly concerned with the financial performance of every project, leading to the sharing of experiences, techniques and methods.
Testing and commissioning
Historically incorporating a new scheme into the live road network was a separate process carried out by a separate unit within HE, HE Operations. Often during this process problems arose requiring additional modifications and causing delays to the opening of the new roadways. As a consequence of adopting programme management, this unit was included as part of the programme team and was able to review design proposals to eliminate or minimise any issues arising between the construction works and the final operational facility.
In addition to the three key programme management stages HE also operate on each project within a detailed project control framework (PCF) which consisted of sequential stages 1–7, each with a gateway approval. (For more detail see HE, The Project Control Framework Handbook).4
The Delivery Hub was responsible for maintaining 14 different functional areas across the programme:
Implementation and maintenance of these functional areas was carried out by a mix of HE internal staff, consultants and contractors. Aspects of particularly important programme functions are highlighted in the following sections.
Risk: Initial consideration of risk disclosed that in the past risk had been treated in different ways on projects. Adoption of common definitions and process uncovered a high degree of commonality of risk type so that strategies could be developed at the programme level, which could either eliminate or minimise risk or its impact. Considering risk at the programme level allowed for a more cost effective way of dealing with the likelihood of aggregate risk occurring. Overall, across the programme it was estimated that this resulted in between 2% and 6% saving on costs.
Planning: Production of an integrated high-level schedule for the programme provided a wider perspective which helped to introduce a level of flexibility into the sequencing of projects that would not have been possible on a project by project basis. This allowed for more efficient balancing of demand for plant, materials, technology and labour. Developing schedules in conjunction with the supply chain had the additional benefit of their being better informed about future requirements. Discussions on scheduling with open and transparent attitudes being displayed by all parties contributed to a 5% improvement in project durations with a saving on preliminary costs, which on civil engineering projects can represent as much as 45–50% of total cost.
Health and Safety: The inherent nature of highway construction, involving major items of plant, means the industry does have closely monitored health and safety processes. Consideration of health and safety at the programme level meant that good practice could be taken from some projects and shared on others. In addition, a detailed investigation by the Delivery Hub of a category of ‘near misses’ across projects led to significant reductions in reportable accidents. Overall the whole programme had a very low accident frequency rate.
Visualisation: The procedure, replicated practice from the car industry, of starting each week with a production meeting involving all parties was implemented. Similar to the methodology of the concept of The Last Planner, the meeting considered performance attained in the previous week and the activities to be undertaken in the coming week. This approach provided full transparency of the current issues, identified problems and blockers, and allowed collective solutions to be developed. Open display of performance measurement was provided by visibility boards in the Delivery Hub’s offices and gave a highly transparent view of performance against goals.
A critical aspect of HE’s adoption of programme management was the desire to introduce a behaviour of open, collaborative working with their supply chain. This was the focus of the organisational development function area and was achieved by entering into framework agreements with preferred suppliers and by involving them at an early stage in the programme, giving them full visibility of the programme’s performance and allowing them to contribute towards jointly developed solutions to problems.
A fuller description of HE’s approach to collaboration is contained in the Infrastructure Client Group paper ‘Improving Infrastructure Delivery: Alliancing Best Practice in Infrastructure Delivery’.5 This document describes an alliance as:
Successful alliancing is based on four aspects; the behaviours displayed by the individuals involved and their organisations need to be sympathetic to objectives of the programme, all parties needed to be highly integrated, there needs to be strong and committed leadership of the alliance and there are commercial rewards in place for delivery performance.
On this programme HE brought together an alliance comprising their internal programme management structure and delivery hub together with their external delivery partners.
The principal benefits that resulted from adopting the programme management approach were as follows:
No major dis-benefits were identified by HE. HM Treasury being impressed by HE’s achievement instructed the addition of six further schemes to the 2010–2014 Delivery Plan. Having demonstrated the benefits of using programme management to delivery 5 year plans of work, in agreement with HM Treasury, this has become the preferred method of delivery for capital works at HE
Implementation of this programme of works identified a number of factors which were considered important to the successful delivery of further similar programmes or projects: