Software Maintainability & Changeability Metrics

The demand for high quality and maintainability of software is increasing, setting it as a differentiator for the success or failure of a software product. Join the Technical Debt bloggers in discussions about how Technical Debt affects the functionality and the software maintainability factors of a system, and how these attributes can be measured. If you are interested in blogging for us, let us know!

Is Tracking Technical Debt A Waste Of Time?

By Frances Lash | February 26, 2015

mh_dzone_logo
Tracking technical debt in the development backlog is meant to make the costs and risks of the technical debt taken on visible; prioritizing debt payments with other work is supposed to ensure that the payments get made. This post argues that tracking debt is not worth it. These are the reasons listed: Some code often isn’t worth ... read more

How To Calculate Technical Debt: A Top-Down Approach

By Frances Lash | February 25, 2015

Screen Shot 2015-02-24 at 5.16.09 PM
As business leaders become more involved with IT investment decisions many CIOs have found it more difficult to receive funding for maintenance of applications and infrastructure. The result of this is that technical debt has become an even more useful term to explain to business stakeholders the importance of IT maintenance investments. This post goes ... read more

How DevOps Can Cut Innovation-Crushing Technical Debt

By Frances Lash | February 23, 2015

Screen Shot 2015-02-21 at 5.29.55 PM
In this post, technical debt management is looked at from a DevOps approach. Technical debt is defined here, as the price organizations pay when releasing poorly designed code. Companies that collect a large amount of technical debt are in risk of running into a situation where any innovation takes a backseat to putting out fires. ... read more

Microservices Architecture & Reducing Technical Debt

By Frances Lash | February 13, 2015

Screen Shot 2015-02-11 at 8.20.29 PM
Paying off technical debt, according to this post, can be made easier with microservices architecture. When building a code base, eventually, trade-offs between quality and delivering on time will arise. The benefit of trade-offs in software is that the option to later go back and fix these shortcuts is available. Quick and dirty shortcuts and ... read more

Is Technical Debt breaking the Software Development bank balance?

By Frances Lash | February 2, 2015

Screen Shot 2015-01-31 at 5.40.44 PM
Is technical debt still a valid metaphor in the present global software development world? The answer is yes, and this post goes on to present the benefits of such a metaphor while explaining just what technical debt is exactly. There is a growing concern on tech debt not simply because of the costs associated with ... read more

CISQ: Establishing Industry-wide Standards to improve Software Quality

By Frances Lash | January 28, 2015

Screen Shot 2014-11-28 at 11.13.17 PM
CISQ is the Consortium for IT Software Quality, a special interest group of the Object Management Group organized to create standards for measuring software quality, including the definition of technical debt and factors that influence it: security, performance, reliability, and maintainability.  This article, from SD Times, goes into depth about the Consortium of IT Software Quality – ... read more

The Technical Debt Singularity

By Frances Lash | January 23, 2015

Screen Shot 2015-01-22 at 2.28.50 PM
A technology singularity, in terms laid out by this post on technical debt, is a point when technology created by humans reaches the point where it can no longer be understood by its creators. A mathematical singularity is a point beyond which odd or unpredictable behaviours can be recognized. In formulating the hypothesis for this ... read more

Is Refactoring “Needless Rework”? – Refactoring for Design Level Smells

By Frances Lash | January 19, 2015

Here’s a post that delves into the necessity of refactoring in software engineering, comparing the practicality of refactoring in software to restructuring in urban planning. It begins by stating that when running software projects that span millions of lines of code the original design is usually good, over a period of time, however, the design ... read more

Technical Debt is Risk Management

By Frances Lash | January 9, 2015

If refactoring code reduces a code base by 80%, then the chance of missing a necessary change in the code base and the risk of missing something in testing that damages the production business are also reduced. Therefore, by this logic, the management of technical debt is in fact risk management. Using the analogy of ... read more

Not all Technical Debt should be Treated Equally

By Frances Lash | December 30, 2014

Screen Shot 2014-12-27 at 9.03.07 PM
The on going management of technical debt has become viewed as critical for the development of high quality and maintainable software, even by those who promote agile development processes. This consideration for tech debt management has contradicted the notion that development decisions should almost exclusively be driven by business value because of the difficulty of ... read more