Tag Archives: agile

FBI chooses Accenture for IT project to modernise its HR systems

By David Bicknell

Yesterday I mentioned the challenges that the FBI is having in bringing a case management IT project in on time.

It’s good to know then that the FBI will now be assisted in its ongoing delivery of IT by Accenture.  Not for the case management project, but for an enterprise resource planning (ERP) system  to support the FBI’s Human Resources Information System (HRIS).

The award, under a  General Services Administration IT schedule that provides technology support services to the FBI through a ‘Blanket Purchase Agreement’ (BPA) plus four task orders’ will enable Accenture Federal Services to oversee selection, installation, testing and support to the agency’s HR systems.  Accenture also will complete a fit gap analysis to determine possible future costs to replace the FBI’s current HRIS systems.

Accenture said that by modernising its Human Resources information System, the FBI ‘will be able to increase effectiveness and streamline processes. These improvements will help the FBI develop a modern, on-demand system for accessing personnel information.’

The contract, which includes one base year with four option periods, also requires Accenture to submit a report with recommendations the FBI can use to determine whether to customise software, re-engineer business processes or combine both options to support future needs.   
 
Accenture, as its press release puts it, will also be ‘eligible to receive additional task orders under the BPA.’
 

Agile approach ‘reduces risk’ but offers no delivery guarantee for FBI as Sentinel project slips again

By David Bicknell

A recent story by the US magazine InformationWeek Government has cast some doubt over whether a move to Agile development will necessarily bring IT projects in on time and to budget, despite the best intentions. Sometimes other technology factors, such as legacy hardware, come into play.

The report says an FBI project to develop a digital case-management system to replace outdated, paper-based processes has been further delayed, despite a move to use Agile development to hasten the project’s completion.

The system, dubbed Sentinel, is now due to go live in May, eight months later than the FBI planned when it embarked on the Agile development plan.

It follows a number of delays going back to 2006 in the plans to build a replacement for the FBI’s 17-year-old Automated Case Support system, which is used by agents and analysts to manage their cases.

 In 2006, Information Week Government reports, the FBI awarded Lockheed Martin a $305 million contract to lead development of Sentinel, but took back control of the project in September 2010 amid delays and cost overruns.

Then, the FBI said it planned to finish Sentinel within 12 months using Agile development. But that worked has slipped (the FBI had earlier pushed Sentinel’s deployment from September 2011 to January 2012), and a four-hour test of the system in October resulted in two outages, according to a report by  the Inspector General released in December which contains details of the Agile development’s sprints’ progress.

The FBI said the glitches  were down to overburdened legacy computer hardware and said the hardware will need to be upgraded to support Sentinel’s use across the agency, according to the Inspector General.

The report’s conclusion says:

The FBI’s transition to an Agile development approach has reduced the risk that Sentinel will either exceed its budget or fail to deliver the expected functionality by reducing the rate at which the FBI is spending money on Sentinel and by instituting a more direct approach to the FBI’s monitoring of the development of Sentinel.

!When we provided our initial draft of this report to the FBI in October 2011, we expressed concern that the rate at which the FBI was developing Sentinel’s functionality indicated the project was at risk of falling behind the FBI’s then planned January 2012 deployment date.

“In December 2011, after we completed our fieldwork for this report and after we provided the FBI with a revised draft report, FBI officials told us that the FBI extended the Sentinel deployment date to May 2012. While we have not had the opportunity to fully review the FBI’s plan to meet these revised completion dates, we continue to believe it will be challenging for the FBI to meet this latest goal for deploying Sentinel to all FBI users in this timeframe.

“It is too early to judge whether the FBI’s Agile development of Sentinel will meet its newly revised budget and completion goals and the needs of FBI agents and analysts. While the Sentinel Advisory Group responded positively to the version of Sentinel it tested, results from wider testing were not as positive. Also, none of the Agile-developed Sentinel has been deployed to all users to give them the ability to enter actual case data and assist FBI agents and analysts in more efficiently performing their jobs.

“Despite the FBI’s self-reported progress in developing Sentinel, we are concerned that the FBI is not documenting that the functionality developed during each sprint has met the FBI’s acceptance criteria.

“Our concerns about the lack of transparency of Sentinel’s progress are magnified by the apparent lack of comprehensive and timely system testing. Our concerns about the lack of transparency also extend to Sentinel’s cooperation with internal and external oversight entities, to which Sentinel did not provide the necessary system documentation for them to perform their critical oversight and reporting functions. We believe that this issue could be resolved, at least in part, with a revision to the FBI’s Life Cycle Management Directive to include standards for Agile development methodologies.”

Responding to the report the FBI said:

“The Federal Bureau of Investigation (FBI) appreciates the opportunity to review and respond to your draft report entitled, “Status of the Federal Bureau of Investigation’s Implementation of the Sentinel Project.”

“We are pleased with your conclusion that, by adopting an Agile development approach, the FBI bas “reduced its rate of spending on Sentinel” and instituted a more “direct approach to monitoring the development of the system’s functionality.”

“Indeed, as the FBI’s figures included in this Report demonstrate, while we have expended only 52% oftbe Agile development budget of$32.6 million. as of December 6 we had completed 88% of the required system functionality. The percentage of functionality completed has further increased during the time that has passed since your report was last updated.

“This accomplishment is significant. In mid-2010, the FBI charted a new course for completing the remaining two phases oftbe Sentinel program using an Agile development approach, which represented a substantial departure from its prior development activities. As a result, you concluded in this Report that the FBI is “expending significantly fewer dollars per month than it had in Phases 1 and 2 for the project.”

“In sum, we agree with your conclusion that the FBI’s transition to an Agile development approach has “reduced the risk that Sentinel will either exceed its budget or fail to deliver the expected functionality.” As you note, “at this point in time, the FBI does not foresee exceeding the $451 million budget to complete the Sentinel project.”

“With that in mind, we are mindful of the short delay we have recently encountered under our new” Agile” approach. The Sentinel development schedule has recently been extended by two months (from December 2011 to February 2012), and the FBI-wide deployment is now scheduled for May 2012, as described in this Report.

“This modest extension is due primarily to the need to implement a standard five-year “refresh” of computer hardware, so the Sentinel software will provide the required functionality as intended. Indeed, you have determined that, given the pace at which the program has proceeded under the Agile approach over the time period you reviewed, your estimate for completion is essentially the same – June 2012.”

Inspectorate General report

Agile for Universal Credit a good choice

Happy New Year from Campaign4Change

By David Bicknell

A Happy New Year to all our readers from both Tony Collins and me. Let’s hope that 2012 brings success in the development of IT projects – and satisfactory resolution for those that weren’t quite so successful – as well as continued progress for Pathfinder mutuals.

I’d like to see the London Borough of Hammersmith & Fulham’s Schools IT mutual successfully get off the ground early this year, and for another  mutual, Central Surrey Health that I spoke with in 2011 to make the continued business progress its efforts deserve. I hope that all growing, developing and prospective mutuals get all the political and economic support they need to thrive.

I came across a few stories at the end of 2011 from other blogs that made for interesting reading, plus a few Campaign4Change favourites. Here’s a selection:

Taking Stock

Lessons from the GoDaddy Customer Revolt

Top Harvard Business Review Blog posts of 2011

Top 10 Green Business stories

The unavoidable truths about GovIT

Government’s new ICT Plan – the good, the bad, and what’s needed

Agile can fix failed GovIT

G-Cloud and agile briefings

By Tony Collins

On 22 November the Government Digital Service is giving a briefing for potential G-Cloud suppliers. It’ll be streamed live.

Officials say the briefing will be particularly useful to suppliers whose employees have never participated in a government tender.

At the ApplyCamp, officials will explain G-Cloud, steps in the OJEU procurement process, what information potential G-Cloud suppliers need to give, and what happens next.

The event is particularly aimed at Infrastructure as a Service, Platform as a Service, Software as a Service and other specialist cloud service suppliers. It will be held at Google, 76 Buckingham Palace Road, London SW1W 9TQ – 3pm – 5pm.

Agile TeaCamp – 24 November

Between 4pm and 6pm at the Cafe Zest, House of Fraser, Victoria St, London, there will be talks on agile. Derrick Cameron, MD of software consultancy Eximium and COO of agile software house Procession will speak on “Becoming the Intelligent Buyer”.  Chris Parsons, a “freelance thinker, coder and trainer” will talk about the e-petitions project and the aims of the Agile Delivery Network.

Teacamps in November and December – Government Digital Service

UK GovIT often a barrier not enabler says Cabinet Office official

By Tony Collins

In an interview for UKauthority.com Chris Chant, Executive Director at the Cabinet Office and head of the G-Cloud programme,  debunks the claims of some that GovIT doing a great job and should remain largely untouched.

Chant says: “IT is supposed to be an enabler. Quite often in my experience in government IT it is actually a barrier to getting things done. That’s no way to use IT. It is supposed to support what we do.”

His criticism puts into context claims by some in the civil service that GovIT is an unpublicised success because of the ease and success of online re-taxing of vehicles, the payment of benefits to millions of people and the collection of taxes.

Chant has made clear his concern that some departments are locked into major IT suppliers through costly, inflexible long-term contracts that, in some cases, are being signed anew.

“In the main we are not delivering good quality IT to government and public sector workers. We are not delivering good IT solutions to the citizen …”

He calls for internal change and describes SMEs as “front and centre to what we need”.

“It is with SMEs that agility and innovation lie, and it is that market we are really encouraging… Good IT is not developed by spending a long time trying to work out a definitive answer, and then taking ages over delivering it only to discover it is not what we needed in the first place. It is about iteration. I have said all along that we do not have all the answers. We will develop as we go and take SMEs with us.”

Asked whether the public sector is ready for the cloud Chant replies: “No we are not. We are quite a way from that… We are very well positioned to operate in a world where our IT is delivered by multinationals but now it is a different world.”

He says that the cloud has security limitations. “It is difficult to see the cloud in the short term handling some of the higher security aspects of what we do but for a lot of what government does it’s about commodity products and we need to get people in who know how to handle that.”

The focus he says must always be on the citizen – assumptions should not start from a departmental or systems standpoint. “We will need to change the way we do things; we will need some new people and I suspect a lot of retraining. I think we will need a lot fewer people working on the client side of government IT…

“We are in really tough times and the idea that we can operate with [current] cost levels is wrong…”

Government clouds take shape – UKauthority.com.

The unavoidable truths about GovIT – Chris Chant.

Vested interests will try to stop GovIT changing.

What exactly is HM Revenue and Customs paying Capgemini billions for?

DWP signs new large contracts with HP, Accenture, IBM and Capgemini.

Government’s new ICT plan – the good, bad and what’s needed

By Tony Collins

There is much to commend the 102-page Government’s ICT Strategy – Strategic Implementation Plan”.  Its chief assets are the touches of realism.

In the past Cabinet Office documents have referred to the billions that can be cut from the annual government IT spend of £15bn-£20bn. This document is different.

In promising a saving of just £460m – and not until 2014/15 – Cabinet Office officials are not being ambitious, but neither are they making impossibly unrealistic claims. [The press release refers to £1.4bn of savings but there’s no mention of that figure in the document itself.]

The Implementation Plan also points out that the oft-quoted annual government IT spend of £16bn-£17bn is not spending in central government IT alone but includes the wider public sector: local government, devolved administrations and the NHS. The Implementation Plan concedes that there is “no definitive or audited record of ICT spending in central government for 2009/10”, but it adds, “the best estimates suggest this to be around £6.5bn in central government…”

Now at last we have a figure for the cost of central government IT. But we’re also told that the Cabinet Office has no control or strong influence over most of the ICT-related spending in the public sector. The document says:

“Though implementation is not mandatory outside central government, Government will work with the wider public sector to identify and exploit further opportunities for savings through greater innovation, and sharing and re-use of solutions and services.”

That said the document has some laudable objectives for reducing ICT spending in central government. Some examples:

–         50% of central departments’ new ICT spending will be on public cloud computing services – by December 2015. [Note the word “new”. Most departmental IT spending is on old IT: support, maintenance and renewal of existing contracts.]

–         First annual timetable and plans from central government departments detailing how they will shift to public cloud computing services – by December 2011.

–         Cost of data centres reduced by 35% from 2011 baseline – by October 2016. [What is the baseline, how will the objective be measured, audited and reported?]

Drawbacks:

It is a pity the document to a large extent separates IT from the rest of government. If simplification and innovation is to be pervasive and long-lasting senior officials need to look first at ways-of-working and plan new IT in parallel with changes in working practices, or let the IT plans follow planned changes.

Not that this is a black-and-white rule. Universal Credit is an essentially IT-led change in working practices. The technology will cost hundreds of millions to develop – an up-front cost – but the simplification in benefit systems and payment regimes could save billions.

Another problem with the Implementation Plan is that it is in essence a public relations document. It is written for public consumption. It has little in common with a pragmatic set of instructions by a private sector board to line managers. Too much of the Cabinet Office’s Implementation Plan is given over to what has been achieved, such as the boast that “an informal consultation to crowd source feedback on Open Standards has taken place…” [who cares?] and much of the document is given over to what the civil service does best: the arty production of linked geometric shapes that present existing and future plans in an ostensibly professional and difficult-to-digest way.

And many of the targets in the Implementation Plan parody the civil service’s archetypal response to political initiatives; the Plan promises more documents and more targets. These are two of the many documents promised:

“Publication of cross-government information strategy principles – December 2011” …

“First draft of reference architecture published – December 2011.”

Platitudes abound: “Both goals are underpinned by the need to ensure that government maintains and builds the trust of citizens to assure them that the integrity and security of data will be appropriately safeguarded.”

There is also a lack of openness on the progress or otherwise of major projects. There is no mention in the Implementation Plan of the promise made by the Conservatives in opposition to publish “Gateway review” reports.

What’s needed

More is needed on specific measures to be taken by the Cabinet Office when departmental officials resist major reform. The promise below is an example of what is particularly welcome because it amounts to a Cabinet Office threat to withhold funding for non-compliant projects and programmes.

“Projects that have not demonstrated use of the Asset and Services Knowledgebase before proposing new spend will be declined.

“Departments, in order to obtain spend approval, will need to move to adopt mandatory common ICT infrastructure solutions and standards, and spending applications will be assessed for their synergy with the Strategy.”

But these threats stand out as unusually unambiguous. In much of the Implementation Plan the Cabinet Office is in danger of sounding and acting like PITO, the now-disbanded central police IT organisation that had good intentions but could not get autonomous police forces to do its will.

Unless Cabinet Office officials take on more power and control of largely autonomous departments – and overcome the uncertainties over who would take responsibility if all goes wrong – the Implementation Plan could turn out to be another government document that states good intentions and not the means to carry them through.

It’s as if the Cabinet Office has told departmental officials to drive at a maximum speed of 50mph when on official business to cut fuel costs. Will anyone take notice unless the speed limit is monitored? It’s the policing, monitoring and open objective reporting of the Implementation Plan’s intentions that will count.

Otherwise who cares about nameless officials making 100 pages of boasts and promises, even if the proof-reading is impressive and the diagrams look good if you don’t try to follow their meaning?

SMEs and agile to play key role as Government launches ICT plan.

Cabinet Office’s Government ICT Strategy – Strategic Implementation Plan.

Puffbox analysis of Implementation Plan.

Is there a useful job for the Cabinet Office?

SMEs and Agile to play key role as Government launches ICT plan to deliver £1.4bn of savings

By David Bicknell

Cabinet Office minister Francis Maude has launched a plan to implement the Government’s ICT strategy which it says will deliver around £1.4bn of savings within the next 4 years and help deliver better public services digitally. 

In its foreword to the Strategic Implementation Plan, the Government says it is committed to reducing waste and delivering modern public services at lower cost:

We have already saved hundreds of millions of pounds in 2010/11 by stopping or reducing spend on ‘low value’ ICT projects. These quick wins demonstrate what can be achieved by taking a whole of government approach and challenging the way we operate and provide services.

The Government ICT Strategy, published in March 2011, described our longer term programmes of reform to improve Government ICT and deliver greater savings. This Strategic Implementation Plan provides a reference for central government and is designed to be read alongside the Government ICT Strategy.

“Our plans are focused on standardising government ICT. In the past, government departments worked to their own requirements and often procured expensive bespoke ICT systems and solutions to meet them. As a result, departments have been tied in to inflexible and costly ICT solutions which together have created a fragmented ICT estate that impedes the efficiencies created by sharing and re-use. It also prevents government from offering joined-up, modern, digitally-based public services that are suited to local requirements.

“Affordability in the current ‘age of austerity’ requires a different approach. The approach set out in this plan ensures that departments will now work in a collegiate way, underpinned by rigorous controls and mandates.

“This is not just a plan to reduce the cost and inefficiency of departmental ICT.  Effective implementation of the Strategy has already begun in programmes that will radically reform front line public services. For example, the Universal Credit programme is one of the first ‘Digital by Default’ services, using an Agile approach to reduce delivery risk and improve business outcomes. 

“Success or failure of government ICT depends on greater business preparedness, competency in change management and effective process re-engineering. That is why, although we focus on the common infrastructure as a way of significantly reducing costs, the ICT Strategy (and this plan) recognises the need for a change in our approach to ICT implementation. In particular, implementation will be driven through the centre, as a series of smaller, local ICT elements, rather than ‘big bang’ programmes that often fail to deliver the value required.”

Significantly, the government says it will continue to reduce waste by engaging SMEs:

“Building on the £300 million already saved (from May 2010 – March 2011) by applying greater scrutiny to ICT expenditure, government will continue to reduce waste by making it easier for departments to share and re-use solutions through the creation of an ICT Asset and Services Knowledgebase, applications store, using more open source, and improving the ICT capability of the workforce. At the same time, it will reduce the risk of project failure and stimulate economic growth by adopting agile programme and project management methods and reforming procurement approaches to make it easier for SMEs to bid for contracts. 

“For all relevant software procurements across government, open source solutions will be considered fairly against proprietary solutions based on value for money (VFM) and total cost of ownership. Success will be measured initially by a survey of each department’s compliance with the existing open source policy. Longer term, open source usage will be measured annually by the use of a departmental maturity model. The ICT Asset and Services Knowledgebase will be used to record the reuse of existing open source solutions, and the deployment of new open source solutions.”

Specfically on procurement, the Government says it has the potential to leverage its huge buying power in the ICT marketplace. But it admits that government procurement of ICT “has in some cases failed to deliver economies of scale and failed to deliver value for money to the taxpayer.”

The government says its objective is to “reform government procurement through the centralisation of common goods and services spend by funding improvements in technology, processes and government wide procurement resources to better manage total procurement spend and government wide standards, such as those for green ICT.”

“Government is therefore committed to become a single and effective ICT customer, leveraging buying power whilst remaining flexible on how it procures. As part of this process government will create a more open, transparent and competitive ICT marketplace embracing open standards and open source that will remove barriers to SME participation in public sector procurement to create a fairer and more competitive marketplace.

Government Procurement has a number of strategic goals, including to:

  • create an integrated Government Procurement (GP) to deliver and manage the Operating Model for Centralised Procurement for all common goods and services including ICT, delivering cost reductions in excess of 25% from the 2009/10 baseline of £13bn;
  • transform Government Procurement Service (GPS) to be leaner, more efficient and to become the engine room of government procurement, delivering savings through sourcing, category, data and customer management across all categories of common spend including ICT;
  • formalise agreements between GPS and all departments to deliver centralised procurement and to improve capability, including within the ICT spend category;
  • deliver policy and capability improvements covering EU procurement regulations; transparency in procurement and contracting; removing barriers to SMEs; and
  • mandate open standards and a level playing field for open source; streamline the procurement process using ‘lean’ plus supporting programme to develop the capability of civil servants who lead government procurements.

The government says its key procurement metrics will be

  • Total spend under management on ICT common goods and services
  • Savings on ICT common goods and services
  • Number of ICT contracts with a lifetime value greater than £100m
  • Time to deliver ICT procurements
  • Number of active ICT procurements

On Agile, the government says many large government ICT projects have been slow to implement and technology requirements have not always been considered early on in the policy making process, resulting in an increased risk of project failure. Agile project methods, it argues, can improve the capability to deliver successful projects, allowing projects to respond to changing business requirements and releasing benefits earlier.

Its Agile objective is to improve the way in which the central government delivers business change by introducing Agile project management and delivery techniques.

By 2014, it says, Agile will reduce the average departmental ICT enabled change delivery timescales by 20%.

In delivering this, the government says it will be measured by:

  • Number of departments who have used the online Agile facility
  • Number of projects using “agile” techniques, by department
  • Total number of instances where the virtual centre of excellence has been utilised

ICT Strategy Strategic Implementation Plan

Universal Credit internal report – now published

By Tony Collins

Below is the Universal Credit Starting Gate review report that the Department for Work and Pensions refused to publish under the Freedom of Information Act.

The Treasury defines the Starting Gate review as a report on the “deliverability of major new policy and/or business change initiatives prior to public commitment to a project”.

The Starting Gate report on Universal Credit was obtained from the House of Commons’ library by Conservative MP Richard Bacon. It appears that the Cabinet Office’s Chief Operating Officer Ian Watmore asked the DWP to release the report to the Public Accounts Committee after Bacon’s request.

This is the first time all the sections of the report have been published on a website. The report is dated March 2011. No later assessment of the IT aspects of Universal Credit is available. UC is the government’s biggest IT-based project based on agile principles.

Starting Gate review: Universal Credit
Version number: Final
Date of issue: 8 March 2011
Name of Sponsor
(Senior Responsible Owner)
Terry Moran, Director-General Universal Credit,DWP
 Department: Department of Work and Pensions (DWP)
Review dates: 28 February 2011–4 March 2011

Introduction

1 The White Paper “Universal Credit: welfare that works”, published on 11 November 2010, sets out the Coalition Government’s plans to introduce legislation to reform the welfare system by creating a new Universal Credit (UC). The main policy intent is a radical simplification of the system to make work pay and to combat worklessness and poverty.

2  On16 February 2011the Welfare Reform Bill was introduced to Parliament. The Bill introduces a wide range of reforms to make the benefits and tax credits system fairer and simpler by:

  • creating the right incentives to get more people into work by ensuring work always pays;
  • protecting the most vulnerable in society;
  • delivering fairness to those claiming benefit and to the tax payer.

The aim is to introduce UC from October 2013.

3  The delivery of Universal Credit has a core dependency on HMRC’s Real Time Information (RTI) programme which will collect Pay-As-You-Earn (PAYE) and other earnings information from employers dynamically as they run their payroll system.  To realise UC objectives, theRTItimetable has been designed to enable a controlled “go-live” from April 2012 and start a phased migration of employers.

Starting Gate review

4  This is a Starting Gate review report.  Starting Gate is an assurance tool of the Major Projects Authority in the Cabinet Office designed for Government Departments, their Agencies and NDPBs. Starting Gate reviews are intended to help Departments working on major high risk policy initiatives before these reach the stage of formal delivery projects or programmes. The aim is to provide an independent, constructive snapshot assessment of key issues and risks, and proposals or recommendations to enhance the prospects of successful implementation.

 Acknowledgements

5  The Review Team (RT) would like to thank the SRO and Programme team for the excellent logistical support and documentation which has helped us in our evaluation.

 Scope of review

6  The scope of this review is to assess the overall deliverablity of the Universal Credit programme with a specific focus on:

  • project structure and governance;
  • the dependency on HMRC’sRTIprogramme, and contingencies if that is delayed;
  • changing customer behaviour (ie increased use of on-line services):
  • testing the risks and benefits of applying the Agile methodology (eg the promise of completed products of lasting value at each stage; the fit with normal business cycle; and the rules on accountability).

SUMMARY OF RECOMMENDATIONS

Recommendation Section Page
The programme, in conjunction with the wider business, develops a roadmap depicting how existing benefits will be managed in the future, specifically but not exclusively, Housing Benefit for Pensioners, Disability Living Allowance. Scope of programme 5
The programme reviews their project governance structures to ensure the optimal board structure is in place, providing a hierarchy of decision making bodies, from the Agile design workshops to the Programme Board.  Ensure each board has clear terms of reference, are aware of their decision making powers and the correct escalation route. Structure and governance 6
The programme should formally assess themselves against the NAO list of common causes of project failure to identify potential ‘danger zones’ that they can plan to mitigate.  Also use the expertise gained by HMRC andASDas a valuable insight to successful delivery and avoiding past mistakes. Communications strategy 6
The programme to establish a comprehensive communications strategy and supporting plan.  Although customers and staff were highlighted above the strategy should include all interested parties, and specifically those with a dependency on or to the programme. Communications strategy 6
The programme to work closely with other government departments to identify where there may be opportunities to link with their activity in order to enhance UC’s chances of success. Dependencies 7
The programme to set up a working group to look at the set of complex cases to see if there are alternative handling options for these cases but with the ultimate payment coming through Universal Credit. Changing customer behaviour 8
DWP, with guidance and assistance from the MPA, produces an Integrated Assurance and Approvals Plan (IAAP) by the end of March 2011. Agile 9

DELIVERABILITY

7  The SRO requested the RT’s overall views.

8  The review team finds that the Programme has got off to an impressively strong start given the demanding timetable and complexity of the design and interdependency with other departments.  This involves liaison with HMRC in particular, but also with CLG and local government in respect of the replacement of Housing Benefit as part of the Universal Credit.  We found that the foundations for a delivery Programme are in place – clear policy objectives, a coherent strategy, Ministerial and top management support, financial and human resources – with no obvious gaps.  The strong working relationship with HMRC and the inclusive approach with other key stakeholders within and outsideDWPhave quickly established a high level of common understanding.  All this gives a high degree of confidence that, notwithstanding the inherent challenges, the programme can deliver Universal Credit.

9  There is a greater degree of uncertainty around the achievability of the intended economic outcomes because of factors which are not within DWP’s control e.g. the general state of the economy and availability of jobs.  There are other risks which derive from trying new approaches: the Agile methodology offers much promise but it is unproven on this scale and scope.  The actual response of different customer groups to UC may pose a risk to its transformational impact if, for example, factors other than net pay turned out to be a greater barrier to take up of work than expected.  The development of a range of approaches to contingency planning (which could be beyond changes to UC) could cover off unintended customer behaviour, whether “no change”, or “change for the worse”.

ASSESSMENT

Scope of programme

10  The Review Team (RT) recognises the challenges that delivering into an organisation already undergoing substantial change through restructuring presents.  In order to have the best chance of determining the most appropriate delivery model and developing credible and effective transition plans to deliver a ‘world class’ service, early decisions on the shape of the organisation would be immensely helpful.

11  There is a very real danger that due to a number of factors, including restructuring, headcount reductions, and uncertainty about the delivery model, the department may lose some of the expertise that it will need in order to deliver Universal Credit successfully.  There is also the challenge of maintaining staff morale during a period of uncertainty, to ensure the quality of service for the existing service is not impacted.  The review team felt that this was sufficiently visible to the Programme and that the risk was being managed at this stage.  Once the delivery model is known and the Programme moves nearer to transition, this risk will need more focus.

12  During the review, a number of interviewees raised the topic of the scope of both the Universal Credit and the Universal Credit IT platform and associated systems.  What was not obvious was whether there was a consensus on whether the Universal Credit platform was being designed as a strategic platform with potential for re-use across a number of other DWP payments, or whether it was solely a platform to pay Universal Credit.

13  Given the Coalition Government’s desire to see re-use built into IT systems from the outset, it would be prudent to consider opportunities for this now.  The review team felt that a roadmap, identifying what was definitely within the Universal Credit boundary, what could be paid by the Universal Credit platform at a future date, and what was definitely out of scope, would be beneficial.  The roadmap should also indicate how the ‘out of scope’ payments are to be handled and assign ownership.  This would be a useful departmental tool to provide clarity to stakeholders both within the Department and those that are impacted outside of DWP.

Recommendation:

The Programme, in conjunction with the wider business, develops a roadmap depicting how existing benefits will be managed in the future, specifically but not exclusively, Housing Benefit for Pensioners, Disability Living Allowance.

Project Structure and Governance

14  The importance of the programme is evidenced by the amount of commitment and support it received during the review.  The appointment of dedicated, experienced and well respected personnel into the key programme roles is seen as very positive and welcome.

15  In terms of structure the proposal to keep the programme’s core team to a minimum whilst commissioning involvement and support from key areas as necessary was generally well supported, However, the impact of any organisational redesign to meet the SR challenges was raised as a key risk to delivery.  As mentioned above, this is an issue the programme is aware of within their risk log.

16  It is recognised in order for the programme to get to their current position is has been necessary to establish a Programme Board which allows all interested parties a voice.  The review team found the time was now right to review the membership and frequency of the Programme Board and supporting structures to allow empowered decisions to be taken at the right level.

17  In reviewing the programme structure it is important that stakeholders retain a voice although not a decision making responsibility.  There was evidence that the programme board had recognised this and consideration was being given to a stakeholder forum.

Recommendation:

The programme reviews their project governance structures to ensure the optimal board structure is in place, providing a hierarchy of decision making bodies, from the Agile design workshops to the Programme Board.  Ensure each board has clear terms of reference, are aware of their decision making powers and the correct escalation route.

 Communications Strategy

18  Communications are key to the successful delivery of the programme on many levels, the review highlighted concerns in three specific areas:

a)      Lessons Learned – The scale and complexity of the programme is recognised as a key risk, however there are many sources of information which could help minimise this risk.  These include the recent NAO review “Assurance of High Risk Projects” which produced a list of the top reasons for project failure; the lessons learned by HMRC with the introduction of Tax Credits and more recently the PAYE modernisation programme; and the very recentASDexperience of using Agile as a development tool.

Recommendation:

The programme should formally assess themselves against the NAO list of common causes of project failure to identify potential ‘danger zones’ that they can plan to mitigate.  Also use the expertise gained by HMRC and ASD as a valuable insight to successful delivery and avoiding past mistakes. 

b)      Customers and Customer Groups – The valuable work already undertaken by the Customer Insights team was greatly applauded and there was a recognition that this should definitely continue and grow.  Concerns were raised about the need to ensure communications with customers and those groups representing customer interests were started early, dispelling myths and unfounded concerns whilst providing the foundations for the cultural and behavioural changes that will be needed.

c)      Internal Staff – The uncertainly of the operational delivery model and the known efficiency challenge highlighted concerns about the need to engage with staff, providing up to date, clear information about what decisions had been taken, what were planned and the timescales.

Recommendation:

The programme to establish a comprehensive communications strategy and supporting plan.  Although customers and staff were highlighted above the strategy should include all interested parties, and specifically those with a dependency on or to the programme.

Dependencies

19  Successful delivery also involves the active management of key relationships and dependencies.  It is recognised by all parties that there is a need for the programme to work with colleagues in DWP, HMRC and Local Authorities. The foundations for these relations are established and embedded in the membership of the key stakeholder and governance boards.

20  Whilst the review highlighted a number of inter-dependencies between Universal Credit and the existing DWP change portfolio, specifically Automated Service Delivery, Transforming Labour Market Services, IB Reassessment and the Work Programme, it is recognised that work has already been commissioned to provide an impact analysis assessment for the Investment Committee.

21 The review did however highlight areas where the programme could potentially utilise (or extend existing engagement with) the expertise and activities of other Government departments:

  • Cabinet Office: continue the engagement on cyber security to ensure security features are built in from the start. The RT noted the involvement of the appropriate agencies.
  • HMT: work to understand the Labour Market forecasts/trends which will provide information on the wider environment.
  • BIS: work to provide information on skills sought by employers.

Recommendation:

The programme to work closely with other government departments to identify where there may be opportunities to link with their activity in order to enhance UC’s chances of success.

HMRC’s Real Time Information (RTI) programme

22  The RT finds that bothDWPand HMRC are clear that timely delivery of RTI is a hard dependency for UC.   The joint framework established between the two departments at strategic, policy and operational levels has worked well to date to achieve rapid progress on areas of shared concern. There is a Universal Credit high level programme delivery plan including RTI;  a common change control mechanism is under discussion; the Welfare Reform Bill team has contact details for key HMRC officials and should be encouraged to engage them wherever needed during the passage of the Bill.  This is a strong foundation for the further detailed work that is needed such as a clear and agreed critical path showing key decision points.

23  The RT notes a strong commitment by Ministers and top management engagement in and support for this framework – a known critical success factor for major programmes in both the public and private sector.  Such support will be ever more important as the challenges of delivery increase in a timetable which, all acknowledge, is tight and poses a significant risk.  A restructured Programme Board (see section on governance), overseen by the Ministerial and top management Group, will be essential to maintaining collaborative management.

24  Detailed work is underway to develop a model for scaling up the non PAYE-RTI solution – a self-reporting system for the self-employed – as a contingency for delay of the required RTI service. (This will need to include the impact of the delivery model for UC, on which a decision is expected before Easter.)  The customer journey work will enable the identification of categories of customer claims which could, in principle, offer early “success stories” from a policy perspective and be processed under a non RTI-dependent system.   These options are work in progress and will need to be costed.

25  Contingency has been provided for in respect of other anticipated risks.  For example, the RTI testing period, envisaged to start in April 2012, has some “stretch” to allow for changes to the RTIBuild specification which could arise from the completion of the RTIDesign phase which runs beyond the letting of the Build contracts in May, or in response to late amendments to the Welfare Reform Bill.

Changing customer behaviour

26  The review team felt that the work that has been undertaken through the Customer Insights Team and the User Centre Design activity was a positive indicator that the customer feedback was being taken seriously from the outset, and was helping to shape both the policy and the system with which to deliver the policy.  It was seen by the review team as essential that this engagement with the customer base continues throughout the process.  The department however, should not underestimate the challenge to its staff in taking on a new customer base (i.e. working customers) and every effort should be made to transfer the learning and experience of those already dealing with these customers into the new delivery model.

27   Although the desire is to encourage customers to change their behaviour and to make the transition into work easier, this cannot be done through the implementation of Universal Credit in isolation.  A sustained programme of education and support through wider welfare reform activities will be needed to achieve this and the Programme should maintain links with those other areas of activity throughout.  One risk with any programme of work designed to change behaviour is that in an attempt to encourage people to make the move one way, there is an unintended consequence and behaviour is driven in the wrong direction.  The Programme should use the Customer Insights Team and the user centre design activity to provide an early warning of the likelihood of this happening.

28  One of the key principles of the new Universal Credit is simplicity and the importance of this was reiterated to the review team on a number of occasions.  One of the biggest challenges for the Programme is to maintain that simplicity but to still make provision within the system to deal with the most difficult and complex cases.  It is not feasible to have a system which does not cater for the customer base in its entirety but the Programme may wish to consider whether there are alternative ways of handling the minority group of customers with the most extreme complex cases in order not to compromise the integrity of the system and the over-arching simplicity of Universal Credits.

Recommendation:

The programme to set up a working group to look at the set of complex cases to see if there are alternative handling options for these cases but with the ultimate payment coming through Universal Credit.

29  Another challenge for the programme is the desire to move the majority of customers to on-line services.  This will present some difficulties and it may be beneficial to engage other organisations that have achieved this to understand the methodologies or tools they have used.

Agile

30  The challenging timetable for delivery of UC meant that DWP elected to use an Agile approach to the delivery. There is no evidence of such a methodology being used on a public sector programme of such scale and during the course of the review it was evident that there had been some initial scepticism to the use of such a methodology with a programme of this scale. However, during the review there was overwhelming evidence of buy-in to the methodology at all levels up to and including the highest levels. DWP have set about thoroughly educating all involved on what can be expected from them and there was clear evidence within the interviews that this is being taken up enthusiastically.

31  There was a view that policy decisions being made later in the programme would pose a problem for delivery. This was countered by the view that the methodology should allow decisions to be made when they need to be made, which is in contrast to fixing requirements early in more traditional (‘waterfall’) methodologies. On balance, the review team found that the use of the chosen methodology here was judged by interviewees to provide greater assurance of delivery in such an environment. The review team agrees with this finding.

32  In terms of the use of Agile within Government,DWPalso have the best current experience via their Automated Service Delivery (ASD) Programme, which used a slightly less ‘lean’ version of the methodology based on an Accenture interpretation. However, there are still valuable lessons that can be transferred from this programme and there exists experience that is being directly deployed on UC. The review team felt that whilst effectively piloting this methodology on a programme such as UC did pose a risk, this was acceptable in view of the risk of delivery out of line with expectations, for example in terms of timing or quality of service to the public.

33  Accenture remain involved in UC, although DWP have brought in consultants (Emergn) to provide an independent methodology not based on any ‘out of the box’ methodologies, but rather one that Emergn have tailored. New contracts supporting this development are due to be awarded in June 2011 and DWP state that their use of this independent methodology will serve to remove any supplier advantage.

34  There was evidence that DWP have understood the need for decision-making delegated to the level at which the expertise exists, with the appropriate empowerment supported within the planned governance re-design. There was also an acknowledgement that the right domain/business knowledge needs to be made available at the workshops that will drive the detailed design processes. It was also accepted that there is a continuing need for this knowledge to be made available and also that it will need to keep pace with the changing policy.

35  One key risk identified by DWP is how an Agile methodology will interact successfully with the various approvals processes that will come into play across the programme – most especially the ICT Spend Approval process (formally known as the ICT Moratorium Exception process). Engagement has begun already with the Major Projects Authority (MPA) on designing the Integrated Assurance and Approval Plan (IAAP) that will ensure the correct internal and external assurance is brought to bear for the identified approval points. The production of this plan is seen by the review team as a key mitigating factor for the risk identified and it is recommended that this is produced, with MPA guidance, by the end of March 2011 at the latest. This may need fine-tuning as approval points are finally agreed.

Recommendation:

DWP, with guidance and assistance from the MPA, produces an Integrated Assurance and Approvals Plan (IAAP) by the end of March 2011.

36  As noted earlier, there are contracts that are relevant to this development that are being re-competed at this time, with a wish to award in June 2011. There was some evidence that the design of contracts to deliver in an Agile environment will require a different design in order to draw out supplier behaviour in line with an accelerated delivery environment.

37  There is a always the risk that any development methodology will fail to deliver and whilst this methodology itself provides early warning of failure, there is recognition that in such a circumstance the prioritisation of customer journeys with high-value returns would be needed.

38  There was much evidence of the reliance of UC on successful delivery of the HMRC PAYE Real-Time Information (RTI) programme. There was also recognition that whilst ‘just-in-time’ decisions as a consequence of policy development could be made within UC, the RTI requirement would need to be more rigidly fixed as the traditional ‘waterfall’ development methodology in use cannot so easily absorb such changes without consequence.

39  There was some concern that fraud would remain a major issue for UC and appropriate Information Assurance should be built into the requirement from the outset – rather than being a ‘bolt-on’. Also, as UC and its interface with PAYERTI will become part of the UK Critical National Infrastructure, appropriate discussions should be maintained. There was evidence that DWP have gripped these requirements.

40  Overall, the use of an Agile methodology remains unproven at this scale and within UK Government; however, the challenging timescale does present DWP with few choices for delivery of such a radical programme. That said, there has been evidence of strong support at all levels and DWP do have some expertise within their own organisation that they can call upon from the outset. The review team not only felt that an Agile development is an appropriate choice given the constraints, they also believe that DWP are well placed with their level of support, knowledge and enthusiasm to act as a pilot for its use at such a scale.

 

Compound failure

41 DWP has made a strong start in identifying risks to delivery.   This could be developed further by thinking through the likelihood and impact of a number of risks being realised simultaneously (eg lack of synchronisation between reduced income and UC top-up, plus wrong employer data plus labour market downturn).and what the responses might be.  The programme could extend its preparedness by drawing on a wider range of experience the elements of recovery and their prioritisation; and test their robustness in advance, including an early warning system for Ministers.

Next independent external assurance

To be identified in the Integrated Assurance and Approvals Plan (IAAP) to be presented to the Programme Board w/b 21 March.

The Programme is scheduled for formal internal DWP “Gate zero” acceptance at an Investment Committee (IC) meeting on 21 April.

**

Thank you to Richard Bacon for obtaining a copy of the Starting Gate review. Bacon had requested a copy from Joe Harley, Government CIO and CIO at the DWP. Ian Watmore, Chief Operating Officer at the Efficiency and Reform Group, Cabinet Office agreed to supply Bacon with a copy as per the following exchange at a hearing of the Public Accounts Committee on 16 May 2011:

Bacon: “You sounded quite confident about universal credit. Will you send us the initial gateway review for universal credit?”

Harley: “The starting gate review?”

Watmore:  “The starting gate review. I don’t have a problem with that.”

After the hearing when the DWP refused our FOI request for a copy of the UC Starting Gate review report, it said that publication was not in the public interest. We can see nothing in the report that justifies the DWP’s claim. That said accountability and transparency are not the DWP’s defining characteristics.

Links:

Open Government? – Up to a point Lord Copper.

DWP FOI team hides already released report.

Agile and Universal Credit

Agile for Universal Credit – a good choice says report

By Tony Collins

Universal Credit is one of  the government’s biggest IT-based projects and the biggest test for agile in the public sector. It is due to start rolling out in April 2013.

The choice of agile for the scheme is supported by a “Starting Gate” review which was carried out for the Cabinet Office’s Major Projects Authority, and for Terry Moran, the Director-General, Universal Credit at the Department for Work and Pensions. The review was carried out between 28 February 2011 and 4 March 2011.

This is what the Starting Gate report says on agile aspects of the project.

Agile

The challenging timetable for delivery of UC meant that DWP elected to use an Agile approach to the delivery. There is no evidence of such a methodology being used on a public sector programme of such scale and during the course of the review it was evident that there had been some initial scepticism to the use of such a methodology with a programme of this scale.

However, during the review there was overwhelming evidence of buy-in to the methodology at all levels up to and including the highest levels. DWP have set about thoroughly educating all involved on what can be expected from them and there was clear evidence within the interviews that this is being taken up enthusiastically.

There was a view that policy decisions being made later in the programme would pose a problem for delivery. This was countered by the view that the methodology should allow decisions to be made when they need to be made, which is in contrast to fixing requirements early in more traditional (‘waterfall’) methodologies.

On balance, the review team found that the use of the chosen methodology here was judged by interviewees to provide greater assurance of delivery in such an environment. The review team agrees with this finding.

In terms of the use of Agile within Government, DWP also have the best current experience via their Automated Service Delivery (ASD) Programme, which used a slightly less ‘lean’ version of the methodology based on an Accenture interpretation.

However, there are still valuable lessons that can be transferred from this programme and there exists experience that is being directly deployed on UC. The review team felt that whilst effectively piloting this methodology on a programme such as UC did pose a risk, this was acceptable in view of the risk of delivery out of line with expectations, for example in terms of timing or quality of service to the public.

Accenture remain involved in UC, although DWP have brought in consultants (Emergn) to provide an independent methodology not based on any ‘out of the box’ methodologies, but rather one that Emergn have tailored.

New contracts supporting this development are due to be awarded in June 2011 and DWP state that their use of this independent methodology will serve to remove any supplier advantage.

There was evidence that DWP have understood the need for decision-making delegated to the level at which the expertise exists, with the appropriate empowerment supported within the planned governance re-design.

There was also an acknowledgement that the right domain/business knowledge needs to be made available at the workshops that will drive the detailed design processes. It was also accepted that there is a continuing need for this knowledge to be made available and also that it will need to keep pace with the changing policy.

One key risk identified by DWP is how an Agile methodology will interact successfully with the various approvals processes that will come into play across the programme – most especially the ICT Spend Approval process (formally known as the ICT Moratorium Exception process).

Engagement has begun already with the Major Projects Authority (MPA) on designing the Integrated Assurance and Approval Plan (IAAP) that will ensure the correct internal and external assurance is brought to bear for the identified approval points. The production of this plan is seen by the review team as a key mitigating factor for the risk identified and it is recommended that this is produced, with MPA guidance, by the end of March 2011 at the latest. This may need fine-tuning as approval points are finally agreed.

Recommendation:

DWP, with guidance and assistance from the MPA, produces an Integrated Assurance and Approvals Plan (IAAP) by the end of March 2011.

As noted earlier, there are contracts that are relevant to this development that are being re-competed at this time, with a wish to award in June 2011. There was some evidence that the design of contracts to deliver in an Agile environment will require a different design in order to draw out supplier behaviour in line with an accelerated delivery environment.

There is a always the risk that any development methodology will fail to deliver and whilst this methodology itself provides early warning of failure, there is recognition that in such a circumstance the prioritisation of customer journeys with high-value returns would be needed.

There was much evidence of the reliance of UC on successful delivery of the HMRC PAYE Real-Time Information (RTI) programme. There was also recognition that whilst ‘just-in-time’ decisions as a consequence of policy development could be made within UC, the RTI requirement would need to be more rigidly fixed as the traditional ‘waterfall’ development methodology in use cannot so easily absorb such changes without consequence.

There was some concern that fraud would remain a major issue for UC and appropriate Information Assurance should be built into the requirement from the outset – rather than being a ‘bolt-on’. Also, as UC and its interface with PAYERTI [PAYE RTI] will become part of the UK Critical National Infrastructure, appropriate discussions should be maintained. There was evidence that DWP have gripped these requirements.

Overall, the use of an Agile methodology remains unproven at this scale and within UK Government; however, the challenging timescale does present DWP with few choices for delivery of such a radical programme.

That said, there has been evidence of strong support at all levels and DWP do have some expertise within their own organisation that they can call upon from the outset. The review team not only felt that an Agile development is an appropriate choice given the constraints, they also believe that DWP are well placed with their level of support, knowledge and enthusiasm to act as a pilot for its use at such a scale.

Compound failure

DWP has made a strong start in identifying risks to delivery.   This could be developed further by thinking through the likelihood and impact of a number of risks being realised simultaneously (eg lack of synchronisation between reduced income and UC top-up, plus wrong employer data plus labour market downturn).and what the responses might be.

The programme could extend its preparedness by drawing on a wider range of experience the elements of recovery and their prioritisation; and test their robustness in advance, including an early warning system for Ministers.

Agile and Universal Credit – Secret report.

Agile can fix failed GovIT says lawyer.

Agile and Universal Credit – secret report

By Tony Collins

Below are excerpts  from the supposedly confidential “Starting Gate” report by the Cabinet Office’s Major Projects Authority on Universal Credit.

The main finding is that, despite inherent challenges, “the programme can deliver Universal Credit”.

Media reports on Universal Credit have depicted the scheme as an impending disaster that may blight the coalition in the run-up to the next general election, but the Authority’s report says the programme has got off to an impressively strong start.

This will encourage advocates of agile in government as Universal Credit is the Government’s biggest agile development.

We requested the Starting Gate report on Universal Credit under the Freedom of Information Act but the Department for Work and Pensions refused to release it; and turned down our appeal.

We obtained the report outside the FOI Act, via the House of Commons Library. It appears that one part of the DWP was trying to keep the report secret while another part had released it to two Parliamentary committees [the Public Accounts Committee and the Public Administration Select Committee].

It may be that the DWP, when it comes to FOI, doesn’t know clearly what it’s doing – or is all but indifferent to the FOI Act and chooses secrecy to keep things simple. The DWP’s FOI reply to us was, at best, in  perfunctory compliance with the FOI Act. It made no attempt to set out the arguments for its decision not to disclose the report, other than to say disclosure was not in the public interest.

The Starting Gate  report was dated March 2011 and was largely positive about the start of the Universal Credit . These were some of the findings.

Deliverability

“The review team finds that the Programme has got off to an impressively strong start given the demanding timetable and complexity of the design and interdependency with other departments.

“This involves liaison with HMRC in particular, but also with CLG and local government in respect of the replacement of Housing Benefit as part of the Universal Credit.

“We found that the foundations for a delivery Programme are in place – clear policy objectives, a coherent strategy, Ministerial and top management support, financial and human resources – with no obvious gaps.

“The strong working relationship with HMRC and the inclusive approach with other key stakeholders within and outside DWP have quickly established a high level of common understanding.  All this gives a high degree of confidence that, notwithstanding the inherent challenges, the programme can deliver Universal Credit.

“There is a greater degree of uncertainty around the achievability of the intended economic outcomes because of factors which are not within DWP’s control e.g. the general state of the economy and availability of jobs.

“There are other risks which derive from trying new approaches: the Agile methodology offers much promise but it is unproven on this scale and scope.  The actual response of different customer groups to UC may pose a risk to its transformational impact if, for example, factors other than net pay turned out to be a greater barrier to take up of work than expected.

“The development of a range of approaches to contingency planning (which could be beyond changes to UC) could cover off unintended customer behaviour, whether ‘no change’, or ‘change for the worse’.”

Campaign4Change will publish more excepts next week.

Links:

Agile can fix failed Gov’t IT says lawyer

DWP FOI team hides Universal Credit report

Universal Credit – guaranteed to fail?

DWP gives IBM and Capgemini 60 application maintenance and development apps

DWP partners with IBM to help deliver Universal Credit