Managing technical debt

Communications of the ACM

Volumn 55, Issue 5, 2012, Pages 50-55

  Allman, Eric ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

END OF LIVES; ENGINEERING BEST PRACTICE; WEB-BASED SERVICE;

COMPUTER APPLICATIONS; COMPUTER SCIENCE;

MAINTAINABILITY;

EID: 84861166931     PISSN: 00010782     EISSN: 15577317     Source Type: Journal    
DOI: 10.1145/2160718.2160733     Document Type: Article

References (6)

1. Brooks, F. The Mythical Man-Month, Anniversary Edition. Chapter 11. Addison-Wesley, Reading, PA, 1995.
2. Cunningham, W. The WyCash portfolio management system. OOPSLA 1992, Experience Report; http://c2.com/doc/oopsla92.html.
3. Fowler, M. Technical debt quadrant, 2009; http://martinfowler.com/bliki/ TechnicalDebtQuadrant.html.
4. Freeman, S. Bad code isn't technical debt, it's an unhedged call option. Higher-order Logic; http://www.higherorderlogic.com/2010/07/bad-code- isnttechnical-debt-its-an-unhedged-call-option/.
5. Grossman, S. Calmail crashes last multiple days. The Daily Californian (Dec. 1, 2011); http://www.dailycal. org/2011/12/01/calmail-crashes-last- multiple-days/.
6. McConnell, S. Technical Debt. Construx Conversations: Software Best Practices; http://blogs. construx.com/blogs/stevemcc/archive/2007/11/01/ technical-debt-2.aspx.