skip to main content
10.1145/2660252.2663599acmconferencesArticle/Chapter ViewAbstractPublication PagessplashConference Proceedingsconference-collections
tutorial

TD 2014: workshop on technical debt in a world of big data and big teams

Published:14 October 2014Publication History

ABSTRACT

Technical debt is an unavoidable part of software development in today's fast-paced market, but it is ignored by many of the people who should care about it most. In large systems, a portion of the accumulating technical debt is just "sloppy design" caused by schedule pressure and other project forces. But the most important part of technical debt is directly related to project size and data complexity. How much technical debt is about large development teams and geographical distribution? How do current "big data" techniques (Hadoop, NoSQL, parallel algorithms, MapReduce) relate to technical debt issues? This workshop explored strategies for understanding the impact of technical debt. If we believe that technical debt is an important issue in long-term software product development, do we have ways to keep the technical debt from causing development gridlock?

References

  1. Ward Cunningham, "Technical Debt" article and video about the Technical Debt metaphor on the Portland Patterns Wiki site, http://c2.com/cgi/wiki?WardExplainsDebtMetaphor.Google ScholarGoogle Scholar
  2. Technical Debt online community website: http://www.ontechnicaldebt.com.Google ScholarGoogle Scholar
  3. SPLASH 2013 Workshop on Technical Debt final report: http://manclswx.com/workshops/splash13/final_report.htmlGoogle ScholarGoogle Scholar
  4. Eltjo R. Poort, "Driving Agile Architecture with Cost and Risk," IEEE Software, September-October 2014, pp. 20-23.Google ScholarGoogle Scholar
  5. Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Joost Visser, "Technical debt in software development: from metaphor to theory," ACM SIGSOFT Software Engineering Notes, September 2012, pp. 36-38. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. Frederick P. Brooks, "No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, April 1987, pp. 10-19. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. TD 2014: workshop on technical debt in a world of big data and big teams

      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
      • Published in

        cover image ACM Conferences
        SPLASH '14: Proceedings of the companion publication of the 2014 ACM SIGPLAN conference on Systems, Programming, and Applications: Software for Humanity
        October 2014
        102 pages
        ISBN:9781450332088
        DOI:10.1145/2660252

        Copyright © 2014 Owner/Author

        Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.

        Publisher

        Association for Computing Machinery

        New York, NY, United States

        Publication History

        • Published: 14 October 2014

        Check for updates

        Qualifiers

        • tutorial

        Upcoming Conference

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader