Tag Archives: agile

Some ways to change government practices

By Tony Collins

Mark Foden, a consultant to the public sector, says that transformation is much more likely to come about through collaboration and small incremental changes than strong-arm tactics such as mandation and regulation.

He also suggests that rather than pay high-cost contractors, government should pay more for talented specialists – and possibly pay them much more than their managers.

Foden has worked within government for many years and has seen some of what works and doesn’t. He advocates the use of internal social networks within and across departments.

He sets out his views in a critique of a report of the Public Accounts Committee on Information Communications and Technology in government.

Foden’s views are to some extent in line with the so-called “nudge” non-regulatory approach to behaviour change. Nudge was used originally by Richard Thaler and Cass Sunstein who define it as:

“… any aspect of the choice architecture that alters people’s behaviour in a predictable way without forbidding any options or significantly changing their economic incentives. To count as a mere nudge, the intervention must be easy and cheap to avoid. Nudges are not mandates. Putting the fruit at eye level counts as a nudge. Banning junk food does not”.

These are some of the points Foden makes:

Systemic change. It isn’t enough to change policy, process and structure and hope that deeper, more systemic, changes will naturally follow.

Targets. There is a deep-grained, almost unquestioned, culture of using targets to control performance. “Often, targets drive target-meeting behaviours rather than performance-improving ones…Measuring, on the other hand, is crucial; but it must be used in the spirit of learning and developing rather than explicitly for controlling…”

Language. Be careful how you use expressions such as “buy-in” and “deliver”.  Buy-in suggests something that is decided by one group of people then ‘sold’ to another. This is just not a great model for helping civil servants feel involved and empowered. “If people are going to play an important part in achieving something then they must be, and feel, involved from the beginning. Just using terms like this creates the wrong dynamic. Rather than cautioning about not achieving buy-in the Public Accounts Committee should be encouraging more-open, more-inclusive behaviours.” Deliver, says Foden, is too transactional. “I just can’t get the ‘deliver a parcel’ sense out of my head: something neatly packaged then sent to a recipient at a specific time. Managing change is just not about this.”

SMEs. “To get benefit from working with SMEs Government will need to bend, in perhaps significant ways; and people will need to behave differently. This is new territory: time should be taken to experiment and find out what approaches flourish. The useful approaches should be developed – incrementally – in much the same way the strategy proposes IT be developed. And this may take years.

Lean. “Change cannot be made by feeding new policy into an old machine. “Government will need to reshape (and that’s not ‘reorganise’) itself dramatically – perhaps using ideas like Lean – and, to do that, it will need to foster new behaviours; like being more open, being naturally collaborative and being more entrepeneurial. The Efficiency and Reform Group [of the Cabinet Office] should attend explicitly to nurturing such new behaviours.

Pay specialists more than their managers? “If government wants more talent, then it must be able pay the market rate for the people it needs and then provide them with hugely satisfying work in an affirming, supportive environment so that they stay around. This will be far cheaper and, in most cases, better than hiring long-term contractors. If this means paying specialists (sometimes considerably) more than their managers, so be it. There’s a real cultural hump to be got over here.”

More on Mark Foden’s views

Open Government? Up to a point Lord Copper

By Tony Collins

There is much we know about Universal Credit.

Ian Watmore, the permanent secretary at the Cabinet Office, has told MPs that the project is built on agile methods: it is split into two-to-three-week drops of code. The coding is divided into customer types  – and there are several thousand different types of customer. The simplest cases are those who have lost their job and the complicated ones are people who are in and out of work.

For each customer type the whole IT solution is being developed and is then tested with benefits claimants. Following agile principles, the problems encountered during testing are understood and the software re-coded.

The plan is to go live  with selected customer types by October 2013  – and it’s probably right that nobody in government will guarantee the deadline will be met.

This all sounds impressive but there’s one big drawback:  officials are refusing to release the “starting gate” review on the Universal Credit project.

Every major project now has to undergo a starting gate review to check it’s feasible before money is committed. It’s a good idea – and all credit to the team led by Cabinet Office minister Francis Maude for enforcing it.

But officials are doing their best to stop starting gate reviews being published, even under the FOI Act. Officialdom  has even ignored an MP’s request for the starting gate report on Universal Credit. That MP, Richard Bacon, a Conservative member of the Public Accounts Committee, will pursue the matter.

Why the secrecy? 

It is likely that the civil service doesn’t want to publish starting gate reports for the reasons they don’t want to publish Gateway reviews: they’d rather not be accountable for what they say. If the advice is wrong it can be known years later when those involved have moved on. But the civil service would prefer that assessments of projects are not published while the advice is contemporaneous.

Hence the Department of Health has published Gateway review reports that are several years old. More recent reviews are published in a form that’s so heavily redacted – edited – that they contain no useful information.

Without the publication Gateway reviews,  the media, MPs and the public have no independent information on the progress or otherwise of large IT-based projects and programmes, unless they are scrutinised by the National Audit Office which has only limited resources. Without the publication of starting gates there’s no independent information in the public domain on the feasibility of big public sector projects and programmes.

So much for open government.

Links:

What is a starting gate?

The DH documents that mock open government

Excerpts from report on GovIT: Recipe for rip-offs – time for a new approach

By Tony Collins

Today’s comprehensive report on the government’s use of IT is replete with strong and important messages, particularly on the domination of government IT by a small number of large suppliers, so-called systems integrators.

That said, Techmarketview, which tracks developments in the IT supplier market, has today attacked the report of the Public Administration Select Committee.  Techmarketview’s analyst Georgina O’Toole concedes she has not looked carefully at the full report but says she is irritated by the summary’s sensationalism.

It may be worth remembering that Parliamentary committees compete with each other for media attention. A bland report will be pointless: it won’t be read. Today’s report of the PASC, though, seeks more often than not to give the balacing view whenever it says something tendentious.  

For ease of explanation the Committee’s report “Recipe for rip-offs – time for a new approach” refers to government as if it were a single entity.

But government is, to some extent, at war with itself. The Cabinet Office is trying to have more influence over departments, in encouraging them to use SMEs,  adopt agile methods, simplify working practices and cut costs; and while the Cabinet Office has a mandate from David Cameron to enforce its wishes, in practice departments are giving strong reasons for not acting:

-long-term contracts are already in force

– EC procurement rules mean that SMEs cannot be preferred over other suppliers

– SMEs give insufficient financial assurances and could go bust at any time

– there are not enough internal staff and skills to manage a plethora of smaller companies

– existing (large) suppliers employ hundreds of SME as subcontractors.

There’s a particularly telling passage in the PASC report. It gave details of an exchange between the Department of Work and Pensions and Erudine, an SME. The Committee was given details of the exchange during a private session.

Erudine had given the department a way of migrating a legacy system onto a more modern, cheaper platform, which could generate potential savings of around £4m a year.

A senior DWP IT official rejected the proposal and suggested that the department was maintaining an interest in SMEs for political reasons – the government’s wish for 25% of contracts to be given to SMEs. This was part of what the DWP official said to Erudine:

“.. we have as you know an ‘interest’ in having SMEs present and working in the department for good political reasons. So you have other value to us … purely political.

“You guys need to be realistic. I will be very candid with you […] it is a huge amount of bother to deal with smaller organisations. Huge. And we wouldn’t necessarily do that because it doesn’t make our lives simpler.”

The Department declined to comment on the exchange and said the views expressed did not represent its own. It told the Committee that in 2009/10 SMEs made up 29.3% of their supplier base, either as a prime contractor or a subcontractor.

The Committee welcomed this assurance from the Department but added:

“… this account does suggest that attitudes at official level risk undermining ministers’ ambitions to increase the number of SMEs Government contracts with directly”.

These are other extracts from the PASC report:

Overcharging by large suppliers – an obscene waste of public money?

They [SMEs] also alleged that a lack of benchmarking data enabled large systems integrators (SIs) to charge between seven  to ten  times more than their standard commercial costs.

**

Having described the situation as an “oligopoly” it is clear the Government is not happy with the current arrangements. Whether or not this constitutes a cartel in legal terms, it has led to the perverse situation in which the governments have wasted an obscene amount of public money.

The Government should urgently commission an independent, external investigation to determine whether there is substance to these serious allegations of anti-competitive behaviour and collusion. The Government should also provide a trusted and independent escalation route to enable SMEs confidentially to raise allegations of malpractice.

Vested interests suppress innovation?

We received suggestions from some SMEs that the major systems integrators used legacy systems as leverage to maintain their dominance. Some SMEs reported that there were solutions that could easily transfer data from old platforms, but that a combination of risk aversion and vested interests prevented these solutions being adopted

Large IT contractors are “not performing well”

The Government’s analysis has shown that its large IT contractors are not performing well. A Cabinet Office review in September 2010 of the performance of the 14 largest IT suppliers found that none of them were performing to a “good” or “excellent” level, with average performance being a middling “satisfactory with some strengths”. Some were performing significantly worse.

Openness would help to cut costs

Making detailed information on IT expenditure publicly available for scrutiny would enhance the Government’s ability to generate savings, by allowing external challenge of its spending decisions.

The Government has already taken steps to provide more information about IT projects and expenditure in general, especially through the work of the Transparency Board and its publication of contracts on Contract Finder. To realise the full benefits of transparency, this is not sufficient. More information should be made public by default.

It should publish as much information as possible about how it runs its IT to enable effective benchmarking and to allow external experts to suggest different and more economical and effective ways of running its systems

Will government objectives be achieved?

We received numerous reports from SMEs about poor treatment by both Government departments and large companies who sub-contract government work to SMEs. There is a strong suspicion that the Government will be diverted from its stated policy and that its objective will not be achieved.

The drawbacks of using SMEs as subcontractors to large suppliers

“… subcontracting could lead to the Government paying a high price as it had to cover the margin of both the sub and prime contractor.

**

SMEs approached us informally to express concerns based on their own experiences of subcontracting. We heard of cases where systems integrators [large IT suppliers] had involved SMEs in the bidding process so they could demonstrate innovation, only for the SME to be dropped after award of contract.

In some of these cases SMEs felt that they have provided innovative ideas which had then been exploited by the larger systems integrators. We were also told by SMEs that by subcontracting with an SI they were barred from approaching government directly with ideas that might allow it to radically transform its services and reduce costs. This was because systems integrators did not want the Government to be provided with ideas that could result in them losing business, or having to reduce costs.

“… When we put these [SME] concerns to the Government we were told that their contracting arrangements did not stop subcontractors speaking directly to Departments…However, during our private seminar with SMEs, we were told that this did not reflect their experiences. SMEs reported that they were instructed to approach the systems integrator first in order to obtain permission to talk to a Department and that some Departments refused to deal with them directly.

**

We take seriously the concerns expressed by many SMEs that by speaking openly to the Government about innovative ideas they risk losing future business particularly if they are already in a sub-contracting relationship with a systems integator.

Government should deal directly with SMEs

The Government should reiterate its willingness to speak to SMEs directly, and commit to meeting SMEs in private where this is requested. We recommend that the Government establish a permanent mechanism that enables SMEs to bring innovative ideas directly to government in confidence, thereby minimising the risk of losing business with prime contractors.

Is government policy shutting out SMEs even more?

“…the Government has been moving to act as a single buyer to obtain economies of scale… This approach can be counter-productive. The effect of demand aggregation can be to aggregate supply, further concentrating contracts in the hands of a few large systems integrators.

Departments are following instructions from the Cabinet Office Efficiency and Reform Group to switch away from their existing direct SME contracting arrangements in favour of centralised procurement models. This would mean that SMEs would become tier 2 suppliers behind selected large suppliers, preventing SMEs from contracting directly with departments. The Cabinet Office has confirmed that:

Spend is being channelled into three current channels: a) existing framework contracts where spot buying is undertaken centrally (this is known as Home Office Cix), b) department-specific arrangements based on their unique needs (such as FCO’s arrangements with Hays) and c) an existing contract with Capita, owned and managed by DWP and available to all government departments.

It is unclear to us how narrowing the supply channels will create a more open and competitive market. The nature of this supply-side aggregation of SMEs under large contracts appears to be in direct contradiction of the policy articulated by the Minister when he indicated his desire to encourage Departments to secure more direct contracting with SMEs.

“… the Government’s plan to act as a single buyer appears to be leading to a consolidation towards a few large suppliers. This could act against its intention to reduce the size of contracts and increase the number of SMEs that it contracts with directly. We are particularly concerned with plans to move SME suppliers to an “arm’s length” relationship with Government. The Government needs to explain how it will reconcile its intentions to act as a single buyer, secure value for money and reduce contract size to create more opportunities for SMEs.

Procurement barriers for SMEs

The way procurement currently operates favours large companies that can afford to commit the staff and resources to navigate the convoluted processes. It also encourages the Government to confine discussions to as few potential contractors as possible.

If the Government is serious about increasing the amount of work it awards to SMEs it must simplify the existing processes

**

We recommend that the Government investigate the practices which seem unintentionally to disadvantage SMEs. When contracts and pre-qualifying questions are drawn up thought must be given to what impact they could have on the eligibility and ability of SMEs to apply for work, and whether separate provision should be made for SMEs. We believe it would be preferable if the default procurement and contractual approach were designed for SMEs, with more detailed and bespoke negotiation being required only for more complex and large scale procurements.

Have Departments the people and skills to handle more SMEs?

Increasing the use of SMEs will place extra pressure on departments. The management of smaller organisations is currently outsourced to the large systems integrators.

For example the Aspire framework provides HMRC with access to over 200 IT suppliers. Mr Pavitt, HMRC Chief Information Officer said that:

“managing those individually would be quite a heavy bandwidth for a Government department”.

It is not clear that Departments are willing to take on the additional work that contracting directly with SMEs implies even where this could yield significant savings…

Ministers need to ensure their officials have the skills, capacity and above all the willingness to deliver on ministerial commitments to SMEs.

On agile methods:

“… greater use of agile development is likely to necessitate behaviour changes within Government. As agile methodology requires increased participation from the business to provide feedback on different iterations of the solution, departments will need to release their staff, particularly senior staff with overall responsibility of the project, to allow them to participate in these exercises.

Agile development is a powerful tool to enhance the effectiveness and improve the outcomes of Government change programmes. We welcome the Government’s enthusiasm and willingness to experiment with this method. The Government should be careful not to dismiss the very real barriers in the existing system that could prevent the wider use of agile development.

We therefore invite the Government to outline in its response how it will adapt its existing programme model to enable agile development to work as envisaged and how new flagship programmes will utilise improved approaches to help ensure their successful delivery….

The Government will have to bear in mind the need to facilitate agile development as it renegotiates the EU procurement directive and revises the associated guidance.

Need for more people with the right skills to manage suppliers

Managing suppliers is as important as deciding who to contract with in the first place. To be able to perform both of these functions government needs the capacity to act as an intelligent customer. This involves having a small group within government with the skills to both procure and manage a contract in partnership with its suppliers.

Currently the Government seems unable to strike the right balance between allowing contractors enough freedom to operate and ensuring there are appropriate controls and monitoring in-house.

The Government needs to develop the skills necessary to fill this gap. This should involve recruiting more IT professionals with experience of the SME sector to help deliver the objective of greater SME involvement.

When disaster strikes is anyone responsible?

We are concerned that despite the catalogue of costly project failures rarely does anyone – suppliers, officials or ministers – seem to be held to account. It is therefore important that, when SROs do move on they should remain accountable for those decisions taken on their watch, and that Ministers should be held accountable when this does not happen.

Open source and open standards

Recent initiatives such as the Skunkworks team, dotgovlabs, data.gov.uk, and the Alphagov project suggest that the Government is moving in this direction

Government should omit references to proprietary products and formats in procurement notices, stipulating business requirements based on open standards. The Government should also ensure that new projects, programmes and contracts, and where possible existing projects and contracts, mandate open public data and open interfaces to access such data by default..

Report’s conclusion

“… The last 10 years have seen several failed attempts at reform. The current Government seems determined to succeed where others have failed and we are greatly encouraged by its progress to date.

“Numerous challenges remain and fundamentally transforming how Government uses IT will require departments to engage more directly with innovative firms, to integrate technology into policy-making and reform how they develop their systems.

“The fundamental requirement is that Government needs the right skills, knowledge and capacity in-house to deliver these changes. Without the ability to engage with IT suppliers as an intelligent customer – able to secure the most efficient deal and benchmark its costs – and to understand the role technology can play in the delivery of public services, Government is doomed to repeat the mistakes of the past.”

Links:

Jerry Fishenden, adviser to the PASC, gives his view of the report.

Today’s Public Administration Committee report: Recipe for rip-offs – time for a new approach

Government reliance on large IT suppliers is recipe for rip-offs.

Government IT rip-offs – surely time for a new approach – my view of the report

Techmarketview on the report

Good analysis of PASC report – Centre for Technology Policy Research.

Agile is brilliant says DWP’s head of major programmes

Steve Dover, head of major programmes at the Department for Work and Pensions, is qu0ted in Computer Weekly as saying of agile methods:

“It’s a brilliant, brilliant methodology … Get it right. Don’t pay it lip service.”

 Mark O’Neill, CIO at the Department for Communities and Local Government and leader of the government’s “skunkworks” team to promote innovation, is quoted as saying: “SIs [systems integrators – large IT companies] must recognise that the old world is dead and they have to change their model”.

But Malcom Whitehouse, DWP deputy CIO, implied there was some work only systems integrators could handle.

Agile can fix failed GovIT says lawyer.

Steve Dover on YouTube – the benefits of agile in GovIT [for the Institute for Government]

Cabinet Office turns to agile SMEs to reform Whitehall IT.

Agile: more about ‘business capability development’ and not simply ‘software development’

By David Bicknell

I like Mark Foden’s thoughts on Agile, posted on his posterous blog . He  makes the point that  Agile is not just about software development but a much broader development of entire business capabilities, including comms, training, people-change etc. But,  as he says, when you hear of Agile, you think of  ‘Agile Software Development’. I think he’s right.  He suggests explicitly referring to it as ‘Agile Business Capability Development (or somesuch). ‘

Agile Business Capability Development  might be a bit longwinded – but might  be  an easy and excellent acronym! I wonder if there are any shorter, more pithy alternatives……

Alpha.gov.uk shows how agile can work in government

By Tony Collins

Harry Metcalfe, managing director of Dextrous Web, has written an excellent article on Alpha.gov.uk.

Alpha.gov.uk is a prototype, built in response to some of the challenges laid down in a report by Martha Lane Fox last year. The two main objectives of Alphagov are to:

– test, in public, a prototype of a new, single UK Government website

– design and build a UK Government website using open, agile, multi-disciplinary product development techniques and technologies, shaped by a preoccupation with user needs.

It’s clear from Metcalfe’s post that he  understands the unbending ways of government. He sees the opportunities too. He says:

“As a technical solution, this [Alphagov] is brilliant. If you’re going to have a single [web] platform, this is the right kind of platform to have, because it embraces change.

“If you want some new functionality, add an app for it. If you need a new department, add a new instance of the department app, add your content, and you’ll have 90% of what you need.

“If you want to run a consultation using someone’s third-party tool, just have them brand it appropriately and write an app that gives you as much integration as you want, or as the tool can support. But this kind of flexibility is powerful. In many respects it’s anathema to the way government works.

“For a start, it requires something government unwisely gave up on long ago: an in-house development team…”

Campaign4Change comment:

Alphagov is not yet handling transactions. Indeed there are no agile-developed systems that handle passport applications or tax self-assessment.

As Metcalfe says: “…transactions are complicated, messy beasts, unavoidably bound up with business processes and legislation; empires, politics and entrenched positions; long contracts and vast sums of money.. it’s not primarily a technological problem. It’s a process problem, and those are much harder to fix.”

It may be a matter of time, though, before agile becomes far more prevalent in public sector IT. Universal Credit is based on agile, in a programme run in part by the redoubtable Joe Harley, the UK Government’s CIO.

Harley told the Public Accounts Committee last month:

“In the waterfall it takes quite a while to do a design – maybe a year or two … By the time we come to execute, things have moved on.

“In the agile world, it is a way of providing rapid solutions very quickly. Normally, and in Universal Credit it is monthly, one designs, develops, implements and produces a product very early on in the cycle. It is particularly useful and appropriate when the users themselves – in the universal credit, citizens themselves – can participate in the creation of it. It is about user-centric, rapid deployment solutions. That is what we hope to achieve.”

Ian Watmore, Chief Operating Officer at the Cabinet Office, told the same committee that the government objective is for the first claims under Universal Credit to be paid by October 2013. He said: “I would have thought that if we achieve that, it will become the precedent and benchmark for Government projects.”

We hope Universal Credit is a timely success and that it becomes a benchmark for government projects. It’s easy to talk down the chances of agile in government on the basis that it ill suits the way government works. But Francis Maude, officials in the Cabinet Office, and Alphagov’s developers want to change the way government works.

To say that agile won’t work in government is like telling someone who’s obese that they need not eat less because history shows they won’t be able to.

Government must spend less. And agile is one way to cut spending. Alphagov is showing the way.

How Alpha.gov.uk came about:

Last year Martha Lane Fox published suggestions on reforming UK Government’s online. At the launch of her report (subtitled “revolution, not evolution”) she recommended:

“…Putting the needs of citizens ahead of those of departments”

She made a strong case for the UK Government to adopt a single web domain, analogous to the BBC’s use of BBC.co.uk, and recommended a radical change in how gov.uk sites are produced:

“Government should take advantage of the more open, agile and cheaper digital technologies to deliver simpler and more effective digital services to users.”

Links:

How Alphagov might change UK government for the better.

Institute for Government: what’s wrong with government IT?

Agile in government IT – don’t knock it.

10 things Alphagov gets right.

10 things Alphagov gets wrong.

Alpha.gov.uk

Agile in Government IT – don’t knock it

By Tony Collins

Alistair Maughan, a lawyer who specialises in large ICT projects, argues that agile won’t work in government ICT.

“The Government ICT strategy had some good ideas. Agile project management isn’t one of them,” says Maughan in a cogent and informed blog post for Computer Weekly.

I asked the Institute for Government to respond to Maughan’s comments. The Institute advocates agile in its report System Error: Fixing the flaws in government IT.

My thanks to Jerrett Myers, a senior researcher at the Institute, who has written the piece below, in response to Maughan’s comments.

Agile government ICT – a question of innovation

Like any management innovation, there are plenty of challenges in adopting an agile approach, but fortunately none are insurmountable.  The innovation guru Everett Rogers outlines a series of factors that influence the rate of adoption of an innovation – in effect setting out a test for how likely it is for an innovation to be implemented.

The first is test is the relative advantage of the innovation – the degree to which a new way of working is perceived as superior. Government departments and agencies have reported extremely positive results from agile projects. Indeed, the Department for Work and Pensions, the Ordnance Survey and the Ministry of Defence have all used agile methods for delivering ICT projects.

Regularly changing priorities, advances in technology and the desire for more cost-effective and user-led solutions require a far more responsive approach to running ICT projects.  Of the thousands of people who have downloaded our recent report, we have had an overwhelmingly positive response to the idea for government.

So how can government make it work? The second innovation success factor is ‘trialability’ – can departments test out this approach on a limited basis.  Again, the good news is that at relatively low cost, departments can use an agile approach for running ICT projects – and indeed they are committed to doing so.

The third characteristic is ‘observability’ – are the results of the innovation visible to others.  Whitehall has committed to creating a centre of excellence across government and the private sector which can enable fast start-up and mobilisation for agile projects.  It will also establish a cross government approach and capabilities for agile.  This should serve to raise the profile and ‘observability’ of agile projects.

The fourth factor is complexity – how difficult is an innovation to use and understand.  Here, the government faces a greater challenge.  New skills will be required which are ‘in-house’ rather than bought in through contractors.  This includes making difficult trade-offs and prioritising effectively. Regular testing, planning and demonstration will need to take place to handle risks. And by taking part in agile projects, it can serve to internalise agile values, build skills and help to foster support, understanding and momentum for change.

The final factor is perhaps the greatest barrier to overcome – compatibility – the degree to which an innovation is consistent with existing values, norms and operating procedures.  Maughan underscores how different the agile approach is for running ICT projects. The project approval processes and legal arrangements governing contracts need to be adapted to be far more responsive and receptive to agile delivery.

Equally important is the culture of empowerment that needs to surround projects.  Fortunately, the experience in other large organisations in the public and private sector suggest this transition is possible.

At a large government agency, budgeting and governance processes have changed to accommodate and encourage more agile projects.  Its new investment approval process involves obtaining early permission to fund development immediately without a fully specified business case being approved (although a robust justification must still be provided). The projects are given permission to spend at a particular rate over a period of time and return to the investment board at specified intervals for further approvals and to update on progress.

On each of these points, it appears that agile can succeed with the right leadership and determination for change. Ultimately, however, this isn’t just about adopting a new approach to government ICT, reforming the procurement process or taking a more sophisticated approach to managing risk.  Instead, it is a test of Whitehall’s capacity for innovation.

**

Jerrett Myers is a Senior Researcher at the Institute for Government. The Institute for Government’s report, System Error: Fixing the flaws in government IT can be downloaded here.

Alistair Maughan’s blog post for Computer Weekly is here.

12 “agile” principles

By Tony Collins

The  principles (below), which are largely managerial,  highlight the challenges for government departments and suppliers of adopting agile principles for major IT-related projects such as Universal Credit.

Some in government have said that agile can deliver systems to support political policy quickly, say within two years –  but that’s far too long. Under agile principles, working systems should be delivered between two weeks and two months.

 I particularly like the tenth principle, which defines simplicity as the art of maximizing the amount of work not done; in other words not gold-plating requirements.

The second principle is also especially important for government IT-enabled projects and programmes: it states that changing requirements are welcome, even late in development.

The principles are from the excellent website of project manager Robert Kelly.

12 Principles behind Agile
 
  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals.  Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development.  The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity –the art of maximizing the amount of work not done– is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Kelly’s contemplation – Robert Kelly’s blog

The Institute foir Government recently produced some case studies from its System Error report.

Francis Maude tells civil servants: try new things and learn from failure

By Tony Collins

Francis Maude, the Cabinet Office minister who’s in charge of reforming central government, has told MPs that “good organisations learn as much from the things that are tried and do not work as from the things that are tried and do work”.

His comments will give top-level support to those in the public sector who are seeking small budgets to experiment with, say, agile approaches to software development.  The agile principle of failing cheaply and quickly and learning the lessons is unconventional in the public sector.

Appearing before the Public Administration Committee, in its hearing on Good Governance and Civil Service Reform, Maude said:

“You need to have a culture-we do not have this yet-where people are encouraged to try new things in a sensible, controlled way; front up if they have not worked – not have a culture that assumes every failure is culpable, and for every failure there has to be a scapegoat – but actually make sure that if something is tried and does not work: 1) you stop doing it; and 2) you learn from the things that have been tried and what the lessons are.

“I do not think we are good at that … part of the reason for that is the sort of audit culture, where everything has to be accounted for to the nth degree.

“I think we waste a huge amount of time and effort in stopping bad things happening and the result is we stop huge amounts of potentially good things happening as well.”

Maude was critical of the way government takes huge risks on big projects but is hostile to innovation at the micro level. He said: 

“Government tends to be quite prone to take huge macro risks, but then at working level, at micro level, to be very risk averse and hostile to innovation.

“You do not often hear of someone’s career suffering because they preside over an inefficient status quo, but try something new that does not work and that can blot your copybook big time.”