# Symptoms Catalog

### What Oobeya Offers

The Oobeya Symptoms module is a powerful tool for detecting and addressing problems in software development and delivery processes. By collecting and analyzing data from a variety of sources, the module is able to identify and alert teams to issues such as recurring anti-patterns, bad practices, and bottlenecks.

The Oobeya Symptoms module includes the following features:

* Identification of patterns and trends that may indicate problems or inefficiencies
* Alerts and recommendations for addressing detected issues

<figure><img src="/files/wf3gNVE7hyDB0p1lK4D9" alt=""><figcaption><p>Oobeya Team Health and Symptoms</p></figcaption></figure>

### Benefits

The Oobeya Symptoms module can help teams improve their software development and delivery processes in the following ways:

* By identifying and addressing issues that may be causing delays or inefficiencies, teams can improve their efficiency and productivity
* By providing alerts and recommendations for addressing detected problems, the module can help teams take proactive action to prevent future issues
* By generating reports at various levels, the module can help teams understand the root causes of problems and identify areas for improvement

### Available Symptoms (more coming soon)

The Oobeya Symptoms module currently includes the following symptoms:

<table><thead><tr><th width="99.33333333333331">No #</th><th>Smyptom</th><th>Symptom Source</th></tr></thead><tbody><tr><td>S1</td><td><a href="/pages/evk2uYbvNPrtPGokXDco">Recurring high rework rate</a></td><td>Gitwiser - Git Analytics (VCS tools)</td></tr><tr><td>S2</td><td><a href="/pages/PtI3HAQeJx95KJR9k0Qf">Recurring high cognitive load</a></td><td>Gitwiser - Git Analytics (VCS tools)</td></tr><tr><td>S3</td><td><a href="/pages/yjYcNA15KcDnxYsn6YQn">High weekend activity</a></td><td>Gitwiser - Git Analytics (VCS tools)</td></tr><tr><td>S4</td><td><a href="/pages/0ksUDDTUa8PJRRs1uzl9">High Code Review Time</a></td><td>Gitwiser - PR Analytics (VCS tools)</td></tr><tr><td>S6</td><td><a href="/pages/l5r71BRE6O00VrNK31RY">High technical debt on Sonar</a></td><td>Sonar</td></tr><tr><td>S7</td><td><a href="/pages/lWX2nKfUBLH057GdPmkD">High vulnerabilities on Sonar</a></td><td>Sonar</td></tr><tr><td>S8</td><td><a href="/pages/XRrxrdP6Xjg4D4W7cSCW">High code quality bugs on Sonar</a></td><td>Sonar</td></tr><tr><td>S9</td><td><a href="/pages/DDBvwWwnHT47cbGAXds6">Unreviewed Pull Requests</a></td><td>Gitwiser - PR Analytics (VCS tools)</td></tr><tr><td>S10</td><td><a href="/pages/4lxdm8tTClNnMKaZTlrW">Lightning Pull Requests</a></td><td>Gitwiser - PR Analytics (VCS tools)</td></tr><tr><td>S11</td><td><a href="/pages/JrUYeJXimamNsXif0kep">Oversize Pull Requests</a></td><td>Gitwiser - PR Analytics (VCS tools)</td></tr><tr><td>S12</td><td><a href="/pages/a9efLaIpMFEWx9ebn7Ji">High Lead Time For Changes (DORA)</a></td><td>Gitwiser - DORA Metrics (VCS + CICD + APM/IM tools)</td></tr><tr><td>S13</td><td><a href="/pages/P4uXxfhQgocw3hmFYzZy">Low Deployment Frequency (DORA)</a></td><td>Gitwiser - DORA Metrics (VCS + CICD + APM/IM tools)</td></tr><tr><td>S14</td><td><a href="/pages/Fka8Rn5dvWJQ3HvfZQTr">High Change Failure Rate (DORA)</a></td><td>Gitwiser - DORA Metrics (VCS + CICD + APM/IM tools)</td></tr></tbody></table>

### Symptom Catalog

Each symptom includes a description, potential complications, possible causes, improvement areas, and a detection method. By identifying and addressing these symptoms, teams can improve their software development and delivery processes and achieve better outcomes.


---

# 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/symptoms-catalog.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.