An empirical assessment of technical debt practices in industry

Technical debt refers to the consequences of taking shortcuts when developing software. These consequences can impede the software growth and have financial implications. The software engineering research community needs to explore technical debt further from a practitioner standpoint.

[1]  Forrest Shull,et al.  Investigating technical debt folklore: Shedding some light on technical debt opinion , 2013, 2013 4th International Workshop on Managing Technical Debt (MTD).

[2]  J. R. Landis,et al.  The measurement of observer agreement for categorical data. , 1977, Biometrics.

[3]  J. Fleiss.  Measuring nominal scale agreement among many raters. , 1971 .

[4]  Carolyn B. Seaman,et al.  Defining the decision factors for managing defects: A technical debt perspective , 2012, 2012 Third International Workshop on Managing Technical Debt (MTD).

[5]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[6]  Jan Bosch,et al.  Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study , 2015, Inf. Softw. Technol..

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

[8]  Jesse Yli-Huumo,et al.  The Sources and Approaches to Management of Technical Debt: A Case Study of Two Product Lines in a Middle-Size Finnish Software Company , 2014, PROFES.

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

[10]  Bill Curtis,et al.  Estimating the Principal of an Application's Technical Debt , 2012, IEEE Software.

[11]  Rodrigo O. Spínola,et al.  Towards an Ontology of Terms on Technical Debt , 2014, 2014 Sixth International Workshop on Managing Technical Debt.

[12]  Forrest Shull,et al.  Investigating the impact of design debt on software quality , 2011, MTD '11.

[13]  Barry W. Boehm,et al.  What we have learned about fighting defects , 2002, Proceedings Eighth IEEE Symposium on Software Metrics.

[14]  Joost Visser,et al.  An empirical model of technical debt and interest , 2011, MTD '11.

[16]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[17]  C. Brodsky.  The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .

[18]  Ville Leppänen,et al.  Technical Debt and the Effect of Agile Software Development Practices on It - An Industry Practitioner Survey , 2014, 2014 Sixth International Workshop on Managing Technical Debt.

[19]  Eric Allman,et al.  Managing technical debt , 2012, Commun. ACM.

[20]  Radu Marinescu,et al.  Assessing technical debt by identifying design flaws in software systems , 2012, IBM J. Res. Dev..

[21]  Neil A. Ernst,et al.  Measure it? Manage it? Ignore it? software practitioners and technical debt , 2015, ESEC/SIGSOFT FSE.

[22]  Shari Lawrence Pfleeger,et al.  Principles of survey research: part 1: turning lemons into lemonade , 2001, SOEN.

[23]  Yuanfang Cai,et al.  Using technical debt data in decision making: Potential decision approaches , 2012, 2012 Third International Workshop on Managing Technical Debt (MTD).

[24]  Jeff Sutherland,et al.  Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, and Leave Competitors in the Dust , 2012 .

[25]  Peri L. Tarr,et al.  An enterprise perspective on technical debt , 2011, MTD '11.

[26]  Ayse Basar Bener,et al.  Measuring the principal of defect debt , 2016, RAISE@ICSE.

[27]  Klaus Schmid.  A formal approach to technical debt decision making , 2013, QoSA '13.

[28]  Zadia Codabux,et al.  Managing technical debt: An industrial case study , 2013, 2013 4th International Workshop on Managing Technical Debt (MTD).

[29]  Don S. Batory,et al.  Feature Models, Grammars, and Propositional Formulas , 2005, SPLC.

[30]  Christian Berger,et al.  Explicating, Understanding, and Managing Technical Debt from Self-Driving Miniature Car Projects , 2014, 2014 Sixth International Workshop on Managing Technical Debt.