Perspectives on managing technical debt: A transition point and roadmap from Dagstuhl

  • Clemente Izurieta
  • , Ipek Ozkaya
  • , Carolyn Seaman
  • , Philippe Kruchten
  • , Robert Nord
  • , Will Snipes
  • , Paris Avgeriou

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

8 Citations (Scopus)

Abstract

Thirty-three practitioners, researchers, students, and tool vendors gathered in Dagstuhl, Germany, for five days in April 2016 to discuss the state of managing technical debt in software engineering. Participants reflected on the significant advances that the Managing Technical Debt (MTD) community has made since its inception in 2010; reached a consensus on a definition, called the Dagstuhl 16K technical debt definition; and discussed avenues for future progress in the area. This paper provides a brief history, summarizes current research, and offers a roadmap and a vision that describe the areas of research where significant challenges remain.

Original languageEnglish
Title of host publicationCEUR Workshop Proceedings
Place of PublicationHamilton
Pages84-87
Number of pages4
Volume1771
Publication statusPublished - 1-Jan-2016
EventJoint of the 4th International Workshop on Quantitative Approaches to Software Quality, QuASoQ 2016 and 1st International Workshop on Technical Debt Analytics, TDA 2016 - Hamilton, New Zealand
Duration: 6-Dec-2016 → …

Publication series

NameCEUR Workshop Proceedings
ISSN (Print)1613-0073

Conference

ConferenceJoint of the 4th International Workshop on Quantitative Approaches to Software Quality, QuASoQ 2016 and 1st International Workshop on Technical Debt Analytics, TDA 2016
Country/TerritoryNew Zealand
CityHamilton
Period06/12/2016 → …

Keywords

  • Software decay
  • Software economics
  • Software project management
  • Software quality
  • Technical debt

Fingerprint

Dive into the research topics of 'Perspectives on managing technical debt: A transition point and roadmap from Dagstuhl'. Together they form a unique fingerprint.

Cite this