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!

Using Agile Techniques to Pay Back Technical Debt

By Frances Lash | September 19, 2014

ee819135.Laribee_Figure1(en-us,MSDN.10)
Acknowledging that some form of technical debt exists in every codebase is paramount to managing debt and staying in “the black”. Asides from the fact that technical debt kills productivity thus leading to economic downsides, there exists a psychological downside to technical debt. If a developer dreads dealing with code that is brittle and filled ... read more

When Code is Considered Technical Debt

By Frances Lash | September 8, 2014

This post tries to explain when code should be considered technical debt, rather than define the term by itself. For example, the post explains that technical debt is often described as code that is difficult to maintain or does not fall under the idea of ‘good code’. The belief that there is technical debt in ... read more

Technical Debt: Do’s and Don’ts

By Frances Lash | September 2, 2014

Atlassian Resource Video.001 copy
This is a kind of ‘wiki-how’ on how to manage technical debt in an agile environment – the right way. Not that there is one right way, but there are a few basics that this article points out. Technical debt, like any other debt should be budgeted in the release and iteration planning. Ultimately, the ... read more

Confronting Technical Debt

By Frances Lash | August 28, 2014

There are a lot of posts out there that talk about how to handle technical debt so it doesn’t get out of control and start to affect your system’s performance. This post does address the reality of paying off technical debt, but also goes into detail of how to know where to start refactoring for ... read more

Technical Debt & Quality – Binary Thinking in an Analog World

By Frances Lash | August 27, 2014

Form Follows Function - All Things Architectural.clipular
This is really great post that discusses the idea that ‘quality is not negotiable’ and that ‘only technical debt enthusiasts believe that’. The post states that deciding what is negotiable isn’t really the decision of the developer – because they are not paying for the work, and that by ‘negotiating’ quality they are not tech ... read more

Technical Debt Measurement Webinar: Reversal Strategy Q&A Follow Up

By Frances Lash | August 26, 2014

CAST-Technical debt
Here’s a post from a while back that follows up the Q&A of the webinar we posted on how to reverse your technical debt. The post focuses on how to set up a technical debt measurement program, what tools to use, and how to manage the results you’ve generated from your tech debt measurement program. ... read more

Technical Debt – Why not just do the work better?

By Frances Lash | August 25, 2014

Here is a post that answers the question: why not just do the work better in order to avoid technical debt? Here it is explained that technical debt is not necessarily consciously done poor work (in the mode of code shortcuts) but also a result of many uncontrollable factors – such as the intrusion of ... read more

Technical Debt – What it is and What to do about it

By Frances Lash | August 21, 2014

Technical Debt - What it is and what to do about it - Iasa Global.clipular
This is a post that goes over what technical debt is, and what to do about it – while drawing away from the common misconceptions of the term. The post begins by quoting the definition of technical debt by Steve McConnell: “a design or construction approach that’s expedient in the short term but that creates ... read more

Feature Toggles are one of the worst kinds of Technical Debt

By Frances Lash | August 20, 2014

mh_dzone_logo
This is great post about how technical debt can accumulate when employing feature flags or toggles into mainline code as a shortcut to release. Feature flags or toggles are used to” build conditional branches into mainline code in order to make logic available only to some users or to skip or hide logic at run-time, ... read more

Software Process and Measurement Cast 301: Technical Debt Essay

By Frances Lash | August 19, 2014

spamcast-300dpi
Here’s a podcast of an essay on technical debt that delves into the reality of using technical debt and the payment of that debt. Thomas Cagely, the host, goes on to describe the practice of documentation, auditing, standards and processes maintenance, and technical debt ‘sizing and valuing’. He mentions possible strategies to maintain software, and ... read more