Abstract is missing.
- Searching for build debt: experiences managing technical debt at GoogleJ. David Morgenthaler, Misha Gridnev, Raluca Sauciuc, Sanjay Bhansali. 1-6 [doi]
- Visualising architectural dependenciesJohn Brøndum, Liming Zhu. 7-14 [doi]
- Investigating the impact of code smells debt on quality code evaluationFrancesca Arcelli Fontana, Vincenzo Ferme, Stefano Spinelli. 15-22 [doi]
- Organizing the technical debt landscapeClemente Izurieta, Antonio Vetro, Nico Zazworka, Yuanfang Cai, Carolyn B. Seaman, Forrest Shull. 23-26 [doi]
- Technical debt aggregation in ecosystemsJohn D. McGregor, J. Yates Monteith, Jie Zhang. 27-30 [doi]
- The SQALE method for evaluating technical debtJean-Louis Letouzey. 31-36 [doi]
- What is the value of your software?Jelle de Groot, Ariadi Nugroho, Thomas Bäck, Joost Visser. 37-44 [doi]
- Using technical debt data in decision making: potential decision approachesCarolyn B. Seaman, Yuepu Guo, Clemente Izurieta, Yuanfang Cai, Nico Zazworka, Forrest Shull, Antonio Vetro. 45-48 [doi]
- Estimating the size, cost, and types of technical debtBill Curtis, Jay Sappidi, Alexandra Szynkarski. 49-53 [doi]
- Defining the decision factors for managing defects: a technical debt perspectiveWill Snipes, Brian P. Robinson, Yuepu Guo, Carolyn B. Seaman. 54-60 [doi]
- On the role of requirements in understanding and managing technical debtNeil A. Ernst. 61-64 [doi]