Choosing "quick and dirty" without a plan to fix it; this leads to long-term project failure.
Debt caused by a lack of skills or following poor practices without realizing it. Technical Debt Management in the Context of Agi...
We know we are taking a shortcut to meet a market window and plan to fix it immediately after. Choosing "quick and dirty" without a plan to
Explicitly track technical debt items as "Technical Stories" in the product backlog. This makes the invisible cost of development visible to stakeholders and product owners. Explicitly track technical debt items as "Technical Stories"
Discovering a better way to have designed something only after it has been built ("Now we know how we should have done it").
Measures how difficult code is to maintain or change.
Integrate quality standards—such as minimum test coverage, peer reviews, and documentation—into the team's Definition of Done to prevent new debt from entering the system.