Gartner Research

Best Practices in Agile Development: Managing Technical Debt

Published: 18 January 2012

ID: G00229397

Analyst(s): Nathan Wilson


Technical debt comprises all elements of a software solution that make it difficult to operate, support, maintain, enhance and extend. This research discusses the causes of technical debt, and how to track and reduce technical debt in an agile organization.

Table Of Contents
  • Overview


  • Sustainable Agile Code
  • What Is Technical Debt?
  • Types of Technical Debt
    • Design Debt
    • Documentation Debt
    • Code Debt
  • Causes of Technical Debt
  • Avoiding Technical Debt
  • Managing Technical Debt
    • Tracking Debt
    • Software Metrics
    • Schedule Work to Fix Technical Debt
    • Debt With Operational Impact
    • Other Debt
    • Fix Windows

Recommended Reading

©2021 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact. While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or influence from any third party. For further information, see Guiding Principles on Independence and Objectivity.

Already have a Gartner Account?

Become a client

Learn how to access this content as a Gartner client.