skip to main content
column

Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at ICSE 2011

Authors Info & Claims
Published:30 September 2011Publication History
Skip Abstract Section

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.

References

  1. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  2. Brown, N., Nord, R., Ozkaya, I. 2010. Enabling Agility through Architecture, Crosstalk, Nov/Dec 2010.Google ScholarGoogle Scholar
  3. Cunningham, W. 1992. The WyCash Portfolio Management System. OOPSLA' 92 Experience Report. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Cohn, M. 2006. Agile Estimation and Planning, Prentice Hall. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Fowler, M. 1999. Refactoring: Improving the Design of Existing Code. Addison-Wesley Professional. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  7. Highsmith, J. 2009. Agile Project Management 2nd ed. Addison Wesley.Google ScholarGoogle Scholar
  8. 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 ScholarGoogle Scholar
  9. 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 ScholarGoogle Scholar
  10. Martin, Robert C. 2008. Clean Code: A Handbook of Agile Software Craftsmanship. Addison Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Second International Workshop on Managing Technical Debt http://www.sei.cmu.edu/community/td2011/ Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. Sutherland, J. 2005. Future of Scrum: Parallel Pipelining of Sprints in Complex Projects. Proceedings of the Agile 2005 Conference, pp. 90--102. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at ICSE 2011

      Recommendations

      Comments

      Login options

      Check if you have access through your login credentials or your institution to get full access on this article.

      Sign in

      Full Access

      • Published in

        cover image ACM SIGSOFT Software Engineering Notes
        ACM SIGSOFT Software Engineering Notes  Volume 36, Issue 5
        September 2011
        160 pages
        ISSN:0163-5948
        DOI:10.1145/2020976
        Issue’s Table of Contents

        Copyright © 2011 Authors

        Publisher

        Association for Computing Machinery

        New York, NY, United States

        Publication History

        • Published: 30 September 2011

        Check for updates

        Qualifiers

        • column

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader