Lessons Learned from the ProDebt Research Project on Planning Technical Debt Strategically

Due to cost and time constraints, software quality is often neglected in the evolution and adaptation of software. Thus, maintainability suffers, maintenance costs rise, and the development takes longer. These effects are referred to as “technical debt”. The challenge for project managers is to find a balance when using the given budget and schedule, either by reducing technical debt or by adding technical features. This balance is needed to keep time to market for current product releases short and future maintenance costs at an acceptable level.

[1]  Jürgen Münch,et al.  CQML Scheme: A Classification Scheme for Comprehensive Quality Model Landscapes , 2009, 2009 35th Euromicro Conference on Software Engineering and Advanced Applications.

[2]  Carolyn B. Seaman,et al.  A Balancing Act: What Software Practitioners Have to Say about Technical Debt , 2012, IEEE Softw..

[3]  Ward Cunningham,et al.  The WyCash portfolio management system , 1992, OOPSLA '92.

[4]  Marcus Ciolkowski,et al.  Formative Evaluation of a Tool for Managing Software Quality , 2017, 2017 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM).