The WyCash portfolio management system
OOPSLA '92 Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum)
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Agile Estimating and Planning
On the Effectiveness of the Test-First Approach to Programming
IEEE Transactions on Software Engineering
Future of Scrum: Parallel Pipelining of Sprints in Complex Projects
ADC '05 Proceedings of the Agile Development Conference
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship
Managing technical debt in software-reliant systems
Proceedings of the FSE/SDP workshop on Future of software engineering research
ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes
4th international workshop on managing technical debt (MTD 2013)
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 0.00 |
The technical debt metaphor is gaining significant traction in the software development community as a way to understand and communicate issues of intrinsic quality, value, and cost. The idea is that developers sometimes accept compromises in a system in one dimension (e.g., modularity) to meet an urgent demand in some other dimension (e.g., a deadline), and that such compromises incur a "debt": on which "interest" has to be paid and which should be repaid at some point for the long-term health of the project. Little is known about technical debt, beyond feelings and opinions. The software engineering 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 trade-offs based on models of their economic impacts. The goal of this second workshop is to discuss managing technical debt as a part of the research agenda for the software engineering field.