How do you explain technical debt?
Technical debt (also known as tech debt or code debt) describes what results when development teams take actions to expedite the delivery of a piece of functionality or a project which later needs to be refactored. In other words, it’s the result of prioritizing speedy delivery over perfect code.
How do you categorize technical debt?
The 3 main types of technical debt are: deliberate, accidental/outdated design, and bit rot. Just as smart financial debt can help you reach major life goals faster, not all technical debt is bad, and managing it well can yield tremendous benefits for your company.
Why do I have technical debt in my documentation?
Usually, technical debt in the documentation comes from coders simply moving too fast and taking shortcuts. But there are certain edge cases to look out for. For example, Programmer and CS Professor Chelsea Troy noted one “egregious case” of perfectionism that led to technical debt in the documentation.
When does a project incur technical debt?
These issues may be related to architecture, structure, duplication, test coverage, comments and documentation, potential bugs, complexity, code smells, coding practices and style. All these types of issues incur technical debt because they have a negative impact on productivity. Technical Debt may emerge during the life of a project.
What does technical debt mean in product management?
Product Management: Technical Debt. What is Technical Debt? Definition: Technical debt (also known as tech debt or code debt) describes what results when development teams take actions to expedite the delivery of a piece of functionality or a project which later need to be refactored.
Where did the concept of technical debt come from?
While people still disagree about the exact definition of technical debt, the core concept identifies a serious problem that many software teams are struggling to manage. Ward used it the first time when he was developing a financial application in Smalltalk.