Technical Debt Is Now Costing Us $3.61 Per Line Of Code
CAST now estimates technical debt to cost companies $3.61 per line of code.
35% of those items considered to be technical debt were severe enough to adversely affect support of the system studied, potentially resulting in security, performance or uptime issues.
Outsourced and in-house developed applications didn’t show any difference in structure quality. The same was true for onshore and offshore applications.
Java EE applications were the most prevalent among those studied and received significantly lower performance scores as well as carrying greater technical debt than other languages.
Established development methods such as agile and waterfall scored significantly better in structural quality than custom methods, while waterfall scored the highest in transferability and changeability.
COBOL applications scored the highest in security, while .NET applications received the lowest security scores.
Modularity of systems may contribute to lower quality and reduced performance.
Government systems tend to be the lowest in maintainability.
The more frequently the code is released the higher the technical debt.
This is the second year that CAST has produced the report. This year's data was compiled from 160 different companies from a hodgepodge of industries. The total number of systems studied was 745, representing a combined 365 million lines of code.
Analysts at Gartner have also exposed and cited the growing problem of technical debt in organizations. David Norton wrote a blog post likening the problem to a time bomb that can be ignored for a period of time, but at some point it will cause serious harm to the affected organization.
CAST and other thought leaders on technical debt suggest that organizations should be accounting for technical debt as part of their capital budgets. Israel Gat's approach for monetizing technical debt was covered by InfoQ in 2010.
Why Congress had to act
So Agile sucks?
Re: So Agile sucks?
IMHO this is more true about those pseudo-agile projects which act like mini-waterfalls - nobody thinks of reducing scope in a sprint when it is clear that estimates have gone wrong, and the team ends up creating technical debt. Truly agile teams focus as much on maintaining engineering quality as on quicker releases.
Re: So Agile sucks?
Look at Nokia phones: they were strict waterfall before 2007, and then they switched to the purest Agile possible.
Don't loose faith in humanity, but if your faith in Agile is debunked a bit, that could actually help. :)
This is not surprising at all
I'll use an example of a tipical company which thinks that people are resources and manth-months effort is the only real calculation. This usually results is a heavy employee turnover as people get demotivated, so most developers tend to stay in this company for 1 year, 2 at most (Accenture, I'm looking at you). As part of this, knowledge is lost and a high number of unexperience developers end up maintaining relatively small codebases.
Another reason is that most companies fail big time in motivating / coaching their employees to become better developers and the result is having "expert" developers with 10 years of eperience, but in fact is 10 years of doing the same mistakes over and over again.
IMHO another useless report.
Good report,but all are the truth?
and transferability and changeability have little related to development methods,it is affected by Object-oriented design,or design method.
Re: This is not surprising at all
Evolving Culture and Values. Understanding the Tradeoffs. Growth through Failure. The Importance of Leadership and Open Communication.
Pedram Keyani Mar 11, 2014
Summly: An Award Winning Mobile App's Journey to the Cloud with Five-9s Availability on a Shoestring Budget
Eugene Ciurana Mar 11, 2014
Christophe Achouiantz Mar 11, 2014