Technical debt is used in the Agile world. In this post, I am going to provide a brief overview of this term as it is related to another important concept of Hardening Sprint.
What is Technical Debt?
Technical debt is a metaphor and was first coined by Ward Cunningham, one of the authors of the Agile Manifesto. It refers to the complexity of code that causes the changes to take more time/effort than required.
Martin Fowler, one of the authors of the Agile Manifesto, talks about Cruft. Most Software systems have internal deficiencies that make it harder to make changes or modify. Ward Cunningham used the financial metaphor to refer to it. The extra effort that it takes to add new features is the interest paid on the debt.
Code that is not quite right may include many types of issues. These issues may be related to architecture, structure, duplication, test coverage, comments, and documentation, potential bugs, complexity, code smell, coding practices, and style.
More details on Technical debt can be found in the Agile Alliance Article on Technical Debt.
Read Also: What is Sprint Zero and Spike?
About Techcanvass
Techcanvass offers the Agile Analysis Certification (AAC) Course, which focuses on applying an agile perspective within a business analysis framework and will strengthen your skills and expertise.
