980.64M lines of code 4835 analyzed projects days of Technical Debt
Latest Tweet : RT @PolloOsorio RT @JoshuaKerievsky: "Have a strategic budget for cleaning #techdebt". --@agile_exec #lkna13
  • May 15, 2013, No comments yet

    Technical Debt, Resign Patterns: Interview with Patroklos Papapetrou

    An agile enthousiast who seeks excellence in software engineering. This is how Patroklos Papapetrou defines himself. Let's have a techdebt talk with this greek "software gardener" who recently published a very interesting approach on how to identify & remediate resign patterns with code metrics and agile practices, based on the original article written by Michael Duell

  • Feb 6, 2013, No comments yet

    The 5th Technical Debt (Jan. 2013) report is available

    This is the fifth report based on TechDebt.org, a perfect occasion for us to review the past year with metrics, a collection of previous experts interviews and the results of our survey sent to a hundred of IT organizations on how they define and manage Technical Debt of their software development projects

  • Feb 6, 2013, No comments yet

    Why did Technical Debt decrease so much?

    If you are a regular reader of our Technical Debt Reports, you have probably noticed that the technical debt decreased from 374K days to 38K days. Don't worry, we're not wizards and remediation costs do not magically disappea. However, a quick explanation is necessary

  • Dec 14, 2012, No comments yet

    Call for Papers: 4th International Workshop on Managing Technical Debt

    Delivering complex, large-scale systems faces the ongoing challenge of how best to balance rapid deployment with long-term value. From the original description—"not quite right code which we postpone making it right"—various people have used the metaphor of technical debt to describe many other kinds of debts or ills of software development, encompassing broadly anything that stands in the way of deploying, selling, or evolving a software system or anything that adds to the friction from which software development endeavors suffer: test debt, people debt, architectural debt, requirement debt, documentation debt, or just an amorphous, all-encompassing software debt

  • Nov 16, 2012, No comments yet

    TechDebt 1.1 is online, with a brand new interface

    At least, the latest version of TechDebt's dashboard is online. Six month after the launch, TechDebt 1.1 comes with a brand new interface, deep focus on technical debt and software quality measures, technology benchmark and metrics history. Let's see what's new

  • Nov 2, 2012, No comments yet

    Interview with Israel Gat, on Technical Debt

    After a pause this summer, we continue our serie of interviews with people involved into Technical Debt management. Israel Gat, Director of Cutter Consortium’s Agile Product & Project Management practice, shares his experience on how

  • Nov 2, 2012, No comments yet

    Technical Debt in figures: TechDebt Report #3 available!

    This is the third report based on TechDebt.org‘s data. It presents the main evolutions of the audit database and the various metrics of the dashboard. It will also give you some tips to configure your rules repository and especially five important rules that seem unknown. This report details the software quality metrics collected since July,

  • Jul 24, 2012, 2 Comment »

    Technical Debt in figures: TechDebt Report #2 available!

    1,293 software projects tracked, 78M+ lines of code analyzed, 59K days of technical debt detected: The secondeTechDebt Report (July, 2012) is available for download on Tocea's website. Thanks to Armel Gouriou for this paper

  • Jul 24, 2012, 1 Comment »

    Interview with Ipek OZKAYA (SEI) on Technical Debt, Agile and Architecture

    When thinking about technical debt of applications, many questions come in our minds: Should we take architecture's defects into account to quantify the debt, as we already do with code defects? Can Agile developments generate an unintended debt? Ipek OZKAYA, a senior member of the technical staff at SEI, kindly answered to our questions

  • Jul 9, 2012, No comments yet

    Interview with Philippe KRUCHTEN on technical debt

    Let's continue our serie of interviews with people who had and continue having major influence on the definition of technical debt metaphor and its implementation in software development projects. Philippe KRUCHTEN, who directed the development of the RUP (Rational Unified Process), explains his vision of technical debt and how to manage it, in order to take right decisions at the right time

  • Jun 27, 2012, No comments yet

    Sigma (a french IT company) joins TechDebt as a contributor

    Sigma -a French IT company specialized in software development, consulting, integration and outsourcing- contributes to TechDebt.org

  • Jun 21, 2012, 1 Comment »

    Interview with Jean-Louis LETOUZEY on Technical Debt and SQALE

    One week after the discussion with Ward Cunningham on technical debt, let’s have a talk with Jean-Louis LETOUZEY, author of the SQALE method. Even if the debt metaphor should be sufficient in itself in many cases, quantitative and tangible data may provide “shareholders” with precious indicators for their “investment decisions”

  • Jun 15, 2012, No comments yet

    Technical Debt in figures: TechDebt Report #1 available!

    The first TechDebt Report (June, 2012) is available for download on Tocea’s website. Thanks to Armel Gouriou for this first paper

  • Jun 14, 2012, No comments yet

    IT&L@bs (an entity of Orange Business Services) joins TechDebt as a contributor

    IT&Labs, an entity of Orange Business Services which provides companies with IT expertise for strategical projects such as evaluation of critical applications, contributes to TechDebt.org

  • Jun 14, 2012, 3 Comment »

    Interview of Ward Cunningham, on technical debt

    Talking about technical debt without interviewing the father of the concept would be a bit pretentious. Ward Cunningham has kindly agreed to answer questions from TechDebt's readers about the debt metaphor: What is debt, what's not? Is it relevant trying to measure it? Must agile teams fight it at all costs

  • Jun 11, 2012, No comments yet

    New widget available: Technical Debt Days

    A new widget has been added to the Technical Debt dashboard: Technical Debt Days. This widget indicates the effort (in days) needed to correct a software project by applying programming best practices (naming convention, performance, dead code, duplication, etc.) into code

  • May 24, 2012, No comments yet

    TechDebt.org is online!

    Welcome to TechDebt.org! We hope this information will help to better control the technical debt of your applications in deciding for the most relevant and cost-effective remediation strategies. TechDebt.org is presented by Tocea and populated by Scertify™ Refactoring Assessment,