🎁Oobeya June 2022 Updates
Check out the new features and improvements we've released for you.
Last updated
Check out the new features and improvements we've released for you.
Last updated
🎉 We are super excited to introduce you to our new features and improvements!
We have added Change Failure Rate to Oobeya Deployment Analytics [BETA]!
Change Failure Rate: The percentage of deployments causing a failure in production.
💡 Read more on Oobeya Blog: How to Measure DORA Metrics Accurately?
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.
Oobeya Deployment Analytics works with GitLab CI, AzureDevOps, Jenkins, and GitHub Actions for now.
Coming soon: Spinnaker, BB Pipelines, Octopus, PagerDuty, OpsGenie, ServiceNow, and more...
We have added the Time to Restore Service / Mean Time To Recovery (MTTR) metric to Oobeya Deployment Analytics [BETA]!
Time to Restore Service: How long it takes an organization to recover from a failure in production.
💡 Read more on Oobeya Blog: How to Measure DORA Metrics Accurately?
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.
[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
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 |
Do you want to see all the new features in action and talk about the product roadmap?
Click and book a demo now.
