Clik here to view.
Webinar – Managing and Measuring Technical Debt (IEEE Software)
This is a great webinar on “Managing and Measuring Technical Debt”, which was held by two of Fraunhofer CESE’s research scientists, Dr. Carolyn Seaman and Dr. Nico Zazworka on Technical Debt, as part...
View ArticleWebinar – Identifying & Tracking Technical Debt (IEEE Software)
Last year, Dr. Carolyn Seaman and Dr. Nico Zazworka hosted an extremely informative webinar on “Managing and Measuring Technical Debt” as part of the Lockheed Martin/IEEE Computer Society Webinar...
View ArticlePaying Down the Interest on your IT Technical Debt — CAST
Dr. Bill Curtis – Senior Vice President and Chief Scientist with CAST – lays out the “Technical Debt Management Cycle”, a 7-step process for analyzing and measuring Software Debt so you can relate...
View ArticleClik here to view.
Ted Theodoropoulos: How to Successfully Manage Technical Debt
Welcome to the OnTechnicalDebt Expert Interview Series. This interview focuses on how Technical Debt can be taken on safely and managed successfully – ultimately bridging the gap between technology and...
View ArticleClik here to view.
“IT Organizations Have Far Too Much Technical Debt”
Dr. Bill Curtis, Senior VP and Chief Scientist at CAST, explains in this interview that we need to measure the structural quality of business applications and incorporate Technical Debt demands in...
View ArticleClik here to view.
Time to Start Estimating Technical Debt
Last week IEEE Software published a special edition for their Nov/Dec issue, dedicated to Technical Debt! My colleagues and I at CAST Research Labs put together an article which was featured in the...
View ArticleCISQ Webinar: The Future of Software Sizing with Automated Function Points
Consortium for IT Software Quality (CISQ) have recently announced the availability of an OMG Specification for Automated Function Points (AFP). Functions points (or source lines of code) have been used...
View ArticleTechnical Debt for the Businessman
The great thing about the term Technical Debt is that it’s easily understood by all stakeholders in a company. For those that do not work in IT, the association of “debt” with the “technical” remains...
View ArticleReducing Technical Debt… Encouraging Software Developers to Document Code
Documentation debt is often overlooked by software developers and this post provides efficient ways of using persuasive technology (which is computer technology designed with the goal of shaping or...
View ArticleThe One Cost Engineers and Product Managers Don’t Consider
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...
View ArticleArchitectural Debt and Moving to Software Defined Architectures
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...
View ArticleConfronting Technical Debt
There are a lot of posts out there that talk about how to handle technical debt so it doesn’t get out of control and start to affect your system’s performance. This post does address the reality of...
View ArticleWhy is Programming so Hard? – Incidental and Accidental Complexity
Accidental complexity can be referred to as technical debt or sometimes spoken about as incidental complexity – ultimately there is a difference between conscious and unconscious sources of poor code....
View ArticleClik here to view.
Inheriting Bad Code: How to Fix and Prevent it
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...
View ArticleMove Fast, Minimize Technical Debt
This is post with some tips for start-ups to minimize their technical debt. First, it needs to be decided which code is going to be kept. Start-ups will often make code that is temporary and some code...
View ArticleClik here to view.
Not all Technical Debt should be Treated Equally
The on going management of technical debt has become viewed as critical for the development of high quality and maintainable software, even by those who promote agile development processes. This...
View ArticleClik here to view.
The Three Kinds of Code: Divergent Perceptions about Cost
This post discusses the three categories of code that can be found within a certain project and that confusion about them plus a misunderstanding about their actual cost can lead to trouble. The three...
View ArticleCISQ: Establishing Industry-wide Standards to improve Software Quality
CISQ is the Consortium for IT Software Quality, a special interest group of the Object Management Group organized to create standards for measuring software quality, including the definition of...
View Article6 Ways to Keep Technical Debt at Bay
It is commonly mentioned, when speaking on technical debt, that small amounts of debt incurred, if they are deliberate and well monitored, can be useful to any development team. However, it is always...
View ArticleThe Bunny Theory of Code: Keeping Poor Quality Code from Multiplying
This is a post that discusses a type of technical debt that arises when bad quality code finds it way into the source control. As with other types of technical debt, the bunny theory of code described...
View Article
