SPLASH '14 Workshop: Technical Debt

Workshop date:  Monday October 20 or Tuesday October 21, 2014, 8:30am - 5pm
Location:  SPLASH '14 Conference in Portland

Website Contents

Workshop Overview

This is the website for the SPLASH workshop on technical debt.

Technical debt is a term that was coined by Ward Cunningham in 1992 to explain the accidental complexity that is a side-effects of "going faster" in the development work on a large code base.

Technical debt is a popular and powerful metaphor for small teams, projects with very short development cycles, and teams working in agile ecosystems, but it can apply to development projects of any size or circumstances.

This workshop will examine the sources of technical debt, especially in the world of big software engineering. What are the best practices for keeping technical debt under control? The workshop participants are invited to share both academic and industrial experiences.

This workshop has some overlap with the SPLASH 2013 workshop on technical debt (see SPLASH 2013 technical debt workshop report for more information on what we discussed).


How to join the Workshop

What are your experiences in dealing with technical debt? You can join in on the discussion.  Here is how you can become part of the workshop:

  1. Contact one of the workshop organizers listed below.
  2. Prepare a one-page "position paper" -- containing your ideas, questions, and experiences.  Send your position paper to mancl - AT - alcatel-lucent.com.  The deadline for position papers is August 26.
The workshop is organized as a set of interactive brainstorming and discussion sessions.  The workshop participants will prepare a poster to present at the SPLASH poster session on Tuesday afternoon.

Workshop committee:

Position Papers

[Position papers will be posted on this website later...]


Extra material

Extra material (useful readings, links to books and articles on technical debt issues) will be posted here.


Last modified: May 16, 2014