Software Debt & Design Debt Overview
Join the Technical Debt bloggers in discussions about their thoughts on Software Debt, its impact on code and on the business. If you are interested in blogging for us, let us know!
By Tomas Malmsten | April 2, 2013
Technical Debt is something most teams struggle with in one way or other. One of the more common issues I encounter is how to visualize the actual cost of technical debt in a way that the business stakeholders understand. To achieve this I have used a special product backlog type with some additional data.
The debt needs to be ... read more
By Alexandra Szynkarski | March 11, 2013
Steve Garnett from Ripple Rock (an IT consulting company that assists customers in improving their software development capabilities) is one of many who has experienced Technical Debt on a project he worked on in the past. His new blog post captures a common problem: you know the Technical Debt is there, you know that it’s going to ... read more
By Alexandra Szynkarski | February 25, 2013
A question was recently posted on StackExchange asking the following: “Should I try to persuade my manager that code tidying should take priority over meeting deadlines?” And if so, what is the best way to go about it?
The answers that have been posted in response to this question have brought up a common dilemma: How ... read more
By Alexandra Szynkarski | February 11, 2013
I recently read a blog post by Cynthia Maxwell, about how important it is to hire A-players to avoid Technical Debt. She’s seen plenty of cases where founders of start-ups have recruited average and inconsistent B-players (as opposed to self-sufficient A-players) to work on their IT systems. Most of the time it results in months ... read more
By Alexandra Szynkarski | January 14, 2013
Living with Technical Debt is possible, as long as it is measured and monitored correctly. This presentation from Sam Pullara (to the First Round Capital CTO Summit in October 2012) is a good synopsis of what Technical Debt means and what the debt could encompass from software architecture to security.
To add to the presentation, here ... read more
By Dr. Nico Zazworka | December 5, 2012
Some months ago we presented three webinars to Lockheed Martin, IEEE, and Boeing on current research in automated identification of Technical Debt through code analysis tools. The topics covered a basic introduction of the Technical Debt concepts and terminology, as well as first research results describing how current tools (code smell tools, ASA issue tools, ... read more
By Daniel.Hardman | November 28, 2012
In the 1950s, researchers at Johns Hopkins conducted some very troubling experiments. They caught wild rats and squeezed them in their hands until they stopped struggling, teaching them that nothing they did would let them escape the crushing grip of their human captors. Then they dropped the rats in a bucket of water and watched ... read more
By Alexandra Szynkarski | November 26, 2012
Welcome to the OnTechnicalDebt Expert Interview Series. This month’s interview focuses on discussing the ways in which different areas of software debt can be tracked, particularly in an Agile environment, and how we can communicate these issues with management. This interview will give us insight into real-life IT projects and how teams are effectively dealing with Technical Debt today.
function ping0() ... read more
By Daniel.Hardman | November 5, 2012
In my previous posts about tech debt, I focused on how we can help organizations remember their debts, and on understanding how tech debts are funded and paid back.
These topics hit a raw nerve with coders and testers. Those in the trenches often feel very keenly the cost of doing things in a messy way, and it’s ... read more
By Alexandra Szynkarski | September 28, 2012
I recently came across this video of Elizabeth Naramore (PHP community manager) talking about Software Debt at the Atlanta PHP User Group presentation (Sept 6, 2012).
I really like this presentation as she explains how the term relates to developers in a clear (and awesome) way: