Technical Debt for Continuous Innovation: Strategies to Avoid


Strategies to fix technical debt is a topic that’s not going unnoticed this year. Discovering technical debt is inevitable as organizations modernize legacy applications. Most important, is the organization’s ability to understand the technical debt that exists, how much and find ways to fix it - even while the business moves quickly to keep up with feature demand.

Tackling technical debt is key to the success of continued innovation, as we learn in an article published on Dzone written by Stefan Thorpe, CTO of Caylent. Thorpe says “Accumulated (technical) debt can amass to such a level that software becomes unmaintainable and innovation is stifled in favor of daily firefighting or rewriting entire legacy software.”

There’s a number of factors that contribute to technical debt accumulation, including strained resources, project constraints, time and deadline pressure and low-quality code. While there’s no magical fix to solve all technical debt issues, a DevOps framework lays a foundation for making continuous improvement and integration (CI/CD), which can help with debt repayment.

“Existing technical debt can be liquidated through practices that systematically improve and facilitate code deployment and its quality. By automating as much of the development pipeline as possible through Continuous Integration and Continuous Delivery, devs are forced to tackle errors early on in order to achieve smooth automation.”

Read more about how DevOps is paving the way for reducing and managing technical debt across industries in these 2017 global trends - CRASH (CAST Research On Application Software Health) Report.

Filed in: Technical Debt
  This report describes the effects of different industrial factors on  structural quality. Structural quality differed across technologies with COBOL  applications generally having the lowest densities of critical weaknesses,  while JAVA-EE had the highest densities. While structural quality differed  slightly across industry segments, there was almost no effect from whether the  application was in- or outsourced, or whether it was produced on- or off-shore.  Large variations in the densities in critical weaknesses across applications  suggested the major factors in structural quality are more related to  conditions specific to each application. CRASH Report 2020: CAST Research on  the Structural Condition of Critical Applications Report
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Software Intelligence Report <> Papers
Making sense of cloud transitions for financial and telecoms firms Cloud  migration 2.0: shifting priorities for application modernization in 2019  Research Report
Load more reviews
Thank you for the review! Your review must be approved first
You've already submitted a review for this item