# Technical Debt

La Technical Debt *(ou dette technique)* est la différence entre ce qui est promis et ce qui a été implémenté *(bugs, implémentations temporaires, User Stories inachevées, ...)* ou autrement dit, les "todos" que l'on laisse traîner.

Il est donc important de mesurer la Technical Debt et de la réduire au maximum.

{% hint style="success" %}
En respectant la Definition of Done, la Technical Debt s'amoindrit.
{% endhint %}

{% hint style="warning" %}
Les **Technical Debts sont prioritaires**, autrement, ils ne feront que croître, l'équipe passera moins de temps sur les nouvelles User Stories et la vélocité diminuera.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide-agile.wishtack.io/scrum/mesures-et-outils/technical-debt.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.