What percentage of the sprint time do you allocate to technical debt?

The optimal percentage of time allocated to technical debt in a sprint depends on the team's and project's context, but it is generally recommended to allocate between 10% and 20% of the time.

Why is this important:

• It allows for gradual reduction of accumulated technical debt without blocking the development of new features.
• It helps maintain code and architecture quality, reducing the risks of bugs and scalability issues.

In practice, it is common to allocate 1-2 days out of a 10-day sprint for refactoring, dependency updates, testing improvements, and documentation.

If technical debt has accumulated significantly, it might be advisable to temporarily increase this percentage to prevent the situation from worsening.

In Go projects, where performance and stability are crucial, regularly dedicating time to technical debt helps keep the code clean and understandable.