Theory-W Software Project Management Principles and Examples
IEEE Transactions on Software Engineering
The WyCash portfolio management system
OOPSLA '92 Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum)
Supporting enterprise stakeholders in software projects
Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
Managing technical debt in software-reliant systems
Proceedings of the FSE/SDP workshop on Future of software engineering research
Managing technical debt in practice: an industrial report
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
An exploration of technical debt
Journal of Systems and Software
Assessing technical debt by identifying design flaws in software systems
IBM Journal of Research and Development
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
Technical debt is a term that has been used to describe the increased cost of changing or maintaining a system due to expedient shortcuts taken during its development. Much of the research on technical debt has focused on decisions made by project architects and individual developers who choose to trade off short-term gain for a longer-term cost. However, in the context of enterprise software development, such a model may be too narrow. We explore the premise that technical debt within the enterprise should be viewed as a tool similar to financial leverage, allowing the organization to incur debt to pursue options that it couldn't otherwise afford. We test this premise by interviewing a set of experienced architects to understand how decisions to acquire technical debt are made within an enterprise, and to what extent the acquisition of technical debt provides leverage. We find that in many cases, the decision to acquire technical debt is not made by technical architects, but rather by non-technical stakeholders who cause the project to acquire new technical debt or discover existing technical debt that wasn't previously visible. We conclude with some preliminary observations and recommendations for organizations to better manage technical debt in the presence of some enterprise-scale circumstances.