> For the complete documentation index, see [llms.txt](https://docs.oobeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s6-high-technical-debt-on-sonar.md). # S6- High technical debt on Sonar ### **Why is this a symptom?** This symptom refers to a high level of technical debt, as reported by the static code analysis tool Sonarqube/SonarCloud. Technical debt is a measure of the cost of maintaining a codebase, including the cost of fixing defects and adding new features. High technical debt can be an indication of poor coding practices, lack of attention to code quality, or lack of time dedicated to code maintenance. High technical debt can lead to increased maintenance costs, reduced code maintainability, and decreased ability to add new features in the future. It can also lead to decreased code quality, increased risk of defects and vulnerabilities, and a decrease in developer productivity. High technical debt can be considered a symptom of the development process, indicating that the team may need to focus on improving their coding practices, increasing time dedicated to code maintenance, and paying down the debt. {% hint style="info" %} **Level:** Team Level, System Level **Potential Complications:** #quality\_risk, #low\_productivity, #slow\_delivery, #low\_developer\_satisfaction {% endhint %} ### **Possible Causes** * Lack of attention to code quality * Pressure to meet deadlines * Lack of time dedicated to code maintenance * Use of poor coding practices * Lack of training or knowledge on good coding practices * Lack of established code review processes ### **Improvement Areas** * Increase the focus on code quality * Prioritize the reduction of technical debt * Incorporate code review and maintenance into the development process * Encourage collaboration and knowledge sharing on clean code * Encourage and facilitate refactoring within the team ### **Detection Method** Oobeya detects this symptom if the level of technical debt on Sonar for the selected period exceeds the specified threshold. **Formula:** (sonar\_technical\_debt) > (threshold) in the selected period **Example:** During each of the **last 3 months**, the team has consistently had **more than 180 minutes** of technical debt on Sonar. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s6-high-technical-debt-on-sonar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.