International Conference on Technical Debt
Sun 29 May - Fri 3 June 2022 TechDebt 2022 with ICSE 2022Welcome to the website of the International Conference on Technical Debt 2022 conference. We are working hard to fill the website with all related information. Please check back soon! |
Wed 19 - Fri 21 May 2021 TechDebt 2021 with ICSE 2021It is with great sadness that we announce that TechDebt 2021 is going virtual. We share the concerns and feelings of ICSE 2021 organizers and believe that going fully virtual is the right way forward. For a detailed explanation, please read the announcement on ICSE’s website. |
Sun 28 - Tue 30 June 2020 TechDebt 2020 with ICSE 2020Welcome to the TechDebt 2020 website. Important: June 29: We have uploaded all presenter videos to a shared Google drive, available here. Technical debt describes a universal software development phenomenon: design or implementation constructs that are expedient in the short term but set up a technical context that can make future changes more costly or impossible. Software developers and managers increasi ... |
Sun 26 - Mon 27 May 2019 Montreal, QC, CanadaTechDebt 2019 with ICSE 2019Welcome to the website of TechDebt 2019. Technical debt describes a universal software development phenomenon: design or implementation constructs that are expedient in the short term but set up a technical context that can make future changes more costly or impossible. Software developers and managers increasingly use the concept to communicate key tradeoffs related to release and quality issues. The goal of th ... |
Sun 27 - Mon 28 May 2018 Gothenburg, SwedenTechDebt 2018 with * ICSE 2018 *Welcome to the website of TechDebt 2018. Technical debt describes a universal software development phenomenon: design or implementation constructs that are expedient in the short term but set up a technical context that can make future changes more costly or impossible. Software developers and managers increasingly use the concept to communicate key tradeoffs related to release and quality issues. The goal of th ... |
Paris Avgeriou
University of Groningen, The Netherlands
Netherlands
Philippe Kruchten
University of British Columbia
Canada
Robert Nord
Software Engineering Institute
United States
Ipek Ozkaya
Carnegie Mellon Software Engineering Institute
United States
Carolyn Seaman
University of Maryland Baltimore County
United States