Category Archives: culture

Whitehall to relent on secrecy over mega projects – after 10-year campaign?

Posted on 29/05/2012 | 1 comment

By Tony Collins

The Cabinet Office may be about to change its decade-old policy of not publishing reports on  the progress or otherwise of its large, costly and risky IT-based projects.

A change of policy from secrecy to openness would give MPs and the public warning of when a major project is in trouble and needs rescuing or cancelling.

Parliament last to know

For more than a decade campaigners have sought to persuade successive governments to publish “Gateway” reviews, which are short independent audits on the state of big projects.  The secrecy has meant that Parliament is usually the last to know when new national schemes go wrong. IT-related failures have hit many public services including those related to tax, benefits, immigration, passports, the fire service, prisons, schools examinations, student loans, the police and health services.

Now Sir Bob Kerslake, head of the civil service, has hinted to campaigning Conservative MP Richard Bacon that the Cabinet Office may change its policy and publish the “red, amber, green” status of large projects as they are routinely assessed.

Kerslake was replying to Bacon at a hearing of the Public Accounts Committee meeting on transparency. Bacon pointed out at the hearing that the Public Accounts Committee had, years ago, called for Gateway reviews to be published.

Not learning from mistakes

“Something I have always been puzzled by is why government does not learn from its mistakes particularly but not only in the area of IT where things go wrong again and again, again and again,” said Bacon. “I have come to the conclusion government does not learn from its mistakes because it does not have a learning curve. If you don’t have a learning curve you are not going to learn.”

He cited the example of how Ian Watmore, Permanent Secretary at the Cabinet Office, had, at Bacon’s request, arranged for an “Opening Gate” report on Universal Credit to be published in the House of Commons library.

But, said Bacon, when an IT journalist applied to the Department for Work and Pensions, under the FOI Act, for the release of all Gateway reports on Universal Credit, the DWP would not publish any of them  – and even refused an FOI request to release the report Watmore had arranged to be placed in the House of Commons library, which Bacon obtained.  “So there is still a culture of intuitive, instinctive secrecy,”  Bacon said. Kerslake replied:

“Yes, actually we are looking at this specific issue as part of the Civil Service Reform Plan….I cannot say exactly what will be in the plan because we have not finalised it yet, but it is due in June and my expectation is that I am very sympathetic to publication of the RAG [red, amber, green] ratings.”

Bacon pointed out that the Cabinet Office Structural Reform Plan Monthly Implementation Updates had said Gateway reviews would be published.  But the commitment was removed for no apparent reason. When the Cabinet Office was asked why,  it said the Structural Reform Plans were only ever “drafts”.

Bacon asked Kerslake if the Government now plans to publish the Gateway reports.  “The Cabinet Office Structural Reform Plan Monthly Implementation Updates originally said Gateway reviews would be published  and then it somehow got downgraded into a draft; and from what’s publicly available at the moment the position of the government is not to publish Gateway reviews.  You sound as if you’re saying that’s going to change. Is that right?” asked Bacon.

“Watch this space,” replied Kerslake. “I am sympathetic. I generally broadly welcome, in principle, the idea of publishing information but there are lots of risks …”

Peter Gershon introduced Gateway reviews when he was Chief Executive of the Office of Government Commerce, which is now part of the Cabinet Office’s Efficiency and Reform Group. The reviews are carried out at key decision times in a project and are sometimes repeated:

  • Gateway Review 0 – Strategic assessment
  • Gateway Review 1 – Business justification
  • Gateway Review 2 – Procurement strategy
  • Gateway Review 3 – Investment decision
  • Gateway Review 4 – Readiness for service
  • Gateway Review 5 – Benefits realisation

Are Gateway reviews a success?

Gateway reviews are now supplemented by regular assurance audits carried out for the Cabinet Office’s Major Projects Authority. None of the reports is published.

Gateway reviews have not stopped costly failures such as Firecontrol or the NPfIT.  One permanent secretary told an MP that the reviews in his department were considered unimportant by senior responsible owners, for whom the reports are written. This may be because SROs often have charge of many projects; and even their SRO responsibilities are often in addition to their main jobs.

But Gershon had high hopes of Gateway reviews when they were introduced in February 2001. This is evident from the number of times he referred to Gateway reviews at one hearing of the Public Accounts Committee in December 2001.

 “… as the Gateway review process cuts in, which I have referred to on a number of occasions when I have appeared at this Committee …”

“… Through things like the Gateway process we are helping to sharpen the focus on the whole life aspects of these and other forms of complex projects in public sector procurement…”

“ …First, we have the introduction of the Gateway review process…”

“ … The Gateway process is a demonstrable example of how we have introduced a technique to support that whole life approach…”

“… If you look at the guidelines around the Gateway review process that is one of the things that is tested by these independent reviews …”

“… we recognised that that was a problem some time ago, which is why in the Gateway review one of the things that is explicitly tested is things like the skills and capabilities of the team at the design and build stage and that the skills and capabilities of the team at the procurement stage …”

“… in this area with the Gateway review process, from when we first launched it last February, we have been helping the department take a whole life approach to these forms of complex projects …”

“… Part of the Gateway Review process is to get a much sharper insight on to where we see good things happening where we can encourage other clients to replicate them…”

“… Now, with the Gateway Review process, my experience has been because of where we have deliberately focused the attention on the early life of projects where there is the greater scope for management to take corrective action, the accounting officers are paying a lot of attention to the recommendations that are emerging because, much to my surprise, most of them do not seem to like coming here defending what has gone wrong in the past. They seem to welcome the recommendations that we are providing to them to help try to get projects on to much stronger foundations in the future…”

“… With the Gateway Review, my experience has been that the Accounting Officers respond to the recommendations very positively…”

“…Gateway Reviews explicitly test how the department is planning in the pre-contract phase to secure ongoing value for money in the post-contract phase…”

“… Take, firstly, the Gateway Review process. That is testing various points in the life cycle of the project, from the very earliest stage…”

“… I would certainly expect in Gateway Reviews that the review team would be testing what methods were in place to facilitate the ongoing management of the contract…”

“… I think it is encouraging that Sir Ian Byatt thought the Gateway Review process had sufficient value to recommend it in his own review…”

And so forth.

Comment:

We applaud Richard Bacon MP for his persistent call for Gateway reports to be published.

Gateway reviews have defeated expectations that they would stop failures; and the National Audit Office tells us that central departments don’t even request Gateway reviews on some big and risky projects although they are supposed to be mandatory.

But Gateway and other project assurance reports could prove invaluable if they are published. In the public domain the reports would enable Parliament and Francis Maude’s “armchair auditors” to hold officials and SROs to account for projects that are in danger of failing. That would be an incentive for officialdom to fail early and fail cheaply; and Gateway reviewers may take greater care to be neutral in their findings – not too lenient, or too harsh – on the basis that the reports would be open to public scrutiny. SROs would also have to take the review reports seriously – not just put them in a draw because nobody knows about them anyway.

We welcome Kerslake’s comments but hope that he and his colleagues plan to publish more than the RAG (Red/Amber/Green) status of projects. Otherwise they will be missing an opportunity.  Gateway reports and other assurance reviews are expensive. Reviewers can earn up to £1,000 a day. This money  could be well spent if the reviews are to be published; but it will add to public waste if the reports are kept secret and continue to be deemed pointless or unimportant by departments.

It is ironic, incidentally, that the Ministry of Justice, which introduced the FOI Act, gives advice to departments to keep the RAG status of Gateway reviews confidential. In its advice on Gateway reviews and the FOI, the MoJ tells departments that the “working assumption” is that the substance of the Gateway reports should be kept confidential until at least two years have elapsed.

It’s time for a culture change. Maybe the Civil Service Reform Plan next month will be worth reading.

1 Comment

Posted in change management, cost reduction, culture, excessive secrecy, Freedom of Information, Gateway reviews, Government IT, IT-related failures, Major Projects Authority, managing change, NHS, npfit, openness and transparency, oversight, Politics, project management, public sector, public services, Universal Credit

Tagged , , ,

Fire ‘superstations’ without software cost £1m a month – The Times

Posted on 24/05/2012 | Leave a comment

By Tony Collins

The Times reports today that taxpayers are paying more than £1m a month on the rent and upkeep of fire control rooms across England that have never been used. The purpose-built control centres look ready for immediate use, with open-plan desks fitted with desktop monitors and keyboards, and huge screens on a wall at the front of the control rooms which are supposed to help fire and rescue crews mobilise appliances and manage incidents.

Only there’s no working software.  The Department for Communities and Local Government negotiated the end of a contract with the main contractor EADS for software to run the regional control centres in December 2010. Officials concluded that the software could not be delivered within an acceptable timeframe. The regional control centres were completed before the IT project was cancelled.

The cost of the centres has been uncovered after a request under the FOI Act. The Times devotes much of its page three to a story under the headline:

Revealed: scandal of the £1m-a-month fire service ‘superstations’ lying empty.

Only one of nine regional centres is in use. The other eight incur rent, electricity, water and repair costs at £1,134,566 a month. Costs will be incurred for years because there are no break clauses in the agreements to lease the buildings. Two leases come to an end in 2027, one in 2028, two in 2032, three in 2033 and one in 2035.

A spokesman for the Department said that agreement has been reached for a further two of the buildings to be used by local fire authorities. Officials are searching for public or private sector tenants to occupy the other regional centres.

Lord Prescott, the former Deputy Prime Minister, who authorised the start of the technology project in 2004,  said he had been kept in the dark by civil servants on the rising costs of the scheme. He said it had been on budget when he left the department in 2007.

Eric Pickles, the Communities Secretary, said the failure of Firecontrol was an “expensive reminder of why you can’t trust Labour to run anything”. But the Coalition’s coming to power has not stopped central government IT-related failures.

Why Firecontrol failed

Firecontrol  followed the same tracks to a cliff edge that have caught out civil servants, ministers and suppliers on other government  computer-related projects.

The National Audit Office and the Public Accounts Committee found that  the Firecontrol project was rushed, had little support from those who would use it, costs and complexity were underestimated, there was an over-reliance on consultants and a lack of accountability for decisions made  – or not made.

The idea was to replace 46 local control rooms with nine, linked regional centres, which would be equipped with new standardised computer systems to handle calls, mobilise equipment and manage incidents.

But the project was cancelled in December 2010 with ministers unsure the technology would ever work. The NAO estimates that £469m will be wasted on the project.

The NAO found that the scheme was “flawed from the outset”, largely because local fire and rescue officers did not want regional centres or major changes in the way they worked.  Introducing any large new system is difficult but with enthusiastic support serious problems can sometimes be overcome; but introducing a complex new system without support from those who would use it means staff will have little incentive to find ways around problems.

The NPfIT [National Programme for IT in the NHS] failed in part because it lacked support among GPs and NHS staff; and the complexity of introducing standardised technology in semi-autonomous hospitals – each one with different ways of working – was underestimated. It was the same with Firecontrol.

The complexity of introducing standardised systems in regional centres with no goodwill among staff – was underestimated.  From the start many local fire and rescue officers criticised the lack of clarity on how a regional approach would increase efficiency. “Early on, the Department’s inconsistent messages about the regionalisation of the Fire and Rescue Service led to mistrust and some antagonism,” said the NAO.

The technology project was rushed while local fire crews were excluded from project discussions. “The project progressed too fast without essential checks being completed. For example Departmental and Treasury approval was given without proper scrutiny of the project’s feasibility or validation of the estimated costs and savings,” said the Public Accounts Committee. The project went ahead before the full business case was written.

A review of the project as early as April 2004 found that the scheme was already in poor condition overall and at significant risk of failing to deliver. But the “Gateway” review report was kept secret for seven years.

Is the stage set for IT disasters in government to continue? So far the Coalition has decided, like Labour, to keep secret all internal reports on the progress or otherwise of its mega projects, including Universal Credit, though the policy on secrecy may be about to change, which Campaign4Change will report on separately.

Firecontrol – same mistakes repeated on other projects.

Leave a comment

Posted in Campaign4Change, change management, consultants, culture, excessive secrecy, Freedom of Information, Gateway reviews, Government IT, IT projects, IT-related failures, local government, managing change, npfit, openness and transparency, Politics, project management, public sector, public services

Tagged , ,

Whitehall defies NAO and Cameron on publishing status of big projects

Posted on 02/05/2012 | 1 comment

By Tony Collins

Government action to cut the number of failures of big projects including those with a major ICT component has made a difference, the National Audit Office reports today.

In its report “Assurance for major projects”  the NAO is largely supportive of actions by the Government, , the Cabinet Office’s Major Projects Authority and the Treasury in setting up reviews of major high-risk projects, including ICT-based programmes, to ensure that if they are failing they are put back on track or cancelled.

The NAO says the Government’s decision to “dismantle” the NPfIT was taken after the project was assessed by the Major Projects Authority.

But the report also shows how civil servants have managed to defy a mandate from the Prime Minister, and a separate NAO recommendation in 2010, for information on the status of big ICT and other high-risk projects to be published.

Says the NAO report

“The ambition to publish project information, as part of the government’s transparency agenda, has not been met.

“Our 2010 report recommended that the government should publicly report project status. We consider that public reporting of project information is key to providing greater accountability for projects and improving project outcomes… Regular transparent reporting of performance which highlights successes and non-compliance would also help to build an enduring assurance system.”

Separately in the report the NAO says

“There has been a lack of progress on transparency.  The [Cabinet Office’s Major Projects] Authority has not yet met its commitment to publish project information in line with government’s transparency agenda. The Authority cannot deliver this objective on its own. Senior level discussions are ongoing, between Cabinet Office, HM Treasury and departments, on the arrangements for public reporting.”

Should ministers intevene to force publication?

But the NAO report does not raise the question of why ministers have not intervened to force civil servants to publish the status information on high-risk projects.

Campaign4Changehas argued that publishing status reports on big ICT projects and programmes would be the most effective single action any government could take to reduce the number of failures. (see “Comment” below)

Prime Minister’s 2011 mandate

The NAO’s 2010 recommendation for status information on major projects to be published was backed by a mandate from the Prime Minister in January 2011 which included the undertaking to “require publication of project information consistent with the Coalition’s transparency agenda”.

The House of Commons’ Public Accounts Committee has recommended that departments publish information on the state of their major IT-based projects and programmes; and the Information Commissioner has rejected civil service arguments for not publishing such information.

In addition Francis Maude, the Cabinet Office minister, said, when in opposition, that the Conservatives, if they gained power,  would publish “Gateway” review reports soon after they are completed.  Gateway reports are similar to the assurance reviews carried out for the Major Projects Authority.

Yet none of this has happened.

The “rebel” civil servants

How is it that a group of civil servants who are opposed to publishing information on the status of large risky projects can defy the Prime Minister, Francis Maude, the National Audit Office, and the all-party Public Accounts Committee? Those recalcitrant civil servants argue that assurance reviewers would not tell the whole truth if they knew their assessments would be made public.

But how do we know they tell the whole truth when the reports are kept confidential? The Information Commissioner has pointed out in the past that civil servants have a public duty to be candid and honest. If they are not because their reports are to be published, they are failing in their public duty.

Today’s NAO report says there are differences of opinion among civil servants over whether to publish status information on projects.

Says the NAO

“There has been some support for greater transparency from departments who believe that tracking and publishing major milestones could create helpful tension in the system.

“However, concerns have been raised that increased transparency could limit the value of assurance, as it could inhibit assurance reviewers and project staff holding full and frank discussions.

“Some senior project staff also have concerns that public reporting could have a negative commercial impact, and would prefer delayed rather than real-time public reporting.”

The Cabinet Office told Campaign4Change in 2010 and 2011 that instead of publishing status reports on each major project, it will publish an annual report on the state of its programmes.

But that hasn’t happened either.

Says the NAO:

“As well as the objective to publish project information, the [Major Projects] Authority has not yet met its objective to publish an annual report on government’s major projects.

“The Authority initially expected to publish an annual report in December 2011 but is now expecting the report to be published in May or June 2012. The format of the annual report, and the information it will contain, has yet to be decided.”

Comment:

Many times over the last 20 years I have said that publishing status reports on major IT-based projects and programmes would be the most effective single action any government could take to deter departments from going ahead with overly ambitious schemes that are doomed to fail. If, against good sense, impractical schemes are approved, publishing status information will make all the difference.

Permanent secretaries will not lose sleep over a failing project, but they will not want information on it published – which is why that information should be published.

Publishing status information would give civil servants a good reason to tackle weaknesses as they developed.  Permanent secretaries may not mind losing public money on a failing project or programme. They will always fear embarrassment, however.

Who is really in control of Whitehall – civil servants or No 10? David Cameron’s office has issued a mandate that requires status information on projects to be published. The NAO has issued a similar recommendation. How long can the civil service hold out against the political will?

Links:

NAO report – Assurance for major projects

Firecontrol – same mistakes repeated on other projects

1 Comment

Posted in cost reduction, culture, excessive secrecy, Freedom of Information, Gateway reviews, Government IT, IT projects, IT-related failures, Major Projects Authority, openness and transparency, operational issues, private sector lessons for the public sector, project management, public sector

Tagged , , , ,

Is DWP stance on Universal Credit reports mocking FOI?

Posted on 27/04/2012 | 1 comment

By Tony Collins

The Department for Work and Pensions, which has remained as secretive over the progress or otherwise of its IT-based projects as before the 2005 Freedom of Information Act, has, as expected, rejected our FOI request for reports on the state of the Universal Credit project.

We have appealed and the DWP has, as is customary, delayed its response. It appears that the Department works on the principle that the longer it delays FOI responses the more out of date will be its reports when the Information Commissioner eventually rules they must be published.

In its reply to us, the DWP gave reasons for hiding a report it has already put in the public domain: a “Starting Gate Review” of Universal Credit.

Hiding reports under its jumper

The review was carried out in February 2011. That the DWP is keeping under its jumper a public report suggests that its responses to the FOI Act owe more to instinct than proper consideration.

The DWP also refused to publish, under the FOI Act, a Universal Credit “Project Assessment Review in November 2011” by the Cabinet Office’s Major Projects Authority.

These are the reasons Ethna Harnett, Universal Credit Division, DWP,  gave for refusing our FOI request for Universal Credit project progress reports:

– “Further reviews, by the Major Project Authority and by the National Audit Office are planned.”

– “Elements of the information you requested is being withheld as it falls under the exemption in Section 36 (2) (b) and (c) of the Freedom of Information Act. This exemption requires the public interest for and against disclosure to be balanced.”

– “The information you have requested includes details of a sensitive nature whose publication would prejudice effective conduct of public affairs. There is a strong public interest in the Department maintaining an efficient and effective risk management and assurance process and in ensuring that this process is not undermined by premature disclosure particularly where risks are not yet fully mitigated.”

– “There is also a strong public interest in the Department being able to carry out and use frank assessments, including unrestrained and candid contributions from business areas. ”

– “The assurance reports produced by the Major Project Authority are not shared beyond the Senior Responsible Owner and interested parties within Government.”

– “DWP Ministers have, however, committed to update Parliament on the Universal Credit programme through written ministerial statements. These statements are available on the Parliamentary website – www.parliament.uk.”

– “The Major Projects Authority will publish information on the progress of the Government’s high-risk and high-value projects, referred to collectively as the government major projects portfolio, alongside the first annual report at the end of this financial year.”

Comment:

The DWP has never met any of our FOI requests and has, in every case, delayed its responses to our requests for internal appeals. The result of the appeals is always the same – the upholding of the original decision. We are in awe of the DWP’s ability to detach its IT operations from the FOI Act.

The DWP considers it is acting in the public interest: that assessments of its IT-based projects such as Universal Credit would not be candid if they were put in the public domain.

But if the DWP had got this right and that its assurance reports would be less effective if published, we’d expect to see successes with major DWP IT-based projects. We don’t see the evidence.

Indeed the signs are that Universal Credit, the DWP’s biggest project, is in trouble; and after 20 years the Department is still having trouble combining its various benefit systems.

The National Audit Office has qualified the DWP’s accounts every year for the last 23 years, largely because of the level of official error and fraud.

Is this a department that is getting IT right?  There is no evidence it is; and some evidence suggests it isn’t.

The DWP needs to change. It needs to see openness as an opportunity not a threat. Openness would show that officials are prepared to be measured publicly against the findings of their assessment reports. That needs self-confidence.

On the other hand secrecy permits an uneasy introspection, allows weaknesses to take hold, and gives officials comfort in not changing.

Somerset Maugham put it well in his excellent book Of human Bondage. He said: “Like all weak men he laid an exaggerated stress on not changing one’s mind.”

Time for truth on Universal Credit

Millions of pounds of secret DWP reports

Universal Credit latest

FOI blog

Trying to kill the FOI Act?

1 Comment

Posted in Campaign4Change, change, culture, DWP, excessive secrecy, Freedom of Information, Government IT, HMRC, Major Projects Authority, openness and transparency, Universal Credit

Tagged , ,

A few suggested blog posts – on change at Kodak, the rise of Splunk and a culture clash in China

Posted on 22/01/2012 | Leave a comment

By David Bicknell

Browsing over the weekend, I came across a few posts about change management and cultural change that caught my eye and are worthy of passing on.

A couple are from the Harvard Business Review, and one is taken from IT-Director.com.

The Harvard Business Review items cover the innovation and transformational change issues involved in the continued demise of Kodak and the cultural issues that anyone who has plans to do business in China may have to get to grips with. The IT-Director article covers the growing reputation of Splunk, a real-time operational intelligence specialist that collects and indexes machine data and which has potential in the growing ‘Big Data’ marketplace.

Leave a comment

Posted in Big Data, Campaign4Change, change, change management, China, culture, IT projects, managing change

Tagged , , , , , , , ,