Does Code Decay? Assessing the Evidence from Change Management Data
IEEE Transactions on Software Engineering
How Does the Architect's Role Change as the Software Ages?
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Key Aspects of Software Release Planning in Industry
ASWEC '08 Proceedings of the 19th Australian Conference on Software Engineering
IEEE Software
Agile Infrastructure and Operations: How Infra-gile are You?
AGILE '08 Proceedings of the Agile 2008
IEEE Software
A Method for Balancing Short- and Long-Term Investments: Quality vs. Features
SEAA '08 Proceedings of the 2008 34th Euromicro Conference Software Engineering and Advanced Applications
What Types of Defects Are Really Discovered in Code Reviews?
IEEE Transactions on Software Engineering
Metrics Functions for Kanban Guards
ECBS '10 Proceedings of the 2010 17th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems
Proceedings of the Third C* Conference on Computer Science and Software Engineering
Perfectionists in a World of Finite Resources
IEEE Software
A portfolio approach to technical debt management
Proceedings of the 2nd Workshop on Managing Technical Debt
An enterprise perspective on technical debt
Proceedings of the 2nd Workshop on Managing Technical Debt
Prioritizing design debt investment opportunities
Proceedings of the 2nd Workshop on Managing Technical Debt
Hi-index | 0.00 |
Context: Whilst technical debt is considered to be detrimental to the long term success of software development, it appears to be poorly understood in academic literature. The absence of a clear definition and model for technical debt exacerbates the challenge of its identification and adequate management, thus preventing the realisation of technical debt's utility as a conceptual and technical communication device. Objective: To make a critical examination of technical debt and consolidate understanding of the nature of technical debt and its implications for software development. Method: An exploratory case study technique that involves multivocal literature review, supplemented by interviews with software practitioners and academics to establish the boundaries of the technical debt phenomenon. Result: A key outcome of this research is the creation of a theoretical framework that provides a holistic view of technical debt comprising a set of technical debts dimensions, attributes, precedents and outcomes, as well as the phenomenon itself and a taxonomy that describes and encompasses different forms of the technical debt phenomenon. Conclusion: The proposed framework provides a useful approach to understanding the overall phenomenon of technical debt for practical purposes. Future research should incorporate empirical studies to validate heuristics and techniques that will assist practitioners in their management of technical debt.