Links

Symptoms Catalog

Oobeya helps software development organizations identify symptoms and areas for improvement in their development and delivery processes.

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

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 (coming more soon)

The Oobeya Symptoms module currently includes the following symptoms:
  1. 1.
    Recurring high rework rate
  2. 2.
    Recurring high cognitive load
  3. 3.
    High weekend activity
  4. 4.
    High technical debt on Sonarqube
  5. 5.
    High vulnerabilities on Sonarqube
  6. 6.
    High code quality bugs on Sonarqube
  7. 7.
    Unreviewed Pull Requests
  8. 8.
    Lightning Pull Requests
  9. 9.
    Oversize Pull Requests
No #
Smyptom
Symptom Source
S1
Gitwiser - Git Analytics (VCS tools)
S2
Gitwiser - Git Analytics (VCS tools)
S3
Gitwiser - Git Analytics (VCS tools)
S6
Sonar
S7
Sonar
S8
Sonar
S9
Gitwiser - PR Analytics (VCS tools)
S10
Gitwiser - PR Analytics (VCS tools)
S11
Gitwiser - PR Analytics (VCS tools)

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.
​