Technical debt is a well-known concept in Agile software development. Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. In this blog post, Steve Blank discusses the concept of organizational debt.
Technical debt is one of this great new metaphor that is applied to software development and more specially to agile project management approaches like Scrum. As its financial counterpart, technical debt is not necessary a bad thing as long as you are able to manage it wisely. In this article, Don Reinertsen will help you to put some numbers on the costs and benefits of your technical debt.
What do home ownership and leveraged buyouts can teach us about how to use technical debt to our advantage in Scrum? How can we sleep soundly at night when we have accumulated mountains and mountains of technical debt? When is good enough good enough and when are we just deceiving ourselves?
Technical debt due to bad code quality is one the problem that every Scrum development team might face in their application. In this blog post, Henrik Kniberg discusses the causes of technical debt and provides some hints on how to manage it.
Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. Sometimes you have to pay it if you want that you can continue to maintain your application. But sometimes it is better to leave the situation unchanged as Ken Rubin wrote in his book.
The metaphor of technical debt is widely used in software project management in general and especially Scrum. This article written by Philippe Kruchten, Robert L. Nord and Ipek Ozkaya try to put this concept in perspective, discussing how it has become somewhat diluted lately with its extension to other areas than code or its associations with tools like static code analyzers.
Technical debt a metaphor that refers to the eventual consequences of poor or evolving software architecture and software development within a codebase. The technical debt can be defined of as work that needs to be done to adapt a software to the best practices. In this blog post, Bastian Buch explains the step used in his organisation to reduce technical debt in an Agile way.
Scrum Expert Copyright © 2009-2024 Martinig & Associates