# Oobeya June 2022 Updates
## Summary
:tada: We are super excited to introduce you to our new features and improvements!
* [x] DORA Stability Metrics -1: [Change Failure Rate](#dora-stability-metrics-1-change-failure-rate)
* [x] DORA Stability Metrics -2: [Time to Restore Service](#dora-stability-metrics-2-time-to-restore-service)
* [x] [Executive View & Organization-Wide Metrics](#executive-view-and-organization-wide-metrics)
* [x] [Improvements](#improvements) on AgileSpace, Gitwiser, Sonarqube, and UI/UX
* [x] Private Beta: [Symptoms ](#private-beta-cooking-something-special)(cooking something special...)
## 🎁 NEW FEATURES
### DORA Stability Metrics -1: Change Failure Rate
We have added Change Failure Rate to Oobeya Deployment Analytics \[BETA]!
{% hint style="info" %}
**Change Failure Rate:** The percentage of deployments causing a failure in production.
:bulb: Read more on Oobeya Blog: [How to Measure DORA Metrics Accurately?](https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/)
{% endhint %}
You can set your deployment status as a failure manually now.
In the next release, deployment failures will be detected automatically by **Git tags** and **branch names**.
Best tool to track DORA metrics: Why Oobeya Deployment Analytics?
* Proven Metrics ([DevOps Research & Assessment](https://www.devops-research.com/))
* Quick Start (Measuring DORA metrics [has never been easier](https://www.youtube.com/watch?v=EYE4e1gTs80))
* Cross-Platform Analysis (SCM x CI/CD x APM)
* Accurate Results :white\_check\_mark:
**Discover DORA Metrics** with Oobeya: [https://oobeya.io/dora-metrics](https://oobeya.io/dora-metrics/)
Read more on Oobeya Blog: [How to Measure DORA Metrics Accurately?](https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/)
{% hint style="info" %}
***Oobeya Deployment Analytics*** works with [GitLab CI](https://docs.oobeya.io/integrations/all-integrations/scm-addons/gitlab-addon), [AzureDevOps](https://docs.oobeya.io/integrations/all-integrations/scm-addons/azure-devops-integration), [Jenkins](https://docs.oobeya.io/integrations/all-integrations/scm-addons/jenkins-integration), and [GitHub Actions](https://docs.oobeya.io/integrations/all-integrations/scm-addons/github-integrations) for now.
Coming soon: *Spinnaker, BB Pipelines, Octopus, PagerDuty, OpsGenie, ServiceNow,* and more...
{% endhint %}
### DORA Stability Metrics -2: **Time to Restore Service**
We have added the Time to Restore Service / Mean Time To Recovery (MTTR) metric to Oobeya Deployment Analytics \[BETA]!
{% hint style="info" %}
**Time to Restore Service:** How long it takes an organization to recover from a failure in production.
:bulb: Read more on Oobeya Blog: [How to Measure DORA Metrics Accurately?](https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/)
{% endhint %}
### Executive View & Organization-Wide Metrics
You can set your own Organization Schema to create a hierarchical view in Oobeya.
After you create your organization chart, you can view your organization-wide metrics with breakdowns. All the metrics shown will be customizable in this view.
## :muscle: IMPROVEMENTS
* \[AgileSpace] Added Total Story Points & Total Issue Count value to Sprint Reports
* \[AgileSpace] Added a new tab to Sprint Velocity Metrics widget: "Team Members”
* \[AgileSpace] Added task dropdown to Scope Changes widget
* \[AgileSpace] Added a new configuration option for Azure DevOps Story Points / Effort fields
* \[Gitwiser] Added automated-reanalyze feature for Pull Request Analysis
* \[Sonarqube] Started hiding Sonarqube issues which are set as "won't fix" on Sonarqube
* Performance improvements
* UI/UX improvements
## :lock: **PRIVATE BETA - Cooking something special**
We are currently working on a new module called "**Symptoms**".
Oobeya ***Symptoms*** module identifies automatically symptoms of software development and delivery processes.
20+ symptoms are ready-to-use and auto-detect unhealthy practices of dev teams in private beta.
| Symptoms of software development and delivery processes | Tags |
| ------------------------------------------------------- | ------------------------------------------------ |
| Recurring high rework rate | low\_efficiency, slow\_delivery, dissatisfaction |
| Recurring high cognitive load | burnout\_risk, high\_workload, bad\_planning |
| High weekend activity | burnout\_risk, bad\_planning |
| High active coding days (%80+) | burnout\_risk |
| Work on X+ repos in a selected period | interruption, burnout\_risk |
| High technical debt on Sonarqube | quality\_risk, dissatisfaction |
| High vulnerabilities on Sonarqube | quality\_risk, security\_risk |
| High code quality bugs on Sonarqube | quality\_risk |
| Unreviewed Pull Requests | quality\_risk, unreviewed\_pr |
| Lightning Pull Requests | quality\_risk, unreviewed\_pr |
| Oversized Pull Requests | quality\_risk, bottleneck, large\_deploy\_risk |
| High Pull Request review time | slow\_delivery |
| Reviewer bottleneck % | slow\_delivery, bottleneck, high\_workload |
| High cycle time (tasks) | slow\_delivery, dissatisfaction, bottleneck |
| High lead time (tasks) | slow\_delivery |
| Low sprint planning accuracy | slow\_delivery, dissatisfaction |
| Low sprint delivery rate | low\_efficiency, slow\_delivery, dissatisfaction |
| Tasks in progress | burnout\_risk, high\_workload, bad\_planning |
| Recurring high scope changes | low\_efficiency, dissatisfaction, interruption |
| High Lead Time For Changes | slow\_delivery |
| High Deploy Duration | slow\_delivery |
| Low Deploy Frequency | slow\_delivery, large\_deploy\_risk |
## :person\_running: SEE OOBEYA IN ACTION!
{% hint style="info" %}
Do you want to see all the new features in action and talk about the product roadmap?
Click and [**book a demo**](https://oobeya.io/schedule-a-new-demo/?utm_source=releasenotes\&utm_medium=june2022) now.
{% endhint %}
---
# 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/product/release-notes/oobeya-june-2022-updates.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.