# TEAM INSIGHTS & SYMPTOMS - [Symptoms Catalog](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog.md): Oobeya helps software development organizations identify symptoms and areas for improvement in their development and delivery processes. - [S1- Recurring high rework rate](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s1-recurring-high-rework-rate.md): This symptom refers to a high rate of coding that needs to be redone or corrected. This could be due to a lack of clear requirements, inadequate testing, or a failure to follow established processes. - [S2- Recurring high cognitive load](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s2-recurring-high-cognitive-load.md): This symptom refers to a consistently high level of cognitive effort among team members. This could be due to a lack of resources, or a lack of knowledge-sharing culture and practices. - [S3- High weekend activity](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s3-high-weekend-activity.md): This symptom refers to a consistently high level of activity on weekends, indicating that team members are working outside of regular work hours. - [S4 - High Code Review Time](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s4-high-code-review-time.md): This symptom occurs when the review time of pull requests exceeds a predefined threshold, signaling potential inefficiencies in the code review process. - [S6- High technical debt on Sonar](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s6-high-technical-debt-on-sonar.md): This symptom refers to a high level of technical debt, as reported by the static code analysis tool Sonar. - [S7- High vulnerabilities on Sonar](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s7-high-vulnerabilities-on-sonar.md): This symptom refers to a high level of vulnerabilities as reported by the static code analysis tool Sonar. - [S8- High code quality bugs on Sonar](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s8-high-code-quality-bugs-on-sonar.md): This symptom refers to a high level of code quality bugs as reported by the static code analysis tool Sonar. - [S9 - Unreviewed Pull Requests](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s9-unreviewed-pull-requests.md): This symptom refers to a high number of pull requests that have not been reviewed by other team members. - [S10 - Lightning Pull Requests](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s10-lightning-pull-requests.md): This symptom refers to a high number of pull requests that are submitted and merged quickly, without adequate code review and testing. - [S11 - Oversize Pull Requests](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s11-oversize-pull-requests.md): This symptom refers to a high number of pull requests that are large in size and contain a lot of changes. - [S12- High Lead Time For Changes (DORA)](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s12-high-lead-time-for-changes-dora.md): This symptom refers to the significant amount of time it takes for code changes to progress from development to production. - [S13- Low Deployment Frequency (DORA)](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s13-low-deployment-frequency-dora.md): This symptom refers to a situation where software changes are not deployed to production frequently. It indicates a potential bottleneck or inefficiency in the deployment process. - [S14- High Change Failure Rate (DORA)](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s14-high-change-failure-rate-dora.md): This symptom refers to the percentage of deployments that result in failures or incidents in production. It can lead to customer dissatisfaction, decreased user trust, and increased operational costs. - [Engineering Benchmarks](https://docs.oobeya.io/team-insights-and-symptoms/engineering-benchmarks.md): Clear, standardized benchmarks that help engineering leaders assess performance, spot risks early, and drive continuous improvement across teams. --- # 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://docs.oobeya.io/team-insights-and-symptoms.md?ask= ``` 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.