The Seventh International Workshop on Managing Technical Debt was held in Bremen, Germany, on October 2 in conjunction with ICSME 2015.
Delivering complex, large-scale systems faces the ongoing challenge of how best to balance rapid deployment with long-term value. Theoretical foundations and empirical evidence for analyzing and optimizing short- term versus long-term goals in large-scale projects are needed. From the original description—“not quite right code, which we postpone making right”—various people have used the metaphor of technical debt to describe many kinds of debts or ills of software development. On one hand, the practitioner community has increased interest in understanding and managing debt. On the other hand, the research community has an opportunity to study this phenomenon and improve the way it is handled. We can offer software engineers a foundation for managing such tradeoffs based on models of their economic impacts. Technical debt succinctly communicates the issues observed in large-scale long-term projects:
- There is an optimization problem where focusing on the short-term puts the long-term into economic and technical jeopardy.
- Design shortcuts can give the perception of success until their consequences start slowing projects down.
- Software development decisions, especially architectural ones, must be actively managed and continuously analyzed quantitatively as they incur cost, value, and debt.
Yet many questions remain open, such as
- What is the lifecycle of technical debt?
- How is technical debt related to evolution and maintenance activities?
- How can information about technical debt be empirically collected for developing conceptual models?
- What metrics need to be collected so that key measurement and pay-off analysis can be conducted?
- How can technical debt be visualized and analyzed?
- How should we manage technical debt incurred by external business constraints such as acquisitions and market ecosystems?
- How can we assign business value to intrinsic qualities (e.g., cohesion and coupling)?
- How do we manage dependencies between different items of technical debt?
- How can we create traces between technical debt items and other software engineering artifacts?
- How we can quantify costs and benefits of refactorings?
- What are the right tools for managing technical debt?
- How can we apply financial theories to manage technical debt?
- How can we benchmark the tools that identify and measure technical debt?
We seek papers on practical experience with technical debt and approaches that attempt to answer these questions. All submitted papers must conform to the ICSME Formatting Instructions, and must not exceed 8 pages for all text, inclusive of figures, tables, and appendices, with up to one additional page for references only. All submissions must be in PDF. Submit your paper electronically via EasyChair. We invite submissions of papers in any areas related to the themes and goals of the workshop in the following categories:
- Research papers, describing innovative and significant original research in the field
- Industrial papers, describing industrial experience, case studies, challenges, problems, and solutions
In either category, we look for long papers (8 pages), describing mature results, and short papers (4 pages), describing emerging results and future trends.
Links to presentations,
proceedings, and results of previous workshops
- P. Kruchten, R. L. Nord,
I. Ozkaya. "Technical Debt: From Metaphor to Theory and Practice," IEEE
Software Special Issue on Technical Debt, Nov/Dec 2012. Multimedia
highlights include four interviews
with key practitioners on technical debt.
Shull, D. Falessi, C. Seaman, M. Diep, and L. Layman, "Technical
Debt: Showing the Way for Better Transfer of Empirical Results," in Perspectives on the Future of Software
Engineering, J. Münch and K. Schmid, Eds. Elsevier, 2013, pp. 179–190.
- D. Falessi, P. Kruchten,
R. Nord, and I. Ozkaya. "Technical Debt at the Crossroads of Research and Practice:
Report on the Fifth International Workshop on Managing Technical Debt," ACM SIGSOFT Software
Engineering Notes, Volume 39, Issue 2, March 2014 (to appear).