Sterling identifies five types of software debt: Technical Debt: a team or team members choose not to do well now and will impede future development if left undone Quality Debt: a diminishing ability to verify the functional and technical quality of software Configuration Management Debt: integration and release management become more risky, complex, and error-prone Design Debt: the cost of adding features is increasing toward the point where it is more than the cost of writing from scratch Platform Experience Debt: the availability of people to work on software changes is becoming limited or cost-prohibitive The scenario and accompanying formula is straightforward. Software debt is created when the project sponsor demands a timeline must be met instead of thinking through the ramifications of their choices
Establish a formula that calculates technical debt and transform it into a pictorial overview
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use