Skip to main content

On Technical Debt

I first came across the notion of "technical debt" in a web article about Agile development methods. The phrase instantly struck me as a pithy summary of all the problems that IT people experience with poor quality code that is rushed out to meet deadlines, code that will cause problems down the line.  We know the problems are there, waiting to hurt us, while our business partners tend to be oblivious to them.

So I was attracted by a local BCS Event on the topic.  I went along this evening to hear Ali Law lead an interesting and wide-ranging discussion.  Ali gave me a lot to consider.  I've always thought of technical debt in terms of maintainability, i.e. of code becoming harder to adapt as it becomes twisted out of shape.  Tonight's discussion suggested that technical debt could include defects, redundant functionality, mismatch with a changing environment, and complexity (of requirements, of design, of code...), as well as maintainability and supportability.  It doesn't just cover in-house code; it can apply to third-party systems that haven't been upgraded or that have become unsupported.  Someone also suggested that there should be an equivalent notion of "process debt", referring to business processes that are too complex, out of date or otherwise costly.

There are also many impacts of technical debt.  The obvious one to me was future cost, in terms of time required to fix things left unfinished.  One person in the audience had an example where the problems with a system directly affected sales, so the debt was more visible and immediate.  There can be other problems too.  You might encounter lack of trust with your business partners and/or customers.    Your developers might be demoralised at having to work with hard-to-maintain code.

My question was, how can we provide evidence of the problems that may be incurred by technical debt?  Ali based his proposals for managing the problem on the assumption that we can measure various aspects of the problem.  He said that we need to decide what types of debt concern us most, which may vary from one system to another within our portfolio.  Then we should find ways of measuring that debt in a way that connects to business value, whether that value is sales, costs, or user experience.  Then make these costs and risks evident to the decision makers so that they can be included in the prioritisation and investment decisions.

There was a lot of discussion about how to make use of these ideas.  The main point is that this presentation brings the problems into known processes for handling risks, trends, costs and priorities.  There were some side conversations about some techniques for reducing particular problems - such as using a good usability analysis to avoid creating redundant functionality.

For me, the big question is how much of the problem can we really measure?  Defects are relatively easy (although I liked Ali's suggested that we should score defects by the operation cost or loss of user experience they involve, so that we can measure a cumulative cost).  The discussion mentioned that we should measure actual usage of functionality, so that we can remove code that it never used.  Ali said that his firm has had success with Halstead and McCabe metrics in the past.  I've never been convinced by these, but to be fair I have never tried them in anger.  Ali did say that there are now several tools available for measuring code complexity; perhaps I should ask one of my team to investigate these.

This event was a useful opportunity to reflect on the question and to hear some potentially useful ideas.  I've only captured the gist of the discussion here; there were many points made in passing that were worth hearing.  For example, I've barely mentioned trust, which was actually a major part of Ali's message.    I don't know how many of these ideas I'll be able to put into practice but I hope we can start with one or two and see how we do.


Comments

Iain said…
Dave, I agree it's a great term.
I wonder if the notion of interest on technical debt is something that people think about... It seems to me that over time not adressing an issue can actually accumulate further debt.
An example might be; Technical staff member leaves out some fix due to time constraints in a project. Time passes and the project agrees to fix the issue as it is proving costly. Some time has passed and the details of how to resolve the problem have actually been to some extent forgotten. The cost to correct might be much higher than it would have been addressed when it intially surfaced. Also the business has been paying for the ommission presumably in the intervening time.

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…