Which practice helps a team address technical debt and improve product quality?

Continuous refactoring is a practice that directly addresses technical debt and plays a crucial role in improving product quality. When teams engage in continuous refactoring, they regularly revisit and improve the existing codebase without altering its external behavior. This process allows for the elimination of outdated, inefficient, or overly complex code, making the system more maintainable and adaptable to future changes.

As technical debt accumulates over time, it can lead to increased costs, reduced speed of development, and lower overall product quality. By incorporating continuous refactoring into the team's workflow, developers ensure that the code remains clean, efficient, and easy to understand. This not only enhances the current functionality but also facilitates future enhancements, leading to better overall product quality.

While continuous integration and continuous delivery are also important practices in Agile development, they primarily focus on automating the integration and deployment processes rather than specifically addressing technical debt. Daily stand-ups, on the other hand, serve to enhance team communication and collaboration but do not directly impact code quality or technical debt management. Thus, continuous refactoring stands out as the most effective practice for tackling these issues.