Category Archives: cost reduction

More agile-thinkers like Roo Reynolds please

By Tony Collins

There’s a useful “keep-it-simple” article on agile software development principles by Roo Reynolds who a product manager at the Government Digital Service.

Reynolds quotes Marissa Mayer, former Google product manager, now Yahoo CEO, who said that there are two types of developer: those who seek perfection and those who seek something working today that they can improve on tomorrow.

“You probably want to work with the second sort of developer as much as possible,” says Reynolds. He quotes Voltaire as saying ‘the best is the enemy of the good’.  From Reynolds’ article:

“We start with a Minimum Viable Product, asking ourselves, what’s the simplest thing that could possibly work? We aim to have a working product, albeit a limited one, within a week or two.

“Having something you can point at and get feedback on as soon as possible is definitely better than attempting to polish something to perfection without anyone being able to tell you whether what you’re making is actually what they need.”

He warns against using made-up data, such as Lorem Ipsum text, because:

– it causes existing assumptions to be reinforced rather than challenged

– it lazily misses an opportunity to iron out any difficulties in getting hold of the real data

He concludes that “nothing beats feedback from real users”.

“Testing products with real users is vital. We always start with user needs (generally captured as user stories) and in meeting those needs I’ve learned not to get too comfortable with any implementation until we’ve tried it with a range of real people. Best of all, it’s ok to be wrong. The best way of getting closer to being right is to test real ideas with real people.”

Comment

If these principles had been applied to the NPfIT it might never have been started.  The NPfIT launched with the principle: what’s the most complicated thing that could possibly work?

Too often assumptions were made on the basis of unrepresentative data such as patient records that were up-to-date, accurate and not duplicated. The NPfIT was tested on real users – but then the bad news was all but ignored.

If Reynolds had been advising on the NPfIT, and Tony Blair hadn’t been so gung-ho when he chaired a discussion on NHS IT at a meeting in Downing Street on 18 February 2002, perhaps billions would not have been wasted on the programme.

More like Roo Reynolds in government please.

@rooreynolds

Reynolds’ article, Government Digital Service.

Poor IT suppliers to face ban from contracts?

By Tony Collins

The Cabinet Office minister Francis Maude is due to meet representatives of suppliers today, including  Accenture BT,Capgemini, Capita, HP, IBM, Interserve, Logica, Serco, and Steria.

They will be warned that suppliers with poor performance may find it more difficult to secure new work with the Government. The Cabinet Office says that formal information on a supplier’s performance will be available and will be taken into consideration at the start of and during the procurement process (pre-contract).

Maude will tell them that the Government is strengthening its supplier management by monitoring suppliers’ performance for the Crown as a whole.

“I want Whitehall procurement to become as sharp as the best businesses”, says Maude. “Today I will tell companies that we won’t tolerate poor performance and that to work with us you will have to offer the best value for money.”

The suppliers at today’s meeting represent around £15bn worth of central government contract spend.

The representatives will also be:

– asked their reactions on the government’s approach to business over the past two years

– briefed on the expanded Cabinet Office team of negotiators (Crown Representatives) from the private and public sectors. Maude says these negotiators aim to maximise the Government’s bulk buying power to obtain strategic discounts for taxpayers and end the days of lengthy and inflexible contracts.

Spending controls made permanent

Maude is announcing today that cross-Whitehall spending controls will be a permanent way of life. The Government introduced in 2010 temporary controls on spending in areas such as ICT  and consultancy. It claims £3.75bn of cash savings in 2010/11, and efficiency savings for 2011/12, which it says are being audited.

The Cabinet Office says: “By creating an overall picture of where the money is going, the controls allow government to act strategically in a way it never could before. For example, strict controls on ICT expenditure do not just reduce costs but also reveal the software, hardware and services that departments are buying and whether there is a competitive mix of suppliers and software standards across government.”

Maude said: “Our cross-Whitehall controls on spending have made billions of cash savings for the taxpayer – something that has never been done before. That’s why I’m pleased to confirm that our controls will be a permanent feature, helping to change fundamentally the way government operates.”

Why is MoD spending more on IT when its data is poor?

By Tony Collins

The Ministry of Defence and the three services have spent many hundreds of millions of pounds on logistics IT systems over the past 20 years, and new IT projects are planned.

But the National Audit Office, in a report published today – Managing the defence investory –  found that logistics data is so unreliable and limited that it has hampered its investigations into stock levels.

“During the course of our study,” says the NAO, “the Department provided data for our analyses from a number of its inventory systems. However, problems in obtaining reliable information have limited the scope of our analysis…”

The NAO does not ask the question of why the MoD is spending money on more IT while data is unreliable and there are gaps in the information collected.

But the NAO does question whether new IT will solve the MoD’s information problems.

“The Department has acknowledged the information and information systems gaps and committed significant funds to system improvements. However these will not address the risk of failure across all of the inventory systems nor resolve the information shortfall.”

MPs on the Public Accounts Committee, who will question defence staff on the NAO report, may wish to ask why the MoD’s is so apparently anxious to hand money to IT suppliers when data is poor and new technology will not plug information gaps.

Comment:

MPs on the Public Accounts Committee found in 2003 (Progress in reducing stocks) that the MoD was buying and storing stock it did not need. Indeed after two major fires at the MoD’s warehouses at Donnington in 1983 and 1988 more than half of the destroyed stock did not need replacing. Not much has changed judging by the NAO’s latest report.

It’s clear that the MoD lacks good management information. Says the NAO in today’s report:

“The summary management and financial information on inventory that is provided to senior staff within Defence Equipment and Support is not sufficient for them to challenge and hold to account the project teams…”

But will throwing money at IT suppliers make much difference? The MoD plans the:

–  Future Logistics Information Services project, which is intended to bring together and replace a number of legacy inventory management systems; and

–  Management of the Joint Deployed Inventory system which will provide the armed services with a common system for the inventory they hold and manage.

But is the  MoD using IT spending as proof of its conviction to improve the quality of data and the management of its inventory?

Managing the defence inventory

How CIOs and IT suppliers view GovIT change

By Tony Collins

CIOs and IT suppliers give their views on Government ICT in an authoritative report published today by the Institute for Government

Inside the wrapper of generally positive words, a report published today on government ICT by the Institute for Government suggests that major change is unlikely to happen, despite the best efforts of  CIOs and the Cabinet Office minister Francis Maude.

The report “System upgrade? The first year of the Government’s ICT strategy”  says progress has been made. But its messages suggest that reforms are unlikely to  amount to more than tweaks.

These are some of the key messages in the report:

If the minister and CIOs cannot direct change who can?

–          “… while the Minister for the Cabinet Office and government CIO are viewed as being responsible for delivering the ICT strategy (for example by the Public Accounts Committee) they currently lack the full authority to direct change.”

Not so agile

–           “While just over half of government departments may be running an agile project, there were concerns that these were often very minor projects running on the fringe of the departments.”

–          “We heard concerns from the supplier community and those inside government that in some areas projects may be being labelled as ‘agile’ without having really changed the way in which they were run.”

–          “CIOs should question whether they are genuinely improving the ways that they are working in areas such as agile, or whether they are just attaching a label to projects to get a tick in the box,” says the Institute for Government.

Savings not real?

–          “There was also an element of challenge to the savings figures provided by government. For example, some from government and the supplier community questioned whether the numbers represented genuine savings or just cuts in the services provided or deferred expenditure. “

–          “Others … cautioned that project scope creep or change requests could reduce actual savings in time. It was pointed out that the NAO [National Audit Office] will scrutinise whether savings have been achieved in future, which was seen as a clear incentive for accuracy – but there were, nonetheless, concerns that pressure to provide large savings figures meant that inadequate attention might be paid to verifying the savings …”

CIOs want faster ICT progress

–          “Among the CIOs we interviewed, there was a clear recognition that government ICT needed to improve.  ‘You expect an Amazon experience from a government department…’ ”

Lack of money good for change

–          “As one ICT lead noted, a lack of money was ‘always helpful’ in driving change as it promoted cross-government solution-sharing and led to more rigour in approving new spend.”

–          “Both ICT leaders and suppliers felt that the ICT moratorium had been a helpful stimulus for increased focus on value for money.”

–          “Though some of the larger suppliers felt bruised by the ‘smash and grab’ of initial interactions with the Coalition government, there was a recognition that the moratorium had been about ‘stopping things which were inappropriate’”.

GDS challenges norms

–          “New ways of working in the new Government Digital Service and the opening up of government through the Transparency agenda were also seen as providing a challenge to existing norms.”

–          The new Government Digital Service (GDS) is providing an example of a new way of doing things, and was pointed to by those inside and outside of government as embodying mould-breaking attitudes, using innovative techniques and … delivering results on very short timescales. Several interviews mentioned being invigorated by the positive approach of the GDS and their focus on delivering services to meet end-user needs.

ICT so poor staff circumvent it

–          “Public servants are increasingly frustrated that the ICT they use in their private lives appears to be far more advanced than the tools available to them at work. Indeed, there are already examples of employees circumventing the ICT that government provides them as they attempt to perform their job more effectively: creating what is known as a system of ‘shadow ICT’ that creates significant challenges for maintaining government security, collaborative working and government knowledge management.”

Joined-up Govt impossible?

–          “The possibility that departmental incentives continue to trump corporate contributions is further suggested by our survey results. Individuals do not yet feel that corporate contributions are valued or rewarded … elements of the [ICT] strategy call for departments to give up an element of autonomy and choice for the ‘greater good’. Several CIOs expressed concerns that by adopting elements of the strategy that were being developed or delivered by another department, they would end up having to accept a service that had been designed  around the needs of a different department.”

–          “Similarly, there were concerns that the host department would be at the top priority in the event of any problems or opportunities to develop services further. This speaks to a strongly department-centric culture. Suppliers noted, for example, that certain parts of government were still happy to ‘pay a premium for their autonomy’.”

–          “… the vast majority of those we spoke to suggested that departmental interests would almost always ultimately trump cross-government interests in the current government culture and context.”

–          “CIOs felt that they would be rewarded for delivery of departmental priorities – not pan-government work …”

CIO Council frustrations

“CIOs noted that there could be a discrepancy between what got agreed at the old CIO Council meetings and what people actually went away and did. Larger department CIOs also expressed frustration that – despite holding the largest budgets and carrying the largest delivery risks – their voices could easily be outweighed by the multitude of other people round the table.”

“The delivery board model [which has superseded CIO Council] has been recognised by both big and small departments as pragmatically dealing with both sides of this issue. Larger departments now form part of an inner-leadership circle, but with this recognition of their clout comes additional responsibility to own and drive through parts of the strategy… the challenge will now be to ensure that the ICT strategy doesn’t become a ‘large department-only’ affair and that other ICT leads can be effectively engaged.”

Canny suppliers?

–          The majority of ICT leads …stated that they believed the ICT strategy would benefit their department and government as a whole. This confidence was less apparent in the attitudes of suppliers who were, on the whole, more sceptical of government’s ability to drive change, though again generally supportive of the direction of travel.

A toothless ICT Strategy is of little value?

–          “…There was also a lack of clarity on how different elements of the [ICT] strategy would be enforced. As one ICT leader commented … ‘Is this a mandatable strategy or a reference document?’ ”

–          … “there are risks that the strategy could be delivered in a way that still doesn’t transform ICT performance.”

Francis Maude an asset

–          “Government ICT has also been a priority of the Minister for the Cabinet Office, Francis Maude – giving the [change] agenda unprecedented ministerial impetus. He has been a visible face of ICT to many inside and outside of government, from demanding departmental data on ICT to being heavily involved in negotiations with ICT suppliers. Though few of his ministerial colleagues appear as passionate about improving government ICT, the CIOs we interviewed overwhelmingly expressed confidence that they would receive the support they needed to implement the changes in ICT.”

Smaller-budget CIOs out of the loop?

–          “With the CIO Council in hiatus for most of the last year, the CIOs of smaller departments felt out of the loop …”

Most ICT spending is outside SW1

–          “Suppliers and other ICT leaders pointed out, rightly, that the vast majority of ICT expenditure happens outside SW1 – with agencies, local government and organisations like primary care trusts and police forces still determining much of the citizen and workforce experience of ICT.”

SMEs still left out?

–          “Smaller suppliers … were generally encouraged that government was trying to use more contractual vehicles which would be open to them – but noted that it was ‘still extremely difficult to get close to government as an SME’.”

Who knows if use of ICT is improving?

–          “Government still lacks the information it needs to judge whether use of ICT across government is improving.”

System upgrade? The first year of the Government’s ICT Strategy.

Too early to claim success on GovIT – Institute for Government

Civil service reform plan – real change or a tweak?

By Tony Collins

The civil service reform plan is to be published this afternoon, at 3.30pm.  The Cabinet Office minister  Francis Maude and Sir Bob Kerslake, the head of the civil service, write about it in today’s Daily Telegraph.

They say that the plan will help deliver a civil service culture that is “pacier, more innovative, less hierarchical and focused on outcomes not process”. They write:

“We also need sharper accountability, in particular from permanent secretaries and those leading major projects, and we need more digital services, better data and management information and for policy and implementation to be linked seamlessly together…”

In the same edition of the Telegraph Andrew Haldenby,  director of the independent think tank Reform, criticises the reform plan which, although not yet published, has been foretold in newspapers including the Financial Times yesterday.

He said the reform plan will “leave the flawed structures of Whitehall in place and do no more than propose some minor variations on a theme”.

We await publication of the paper before we judge it. We hope it will, at least, require the publication of “Gateway” review reports on the progress or otherwise of major IT-enabled projects.

Without timely publication of the Major Projects Authority’s Gateway reports, MPs and the public will continue to learn of failed schemes such as the NPfIT and Firecontrol when it is too late to do much about any rescue; and without contemporaneous publication there will continue to be no accountability for the rigour or otherwise of the reviews, or their outcome.

Civil service reform – meltdown or business as usual? – Institute for Government

Cabinet Office promises unprecedented openness on big, risky projects.

Civil service shake-up – Guardian

Cabinet Office promises unprecedented openness on risky projects

By Tony Collins

The Cabinet Office has defended its decision not to publish “Gateway” review reports on the progress or otherwise of large and risky IT and construction projects.

Gateway reviews are regular, short and independent audits on the state of medium and high-risk projects. Their publication would allow  MPs and the public to have an early warning of a major project in trouble – rather than know of a project failure only after it has happened.

Campaigners have sought for a decade to have the review reports published; and the  Information Commissioner, in requiring the publishing of ID Card gateway reviews under FOI,  dismissed the generalised arguments put forward by officials for Gateway reviews to remain confidential.

The Conservatives, when in opposition, promised to publish Gateway review reports if they came to power. But departmental heads and senior officials have stopped this happening.

Now the Cabinet Office, in a statement to The Guardian, has suggested that the first annual report of the Major Projects Authority will more than compensate for the non-publication of Gateway review reports.

The statement says that the Authority’s ( delayed)  first annual report will “bring unprecedented scrutiny and transparency to our most expensive and highest risk programmes, changing forever the culture of secrecy that has allowed failure to be swept under the carpet”.

The statement continues:

“Historically, fewer than a third of government major projects have delivered to original estimates of time, cost and quality. Since April 2011 the Major Projects Authority has enforced a tough new assurance regime and begun raising leadership standards within the Civil Service.”

The Guardian asked the Cabinet Office whether the traffic light red/amber/green status of Gateway reviews will be published.  The spokesman replied:

“The annual report will contain details of the status of major projects.“

Comment:

We applaud the Major Projects Authority in scrutinising, and in rare cases helping to stop,  departmental projects that don’t have adequate business cases. The Authority’s work is vital in pre-empting ridiculous schemes such as the NPfIT.

But project  disasters that rely on  IT continue, at the Ministry of Justice for example.  Like the National Audit Office, the  Major Projects Authority has limited resources and cannot scrutinise everything. Even if it could, the system of government is not set up in such a way as to allow the Authority to have final say over whether a project is stopped, curbed or re-negotiated.

Preventing failure

Gateway review reports are a critical component in preventing IT-related project failures. If officials know the whistle is going to be authoritatively blown on their failing schemes they are likely to do all they can to avoid failure in the first place. If they know that nobody will be aware of doomed schemes until those involved have left or moved, they will have less incentive to make projects a success.

An annual report is no substitute for the contemporaneous publishing of Gateway review reports. Each Gateway review is several pages and puts into context the traffic light red/amber/green status of the project. An annual report will not contain every Gateway review report. If just the traffic light status is published that will be a start, but without the context of the report what will it mean?

[And it’s worth bearing in mind that the first annual report of the Major Projects Authority is already six months late.]

The non-publication of Gateway review reports is  a victory by senior officials over ministerial promises.  How can we believe that the coalition is committed to unprecedented openness when the final say remains with Sir Humphrey?

Cabinet Office promises to challenge culture of secrecy on IT projects.

Whitehall to relent on secrecy over mega projects?

Francis Maude talks open govt – and Whitehall does the opposite

By Tony Collins

“If people do not know what you’re doing, they don’t know what you’re doing wrong.” – Sir Arnold Robinson, Cabinet Secretary in a discussion on open government in Yes Minister.

Francis Maude, the Cabinet Office minister, said all the right things at the Intellect World Class Public Services conference 2012.

He said that:

– smaller, innovative and efficient suppliers were finding themselves locked out of the supply of services to Government because of what was described by Parliament as a powerful “oligopoly” of large suppliers

– for the first time in Government “we are using agile, iterative processes, open source technology platforms and world-class in-house development teams alongside the best digital innovation the market can offer”

– “We must eliminate failure waste. At the moment, a large proportion of our service delivery costs are incurred through incomplete or failed digital transactions. And these transactions create cross-channel duplication, which burdens the user and costs Government a huge amount in repeated costs. For HMRC alone, they estimate that 35% of calls to its contact centres are avoidable, which would save £75m.”

– “Transparency is a defining passion for this Government …”

Comment:

How much influence does Maude really have? Can he persuade permanent secretaries to effect major change? The evidence so far is that departmental officials and Maude have different ideas on what reform means.

In “Yes Minister” civil servants were proud of a new hospital that was the best run and most hygienic in the country, with no medical staff, 500 administrators and no patients.

Maude may also recall that Antony Jay and Jonathan Lynn, the acclaimed writers of Yes Minister, spoke of the Whitehall law of inverse relevance – “the less you intend to do about something, the more you have to keep talking about it”.

Open government? 

Perhaps civil servants are letting Maude get on with talking the talk while they find every way to keep things much as they are. A good example: The Guardian reported yesterday that a key part of the Government’s transparency drive has stalled amid reports of ministry opposition.

The paper’s political editor Patrick Wintour reported that plans to publish regular ‘traffic-light’ progress reports on large, costly and risky IT projects “appear to have been shelved”.

When it comes to IT this could have been the coalition’s most important single reform. It would have given MPs and the public a way of knowing when mega projects such as Universal Credit are failing. Usually we don’t know about a failed IT-related project unless there is a leak to the media, or the National Audit Office finds out and decides, with its limited budget, to do a study.

Sir Bob Kerslake, who is head of the civil service,  had indicated to MP Richard Bacon that “Gateway” review reports on large and risky IT and construction projects may be published in the civil service reform plan which is expected to be released this month.

Gateway reports to go unpublished?

Now it seems that departmental civil servants  have persuaded the Sir Bob not to publish “Gateway” reports. So the secrecy over the progress or otherwise of government mega projects is set to continue.

Yes, civil servants will allow the Cabinet Office to have its way on the publication of data about, say, some government spending. But it’s becoming clear that the civil service will not allow any publication of its reports on the progress or otherwise of major projects. It has been that way since Gateway reviews were introduced in 2001.

Some senior officials – by no means all – say they want a confidential “safe space” to discuss the progress of projects. The reality is that they do not want outsiders – MPs, the media and NAO auditors – meddling in their failing schemes – schemes such as Firecontrol and e-filing at the Ministry of Justice.

Unlike Maude, senior civil servants have what Jay and Lynn call a “flexible approach to open government”. This means in practice that Whitehall will happily release data – but not project reports on which the civil servants themselves can be judged.

Activity is not achievement

Maude’s speeches will give the impression of activity. But activity is the civil service’s substitute for achievement. I quote Jay and Lynn again, in part because their depiction of Whitehall seems to have been taken as serious wisdom by those officials who think Sir Humphrey a character worth living up to.

It’s time Maude and his team got a grip on departments. Until they do, permanent secretaries and their senior officials will regard Maude as trying to get out of situations that don’t need getting out of.

Whitehall to relent on secrecy over mega projects?

The empty hospital – Yes Minister

Government’s transparency drive stalls.

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

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.

Watmore’s successor – the biggest challenge?

By Tony Collins

Ian Watmore, Permanent Secretary at the Cabinet Office, leaves at the end of June. What will be the biggest challenge for his successor?  I am told it will be to join up all the efficiency and reform measures:  ICT, digital, procurement, supplier management, project management, new business models, property and rationalisation  so that they are coherent from the point of view of departments, and don’t just look like a random set of instructions from the centre.

Farewell to Ian Watmore – the antithesis of Sir Humphrey

Whitehall defies NAO and Cameron on publishing status of big projects

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