Tag: IT Debt

Strategies to fix technical debt is a topic that’s not going unnoticed this year.
Technical Debt for Continuous Innovation: Strategies to Avoid
Technical Debt standards have been debated for many years.  And now CISQ (Consortium for IT Software Quality) has released standard that not only measures by automates technical debt calculation in complex software systems.
Technical Debt: CISQ Releases New Standard to Define and Measure Technical Debt
Vision is a term often employed to describe leaders: i.e "they have vision" or "they are visionaries".
How Technical Debt Can Help You Be Innovative
This post is based on an interesting paper about managing technical debt at Google.
Managing Technical Debt At Google
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 into detail on how to calculate technical debt.
How To Calculate Technical Debt: A Top-Down Approach
In this presentation by Kimber Lockhart, as part of the Hack Summit (the virtual conference for programers), she discusses what to do once you’ve inherited bad code. She speaks less about the source of bad code (low budget, high pressure to meet deadlines, company’s decision to hire poor developers) and more on the steps to fix and prevent this code. She does mention that not all bad code is because of technical debt, since for her tech debt comes from a conscious decision to write poor code, but this presentation does address how to get rid of it.
Inheriting Bad Code: How to Fix and Prevent it

Our colleagues at Gartner have made a little bit of a stir in the media with their findings on IT debt. Almost every industry pub, and some bloggers, have opined by this point. Here is a stack containing some of the recent articles and posts on the topic:

Quantifying Technical Debt: Beware of Your Assumptions