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!

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

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

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

Meta-Architecture: The Solution to Architecture Technical Debt?

By Frances Lash | July 11, 2014

One of the mantras of Agile development teams is to do “just good enough” to get the job done. This is what drives the creation of  architecture that meets the bare minimum requirements to function. But the “just good enough” mindset is an easy way to incur technical debt. This is what the post, Architecture Technical ... read more

Architectural Debt and Moving to Software Defined Architectures

By Frances Lash | June 25, 2014

This article gives us an in depth look at another type of IT debt: architectural debt. It starts off with the jarring statistic that 72% of IT budgets are usually spent “keeping the lights on” or in other words day-to-day maintenance. The only way to reduce this proportion of the budget dedicated to maintenance is ... read more

“Real Options” for Technical Debt

By Alexandra Szynkarski | June 18, 2014

An interesting presentation is going on tomorrow about technical debt and the “real options” to balancing short term market  goals with long term stability. The process of taking out technical debt isn’t what’s difficult, knowing when you are accumulating debt and keeping track of it is the challenge. The event will be hosted by Agile Iowa ... read more

Technical Debt and Vendor Lock-In

By Alexandra Szynkarski | September 10, 2013

Vendor Lock-In
How do we know we are locked in with a vendor? The most important key to this question is “data”… which is what everybody should be worried about. A recent blog post on Business 2 Community describes the situation of vendor lock-in as not being able to get your data out of your tool or custom-built application ... read more

Technical Debt: Paying Back Your Creditors

By Francois Reynald | June 10, 2013

Swimming in Technical Debt
Would you still go for a swim if you saw that sign on the beach? Probably not. Most people would agree that a swim in the sea is not worth dying for. Now then, what drives people to cut corners in software engineering? I think the factors that are weighed in to take these decisions are diametrically opposed to ... read more

Broken Windows

By Corey Cossentino | February 27, 2013

Broken Windows Technical Debt
One of the tools we use when developing production web services is a script that runs nightly to compile a list of any errors in the webservers’ error logs, and email anything abnormal to the developer list. This often helps us to catch broken links, uninitialized value warnings, and code paths that we may have ... read more

Technical Debt: Naughty or Nice?

By Leon Fayer | January 7, 2013

Technical Debt-Good or Bad
Many years ago I was working with a very large customer, both from user-base and traffic perspective, with a pretty interesting business model at the time.  Their MO was that, “time to market” is everything.  And I mean everything.  With the vast majority of their initiatives they were willing to launch that day, knowing that ... read more