Software Development: How the Traditional Contract Model Increases the Risk of Failure
In 2007 the UK Department for Communities and Local Government (the DCLG) entered into a contract with European Air and Defence Systems (EADS, now known as Cassidian) to deliver an IT system that would underpin the FiReControl project. The FiReControl project aimed to improve the UK Fire and Rescue Service by replacing 46 local control rooms with a network of nine purpose-built regional control centres. The project was expected to be completed in October 2009, and the DCLG's original estimate of the project costs was £120 million. By 2009, two years into the project, the expected duration of the project had doubled, and the anticipated total project costs had increased by more than 500% to £635 million. In 2010 the contract was terminated. The DCLG had wasted at least £469 million as a result of the failure of the project to deliver.1
This is a sobering story of a large IT project spiralling out of control. But it is not an isolated incident. Many projects are late or fail to deliver and one in six IT projects has a cost overrun of 200% on average and a schedule overrun of almost 70%.3 It seems that no organisation is immune from these risks. There was a common belief that out of control IT projects were the preserve of the public sector, but recent studies show that the private sector does not fare any better in comparison. Organisations in the private sector are simply less publicly accountable and so have greater ability to conceal IT disasters.
So why are IT projects so high risk, and how can this risk of failure be mitigated?
There is a huge disconnect in the world of software development. The lawyers aim to specify the relationship between the contracting parties with as much certainty as possible. But both the business function and the software development practitioners are operating in an increasingly complex, dynamic and inter-connected environment.
The legal and management functions have, by and large, not adapted their practices or values to take account of the challenges faced by the business functions and software development practitioners. Indeed, the contract model for software development (the "Contract Model") and the management practices that surround it have barely changed in the last thirty years. Much of the thinking underlying the Contract Model can be traced back to principles that were developed during the Industrial Revolution by the likes of Henry Ford and Frederick Taylor.
Our view is that the Contract Model compounds the effects of poor management, and that poor management is often based on the flawed thinking underlying the Contract Model. We have found that even if an IT project is resourced internally, the organisation tends to apply quasi-contractual relationships between its internal departments for the purchase of IT services. And we find the principles of the Contract Model in evidence here too.
We do not believe that we will see any significant improvement in the success of IT projects until we change the basis of the Contract Model and the surrounding management practices. For the purposes of this article we use the term "IT project" as shorthand for any IT change initiative involving the development of software.
The fundamentals of the Contract Model
We believe that any contract for software development based on the Contract Model contains three distinguishing features, all of which are seriously flawed. We use the terms "supplier" and "customer" to explain the dynamics in an external relationship. However, as mentioned above, in many cases similar principles appear to apply even if the IT project is resourced internally.
The three distinguishing features to any contract for software development based on the Contract Model are as follows:
- Output-Based Requirements. The supplier is required to deliver output that possesses all of the requirements, as specified by the customer in the contract. We use the term "output" to refer to product (e.g. code, features, functions, attributes), documentation and/or services.
- Change Control Mechanism. The Contract Model mandates that any change to any Output-Based Requirement or to any other element of the contract is regulated by the Change Control Mechanism. Broadly speaking, to initiate change the customer must submit a change request form to the supplier outlining the desired change. The supplier analyses the impact of the change request on the contract as a whole, including, in particular, the Output-Based Requirements, the price and the due date for completion of the IT project. On the basis of this, the supplier proposes an amendment to the contract. Following the agreement of the parties to the proposed contract amendment, a formal amendment is made to the contract to incorporate the requested change.
- Sequential Development. The software is to be developed sequentially, that is, using the waterfall model. Development is seen as flowing steadily downwards - like a waterfall - through the phases of conception, initiation, analysis, design, construction and testing. The supplier is required to complete each phase before starting the next phase, and the output of each phase provides the input for the next phase.
It is worth noting that we do not make any reference to the type of charging model in the Contract Model. If the three distinguishing features of the Contract Model feature in a contract, the contract will be flawed regardless of which charging mechanism is adopted.4 It makes little difference whether the price is fixed, target or based on time and materials, or whether there are bonuses or penalties.
On the face of it, and to anyone not directly involved in the implementation of the IT project, the Contract Model may appear to be eminently sensible. It creates a sense of certainty and predictability regarding the IT project, and it provides a clear and understandable structure for the various activities involved in the IT project. Plus it mirrors current procurement models.
However, the combination of these three elements in a contractual relationship between a customer and a supplier appears to cause the failure of many IT projects that would probably otherwise succeed. In fact, we would suggest that those IT projects which do achieve success, do so in spite of the Contract Model and the surrounding management practices, and not because of them.
In this article we explore some of the ways in which the Contract Model increases the risk of failure in any IT project.
An increased risk of failure
Any IT project is subject to risk which can be categorised into three main types:
- Delivery risk. This is the risk that the IT project is not delivered on time, on budget and to the required quality.
- Business value risk. This is the risk that the IT project doesn't deliver the expected business value.
- Existing business model failure risk. This is the risk that the IT project damages the existing organisation.
The Contract Model does not address the second two categories of risk and actually increases the customer's exposure to all three categories of risk.
The FiReControl Project is a classic example of the delivery risk de-railing the IT project. The UK National Audit Office noted that during the first two years of the contract there was little progress in delivering the IT system.5 Indeed, the DCLG does not appear to have received any working software before the contract was terminated. We do not know the reason for this but we can hazard a guess.
The outdated principles of the Contract Model assume that the Output-Based Requirements can be predicted upfront. As a result the Contract Model fails to adequately respond to changing conditions and forces the customer to incur costs disproportionate to the returns on the IT project.
The fallacy of predicting the Output-Based Requirements upfront
The assumption that the Output-Based Requirements can be predicted upfront is predicated on two further assumptions. Firstly, that the Output-Based Requirements are understood fully by both the customer and the supplier and, secondly, that the software can be finished before significant changes occur. In other words, to function optimally, the Contract Model requires both contracting parties to possess perfect information. This is a practical impossibility.
The very dynamics of the IT project lead to changes. It is only natural that, as the customer learns more about the latest technology and its relative strengths and weaknesses, the customer revises its thinking on how best to take advantage of the technology.
"… [S]ystems requirements cannot ever be stated fully in advance, not even in principle, because the user doesn't know them in advance – not even in principle. To assert otherwise is to ignore the fact that the development process itself changes the user's perceptions of what is possible, increases his or her insights into the application's environment, and indeed often changes that environment itself." 6
By the same token it is only natural that as the supplier learns more about the customer’s business processes, it will gain a deeper understanding of the problems that the customer is trying to solve and the opportunities that the customer is trying to harness.
In any event, it is not possible to anticipate how the many disparate design elements of the software will interact before the software is implemented, and this can frequently lead to surprises.
The assumption that the software can be finished before significant changes occur is also flawed. External forces are at play. Technology is evolving at an ever increasing pace. The market or context in which the concept for the software was conceived continues to change. Hence, the opportunities or risks to be addressed by the software also change. For example, the emergence of disruptive technologies such as Facebook, Twitter or the touch screen IPad can have a huge impact on any existing plans for software development and distribution. The regulatory environment may also change.
Recent studies, led by Al Goerner at the University of Missouri, Kansas City, demonstrate that the inherent value in Output-Based Requirements erodes exponentially over time. This rate of decay has been likened to the half-life of an unstable radioactive atom. The 'half-life' is the measure of the period of time it takes for the substance undergoing decay to decrease by half.
According to the studies carried out by the University of Missouri, the half-life of the value of the Output-Based Requirements has been rapidly decreasing. In 1980 this was around 10-12 years, by 2000 it had fallen to 2-3 years, and it is currently running at about 6 months.7
In other words, half of the Output-Based Requirements will become obsolete by the end of month 6, half of the remaining half (i.e. 1/4) will become obsolete by the end of month 12, half of the remaining quarter (i.e. 1/8) will become obsolete by the end of month 18, and so on. Hence, by the end of month 18, according to the University of Missouri studies, only 1/8 (i.e. 12.5%) of the Output-Based Requirements will still possess any inherent value.
In its desire to create certainty, the Contract Model actually creates the risk that when delivery finally occurs, what is delivered may no longer meet the customer’s needs.
The failure of the Contract Model to respond adequately to change
If changes happen, the customer will wish to change the Output-Based Requirements. As an integral part of the contract, the Output-Based Requirements cannot be amended to reflect a change without a formal amendment to the contract as agreed by the parties in accordance with the Change Control Mechanism. In a fixed price contract, the amendments are often seen as leading to additional work and the customer is required to pay additional fees. It is not uncommon for the supplier to view a change control as an opportunity to increase its margins.
The initial stage of the Change Control Mechanism is that the supplier analyses the impact of the change requested by the customer. The larger and more complex the IT project, and the greater the amount of work that is involved in the supplier carrying out this exercise. Sometimes, the impact of the change request is so complex that the supplier simply cannot work out how to incorporate the requested change into the existing IT project.
The process of analysing the impact of a change request can take so long and be so extensive that it has a destabilising effect on the IT project. The main team is only too aware that current work may be rendered redundant following the approval of the change request. The bigger the proposed change, the longer the hiatus while it is being analysed, and the more damaging the effects can be.8
Any change request will inevitably cause delay to the IT project. It is unlikely that the original timetable builds in a buffer for the supplier's resources to be diverted to this activity and for any resulting additional work to be undertaken. If is for this reason that both customers and suppliers consistently cite changes to the Output-Based Requirements as one of the main causes of failure of an IT project.
To make matters worse, the Contract Model mandates Sequential Development. It is not until testing, late on in the IT project, that the customer has visibility of the software. Up until that point it is very difficult for anyone to assess whether the IT project is on track. The deliverables of all earlier phases are documents that are based on assumptions. It is only when the software is actually built that anyone can accurately assess whether the IT project is actually on course to meet the Output-Based Requirements. However, there is a long gap, often in the order of years, between the date when the customer collects the Output-Based Requirements and the date when the supplier makes the first delivery of working software. The longer this gap, and the more likely that significant change has occurred during the intervening period.
Business value risk
The FiReControl project highlights the importance of demonstrating from the outset how the ICT project will deliver the expected business value and of obtaining the buy-in of all those involved. The DCLG was criticised by the National Audit Office for not making sufficiently clear the case for a centrally-dictated standard model of emergency call handling and mobilisation, operating from new purpose-built regional control centres. From the start many local Fire and Rescue Authorities and their Fire and Rescue Services criticised the lack of clarity on how a regional approach would increase efficiency.9 Unless the resulting software delivers tangible business value, it doesn't matter how state of the art or sophisticated it is, the intended end users may each simply decide not to use it.
The business value risk, actually overlooked by the Contract Model, is far more serious. There is, instead, an assumption that if the supplier delivers software that meets the Output-Based Requirements, it will therefore deliver business value to the customer. However, this in turn assumes that the customer knows what it needs. What we have found instead is that, although customers are very good at stating what they want, far too often customers do not in fact know what they need. As a result, it is not uncommon for the customer to be disappointed with the resulting software, even if the supplier can demonstrate that the software meets the Output-Based Requirements.
It is a sad indictment of the current state of software development that one of the greatest risks is that the supplier builds 'the wrong product'. This happens whenever the supplier successfully executes against the customer's specified Output-Based Requirements, but the resulting software does not add any real value to the customer. The software does not add value because it does not enable the customer to solve the problem that it had wanted to address.
The reason why customers to date have derived so little business value from the software delivered by the supplier is that the Contract Model is not referenced to the target outcomes of the customer (that is, the results that the customer wishes to achieve and which will add value to the customer). Instead, the Contract Model is referenced to the Output-Based Requirements, that is, the requirements for the deliverables of the IT project which are intended to contribute to and facilitate the achievement of the target outcomes.
People buy a hammer to knock in a nail so that they can put up a picture – they know that they can achieve their target outcome (putting up the picture) with the acquisition of the hammer. Unfortunately, in the context of software development it is not as straightforward to make the link between the delivery of the output (the software) and the achievement of the customer's target outcomes. Many people simply don't even try. This creates a large risk that the supplier will only deliver what the customer asked for – a vague set of Output-Based Requirements – rather than what the customer actually needs, which is to achieve the target outcomes.
Software development involves the transformation of ideas into deliverables to achieve business objectives. The catalyst for the IT project is generally a business case. This justifies at a strategic and financial level the acquisition of the software. The anticipated cost of the software is justified by various assumptions such as the improvement of business processes, increase in market share, increased revenue, reduction of support costs and so on. Following internal approval of the business case, the Output-Based Requirements are then collected and assimilated from everyone at the customer's organisation who has an interest in the resulting software system.
So if a business case generally precedes the specification of the Output-Based Requirements, why is it the case that the resulting software will not necessarily meet the target outcomes?
Firstly, the business case is untested. In many business cases there are elements which are based on assumptions rather than facts. These assumptions have not been proved to be true, and it is probable that many of them are in fact erroneous. Ideally, those assumptions should be tested before significant resources are invested in building a software system that delivers against the business case. But that rarely happens.
Secondly, the business case is typically produced at a high level and with a view to obtaining funding or budgetary approval. It is not uncommon for the business case to be very ambitious in terms of what the software will achieve, as this provides a better argument for investing in the acquisition of the software. It is less common for the business case to play an active role in steering the direction of the IT project. It is even less common for anyone to revisit the business case in the light of the progress of the IT project or to measure the progress of the IT project with reference to the business case.
The implications of this cannot be overstated. The DoD is one of the most sophisticated IT purchasers worldwide: it has a significant amount of leverage in negotiating contract terms because its annual spend its so large. And yet it derives practically no immediate business value from its investment in software development. Is it possible that other organisations, with less experienced procurement functions, actually derive less business value from their IT spend?
The most effective way for any organisation to reduce its IT spend is to ensure that only software which delivers business value is built. We need to consciously connect the levels and clarify how the resulting software will deliver business results.
Existing business model failure
The Contract Model does not address the possibility of existing business model failure risk. There is simply no recognition of the fact that when a new software system is launched, this may impact on the existing business processes. As a result, the Contract Model increases the exposure of the customer to existing business model failure risk, which is arguably the most insidious of the three categories of risk.
Perhaps, back in the 1980s when the Contract Model was first used, software systems were fairly discrete and limited in terms of their operation. However, today software systems are used for virtually every business function of an organisation. There may be end users at multiple levels of the organisation – for example, the finance director, accounts department, marketing director, marketing team and sales team may all need to use the same software system. This software system may interlink with other software systems within the organisation which are used by other end users. The software system may also interface with software systems of other organisations – such as the clients or the suppliers of the organisation.
In light of the many business processes that may be impacted by a new software system, it is essential that the transition to this system is managed in a way that contains the risk of existing business model failure to a minimum. However, the Contract Model generally requires that all of the Output-Based Requirements are delivered as a single batch. The larger the IT project and the larger this batch will probably be.
For many organisations it is simply not realistic to attempt to assimilate a software system of this scale and complexity into their existing business processes all at once. The risk of any of those existing business processes falling down under the enormity of the change is huge. It would be much better if the transition to the new system was managed in smaller launches, with an emphasis on the quality of the user experience throughout the transition.
Much research and many studies have been carried out on IT projects to try to understand why there are so many failures and why the extent of those failures can be so great. Yet to date the Contract Model has been largely ignored. We believe that the Contract Model is in need of a total overhaul. With our increasing dependency on IT and escalating costs of IT spend, an overhaul of the Contract Model cannot happen soon enough.
Susan and Gabrielle will be shortly releasing a flexible contract here.
1 ‘The failure of the FiReControl project’ Report by the Comptroller and Auditor General of the National Audit Office, 1 July 2011.
3 ‘Double whammy – How ICT projects are fooled by randomness and screwed by political intent’ by Alexander Budzier and Bent Flyvbjerg, Said Business School working papers, Oxford, August 2011.
4 Sometimes the contract does not contain sequential development, but even if the contract only contains the Output-Based Requirements and the Change Control Mechanism it is almost as problematic.
5 Infra Footnote 1.
6 ‘Lifecycle Concept Considered Harmful’ by Daniel McCracken and Michael Jackson, ACM Software Engineering Notes, April 1982.
7 We have been unable to find out more details regarding these studies. Clearly the half-life for the specifications will vary for different sectors. However, there is anecdotal evidence to support the view that the half-life could be even shorter in the technology sector.
8 ‘The curse of the change control mechanism’ by Susan Atkinson and Gabrielle Benefield, Computers & Law, May 2011.
9 Infra. Footnote 1.
About the Authors
Gabrielle Benefield is the CEO of Evolve Beyond, and helps people build great products and organizations. She is the author of the Scrum Primer and is a co-founder of Flexible Contracts with Susan Atkinson. She is currently writing two books on Outcome Delivery and HotHousing; adaptive frameworks that focus on the Outcomes that matter to the business and users, rather than the Outputs that create waste and confusing user experiences.
Susan Atkinson is a Consultant Solicitor at Keystone Law and a co-founder of Flexible Contracts with Gabrielle Benefield. She is a commercial lawyer, focusing on IT, outsourcing, e-commerce and intellectual property. She has over 15 years of legal experience, and has typically worked on high-value, complex commercial contracts, primarily in the technology, financial services and public sector, and often in an international context.
The "contract model" is not broken per se. I get the point, but again it's a matter of both knowing how to write good contracts (fixed cost, flexible scope is not so unusual nowadays) and also having the capability to deliver projects.
"How does a large software project get to be one year late? " - "1 day at a time". It's been said in the Mythical Man-Month and it's not news anymore. The problem relies on the management and programmers who are not actually committed to results. Accountability is a rare commodity in the software realm, that's the truth.
So, blaming the "contract model" is shallow at best.
But, to move to a better tomorrow one has to show benefits of the new approach to both parties, or we will stay stuck with the current approach. It'd be good to see a follow-up article here at InfoQ that includes especially the how do you sell flexible contracts to both clients and software vendors.
The US government, certainly the largest contractor in the world, has been pointing the finger at traditional procurement models as a root-cause of failure since the early 1990s. The Government Performance and Results Act of 1993, the Federal Acquisition Streamlining Act of 1994 (FASA), and the Clinger-Cohen Act of 1996 together directed Federal agencies to reevaluate its acquisition processes. The DoD's Defense Acquisition University formalized a body of knowledge for "Performance-Based Contracting," now called "Performance-Based Acquisition" (PBA). The OMB promotes PBA practices on Acquisition.gov.
Yes, it is true that the US government has not fully realized PBA (the rules mandating its use were rescinded for political reasons) -- and is perhaps not the best model for AD acquisition/procurement/contracting -- these efforts in the Federal acquisition community definitely demonstrate the authors' points.
Note, even if 'big' procurement contracts are signed, the software doesn't actually have to be delivered. in that manner. The software can be delivered in the usual agile way, with the 'box ticking' then mapping them to payment gates. This is why the characteristics mentioned in this article are important. From what I can make out, if any one changes, you don't have a characteristic failure any more.
Plus, it really shouldn't be the contract that explicitly defines any spec (the 'spec' should - Which the consumer driven requirements can check). So I too look forward to the new style of contract. Should be interesting. However, chances are it too, will be untested in the marketplace. As long as the agile contract itself can work in an agile way, you're set.
Re: Performance-Based Acquisition?
good paper, but where are the suggestions for improvement?
Re: good paper, but where are the suggestions for improvement?
We strongly believe that the traditional contract model is broken. We know this is not the only reason that projects go awry, but it is a significant factor and one which has been largely overlooked to date. There has been an assumption that this model cannot be fundamentally overhauled, and we wish to challenge that assumption. Your example of ‘fixed cost, flexible scope’ alludes only to the charging model, and does not address the fundamental flaws in the contract.
We agree that the problem is a lack of commitment to results, but this cannot be explained simply as poor management and programmers. Contracts drive behaviour. Traditional contracts are not focused on results, and they incentivise the management and programmers to focus on the wrong thing. We are developing an outcome-based contract to encourage the right behaviour, focused on results.
It is time for an analysis of project failures to look beyond management and programming capability and to examine how the contract model can influence the eventual outcome.
Agile all the way?
Indeed, an Agile should be accommodated by the contract.
Seeing your remarks on the lifetime of requirements, one certainty remains: everything will change in software. This makes it desirable that the construction quality of the software (that is hardly measured, even not in big projects) allows change. That this construction quality has great impact shows for example:
I would recommend the following:
1. Establish criteria such as above so the customer knows his software is constructed well. (preferably such criteria should be in the tooling so that it is impossible to deliver software that does not meet the construction criteria (just like the programmer has to solve compile and link errors)
2. Use a iterative process with short cycles including end-user tests.
3. Create a culture with focus on product vision for the end-user, software architecture and craftsmanship as opposed to focus on requirements, management & control, contracts, procedures. (also known as “flip the triangle” in Agile).
To quote Brooks: you should grow incrementally complex systems, not build them. (see The Design of Design, page 226)
I am looking forward to see such a flexible contract proposal, so I can try it out immediately.
Could you notify me when it is available?
Re: Agile all the way?
You can download the contracts at flexiblecontracts.com. We are working on the book currently with the guidelines on using it so stay tuned. I agree on growing rather than pre-planning everything. The lawyers don't realize how software is created, and even less about Agile methods. We need to continue to educate people on the realities of our industry.
Great article - thanks Frits
The inability of a customer to identify needs, as opposed to wants, is something I encounter regularly as a practising PM/BA, and I agree with the authors that a frequent early manifestation of this is the poorly thought out business case, usually abetted by an ineffective vetting process. A project that lacks a credible underlying narrative articulated in the business case makes effective project governance well-nigh impossible, regardless of the development methodology. I am at a loss to know why we continue to initiate projects based on flawed business cases despite the volumes that that have been written about it. Is it hubris? Ignorance?
As the authors note, the preparation of more detailed requirements by a competent business analyst is often the first time that the stakeholders have the opportunity to gain an effective insight into the business problem and the nature of an appropriate solution. Much is learned during the requirements definition which can be used to clarify and/or revise the original high-level requirements and the overall business case. Unfortunately this important process is often thwarted by the business analyst not being independent of the developer or not being up to the job, or being unable to do the analysis properly because of the perceived need to, “get on with the real work” (I still hear this) or pressure not to upset management expectations. Many of these issues can be addressed by senior management electing to authorise the technical development phase separately from the requirements definition phase subject to the business case remaining viable.
The section on business model failure highlights the importance of recognising that software implementation must be accompanied by organisational process change including process reengineering. Management of this change is one of those tasks that more broadly focussed IT practitioners and experienced project sponsors know needs to be done. Often, in organisations with a lower level of IT maturity, the IT practitioners are technically focussed and/or the project sponsor lacks the experience and the organisation winds up with a mish-mash of old and new processes and fails to realise the expected benefits.
Ben Linders May 28, 2015