Abstract
The technical debt metaphor is gaining significant traction in the software development community as a way to understand and communicate about issues of intrinsic quality, value, and cost. This is a report on a second workshop on managing technical debt, which took place as part of the 33rd International Conference on Software Engineering (ICSE 2011). The goal of this second workshop was to discuss the management of technical debt: to assess current practice in industry and to further refine a research agenda for software engineering in this area.
- Brown, N., Cai, Y., Guo, Y., Kazman, R., Kim, M., Kruchten, P., Lim, E., MacCormack, A., Nord, R., Ozkaya, I., Sangwan, R., Seaman, C., Sullivan, K., Zazworka, N., 2010. Managing Technical Debt in Software-Reliant Systems, 2010 FSE/SDP Workshop on the Future of Software Engineering Research. Google ScholarDigital Library
- Brown, N., Nord, R., Ozkaya, I. 2010. Enabling Agility through Architecture, Crosstalk, Nov/Dec 2010.Google Scholar
- Cunningham, W. 1992. The WyCash Portfolio Management System. OOPSLA' 92 Experience Report. Google ScholarDigital Library
- Cohn, M. 2006. Agile Estimation and Planning, Prentice Hall. Google ScholarDigital Library
- Fowler, M. 1999. Refactoring: Improving the Design of Existing Code. Addison-Wesley Professional. Google ScholarDigital Library
- Erdogmus, H., Morisio, M., and Torchiano, M. 2005. On the Effectiveness of the Test-First Approach to Programming. IEEE Trans. Softw. Eng. 31, 3 (Mar. 2005), 226--237. Google ScholarDigital Library
- Highsmith, J. 2009. Agile Project Management 2nd ed. Addison Wesley.Google Scholar
- InfoQ: What Color is your Backlog? Interview with Philippe Kruchten, May 02, 2010. Available from: http://www.infoq.com/news/2010/05/what-color-backlogGoogle Scholar
- McConnell, S. 2007. Technical Debt. 10x Software Development {cited 2010 September 17}; http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspxGoogle Scholar
- Martin, Robert C. 2008. Clean Code: A Handbook of Agile Software Craftsmanship. Addison Wesley. Google ScholarDigital Library
- Second International Workshop on Managing Technical Debt http://www.sei.cmu.edu/community/td2011/ Google ScholarDigital Library
- Sutherland, J. 2005. Future of Scrum: Parallel Pipelining of Sprints in Complex Projects. Proceedings of the Agile 2005 Conference, pp. 90--102. Google ScholarDigital Library
Index Terms
- Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at ICSE 2011
Recommendations
Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt
As the pace of software delivery increases and technology rapidly changes, organizations seek guidance on how to insure the sustainability of their software development effort. Over the past four years running the workshops on Managing Technical Debt, ...
Technical debt in software development: from metaphor to theory report on the third international workshop on managing technical debt
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. This is a report on a third workshop on managing technical debt, which ...
Technical Debt in Agile Development: Report on the Ninth Workshop on Managing Technical Debt (MTD 2017)
We report on the Ninth International Workshop on Managing Technical Debt, collocated with the 18th International Conference on Agile Software Development (XP 2017) in Cologne. The technical debt research community continues to expand through ...
Comments