The Technical Debt Community

So you’ve got Technical debt… now what? Ward Cunningham coined the metaphor back in 1992, and it has since been taken on by the industry to describe the consequences of poor software architecture and bad coding. This website encourages a pragmatic view of technical debt, attempting to elevate the discussion from merely defining technical debt to finding approaches for business technology organizations to use technical debt awareness as a vehicle to fix fundamental problems

Recent blogs posts

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

Effective Teams; Always Releasable

By Frances Lash | July 3, 2014

CoC vs. Responsiveness to change
Here is a short and sweet post in a series about effective development teams. The content of the article is pretty standard technical debt overview. First, that what often prevents teams from achieving their optimal goals is their software. Software that is burdened with loose ends in the source code or where there is too ... read more

Technical Debt 101: More Haste, Less Speed

By Frances Lash | June 30, 2014

Brazilian Favelas
This is a really interesting post (which cites our interview with Steve McConnell on how to communicate technical debt) that delves into the culture surrounding technical debt management. Using comparisons to civil engineering and biblical references, this post goes deep into the analogy of technical debt. The debt analogy has been used to explain to non-technical ... read more

Technical Debt: What, Why, and How

By Frances Lash | June 25, 2014

steve mconnell
Here’s post that was cited in the article we recommended previously (Architectural Debt and Moving to Software-defined Architectures) that gives a clear and detailed description of technical debt. Technical debt is broken down, by Steve Mconnell CEO at Construx,  into two basic types: debt incurred unintentionally (the result of unplanned poor work) and debt incurred intentionally ... 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

The One Cost Engineers and Product Managers Don’t Consider

By Frances Lash | June 24, 2014

Kris Gale, VP Engineering at Yammer, in this article writes about a highly ignored cost: the complexity cost. Gale explains this cost as the debt accumulated by complicating features or technology to solve problems. The implementation of a new complicated feature is only a small fraction of the work needed to support and maintain that ... read more