Oobeya Docs
  • GETTING STARTED
    • Welcome to Oobeya!
    • Get Started with Oobeya
    • Playground: Live Demo
    • Oobeya Quick Onboarding Guide
  • TEAM INSIGHTS & SYMPTOMS
    • Symptoms Catalog
      • S1- Recurring high rework rate
      • S2- Recurring high cognitive load
      • S3- High weekend activity
      • S4 - High Code Review Time
      • S6- High technical debt on Sonar
      • S7- High vulnerabilities on Sonar
      • S8- High code quality bugs on Sonar
      • S9 - Unreviewed Pull Requests
      • S10 - Lightning Pull Requests
      • S11 - Oversize Pull Requests
      • S12- High Lead Time For Changes (DORA)
      • S13- Low Deployment Frequency (DORA)
      • S14- High Change Failure Rate (DORA)
  • SECURITY
    • πŸ”Security at Oobeya
    • Oobeya Managed SaaS
  • INSTALLATION
    • 🐳Oobeya Docker Installation Tutorial & Requirements
    • 🐳Oobeya Version Upgrade For the docker-compose Installations
    • 🐳HTTPS Configuration For Docker Installations
  • PRODUCT DOCS
    • ⭐Oobeya Release Notes
      • 🎁Oobeya 2024 Q1 - Release Notes
      • 🎁Oobeya 2023 Q4 - Release Notes
      • 🎁Oobeya 2023 Q3 - Release Notes
      • 🎁Oobeya 2023 Q2 - Release Notes
      • 🎁Oobeya 2023 Q1 - Release Notes
      • 🎁Oobeya Nov & Dec '22 Updates
      • 🎁Oobeya September 2022 Updates
      • 🎁Oobeya August 2022 Updates
      • 🎁Oobeya July 2022 Updates
      • 🎁Oobeya June 2022 Updates
      • 🎁Oobeya Apr & May 2022 Updates
      • 🎁Oobeya March 2022 Updates
      • 🎁Oobeya Feb 2022 Updates
      • 🎁Oobeya Jan 2022 Updates
      • OOBEYA-2.0.8 - Release Notes
      • OOBEYA-2.0.4 - Release Notes
      • OOBEYA-2.0.0
      • OOBEYA-1.4.6
      • QAD-1.0 - 1.4
    • ▢️Product Tour
    • ❇️Metrics List
    • β˜€οΈDeveloper Experience Metrics
  • INTEGRATIONS
    • Integration Catalog
      • SCM & CI/CD Integrations
        • Azure DevOps Integration
        • Bitbucket Cloud Integration
        • Bitbucket Server Integration
        • GitHub Integration
        • Step-by-Step Integration Instructions for the Oobeya GitHub Application
        • GitLab Integration
        • Jenkins & Cloudbees Integration
        • Octopus Deploy Integration
        • TeamCity Integration
      • Quality & Security Integrations
        • SonarQube Integration
        • SonarQube Cloud Integration
        • Veracode Integration
      • Project Management Integrations
        • Jira Cloud Integration
        • Jira Server Integration
      • APM / Monitoring Integrations
        • AppDynamics Integration
        • Azure Application Insights Integration
        • Dynatrace Integration
        • Elastic APM Integration
        • New Relic Integration
        • Sentry Integration
    • Installing An Addon
    • Adding A New Data Source
    • Updating and Deleting Data Sources
  • ADMINISTRATION
    • User Management, Single Sign-On, Auth Settings
      • Microsoft Entra (Azure AD) Integration
      • LDAP / Active Directory Integration
      • Importing a New User From LDAP / Active Directory
      • Bulk User Import in Oobeya Using CSV
      • Adding a New User
      • Deactivating a User
      • Understanding Roles in Oobeya
    • License Management
      • Updating The License Key
  • DEVELOPMENT ANALYTICS - GITWISER
    • Git Analytics - Metric Definitions
      • Coding Impact Score
      • Impact Ratio (team-level)
    • Setting Up Development Analytics And DORA Metrics
    • Git Analytics Exclusions
    • Setting Automated Reanalyze For Gitwiser
    • Deployment Analytics (DORA Metrics)
    • Merging Contributor Accounts
  • DORA Metrics
    • DORA Metrics Introduction
      • Lead Time For Changes (LTC)
      • Deployment Frequency (DF)
      • Change Failure Rate (CFR)
      • Mean Time To Restore Service (MTTR)
    • Failure Detection (For Change Failure Rate & MTTR)
    • How To Calculate DORA Metrics for GitHub
    • Updating Team Scorecard configuration to display DORA Metrics
    • How To Start Deployment Analytics (DORA Metrics) For An Existing Gitwiser Analysis
  • Project Analytics - AgileSpace
    • Agile Analytics - Metric Definitions
    • Agile Board Analytics Intro
    • Starting an Agile Board Analytics
    • Board Overview
    • Sprint Reports
    • Update the Agile Board Analytics
  • QUALITY ANALYTICS
    • Total Code Quality Index (TCQI)
  • Guides
    • Azure DevOps Guides
      • How To Calculate DORA Metrics for Azure DevOps
      • Best practices for integrating Oobeya with Azure DevOps Scrum Boards
  • PROFILES
    • Introduction
    • Adding A Profile
    • Developer Scorecard
    • Adding A Related Account Information To Oobeya Profile
  • Team Health
    • Adding A Team
    • Team Scorecard
    • Project Analytics (Scrum Teams) Widget
  • Test Quality Report Widget
  • CUSTOM DASHBOARDS
    • Adding A New Dashboard
    • Adding A New Widget
    • Updating And Deleting Widgets
    • Adding Jira Sprint Progress Widget
    • Adding Jira Board Metrics Widget (Metrics With JQL)
  • SUPPORT
    • Support Request Workflow
    • Customer Success & Support Guide
Powered by GitBook
On this page
  • Initializing Oobeya Development Analytics In 6 Steps
  • Step 1: Repository
  • Step 2: CI/CD Flow
  • Step 3: Deployment
  • Step 4: Incident Detection
  • Step 5: Advanced Settings
  • Step 6: Finish
  • Notes
  • Tips for Efficiency

Was this helpful?

  1. DEVELOPMENT ANALYTICS - GITWISER

Setting Up Development Analytics And DORA Metrics

The objective of this document is to guide you through the process of setting up development analytics on Oobeya.

Oobeya Development Analytics (Gitwiser) module offers comprehensive insights into the development process, providing visibility into the coding, code review, and delivery cycles. Through Development Analytics, Oobeya analyzes all development activities, including commits, pull requests, and deployments, offering valuable insights. By leveraging Development Analytics, teams can identify bottlenecks, pinpoint problematic areas, and enhance engineering productivity and efficiency.

Initializing Oobeya Development Analytics In 6 Steps

  • Click the "Gitwiser" icon on the left sidebar. Then click the "New Analysis" button.

  • Select the Version Control System tool (Github, GitLab, Azure DevOps, Bitbucket, Gitea).

  • Follow the steps below to start analyzing the software development process historically:

Step 1: Repository

Select the data source, project, repository, and branch information. This step ensures accurate analysis of the coding repository including commits, pull requests, and metadata, enabling comprehensive insights into the development workflow.

Step 2: CI/CD Flow

Choose the CI/CD strategy that aligns with your development workflow. This step enables Oobeya to understand how software development processes are managed and integrated, enabling accurate tracking and analysis from code commit to deployment.

Step 3: Deployment

Provide details about your deployment pipeline, including environments, deployment process, and relevant tools. This information helps Oobeya to accurately track and analyze deployment activities, DORA Metrics, and their impact on software delivery performance.

Step 4: Incident Detection

Specify incident sources, such as incident management tools and hotfix branch naming conventions. This step is essential for enabling Oobeya to automatically detect, track, and accurately calculate DORA Metrics such as Change Failure Rate and Time to Restore Service.

Step 5: Advanced Settings

Fine-tune the analytics process by selecting related teams and defining the date range for analysis. Customize settings to focus on specific data and time frames relevant to your needs, enhancing the accuracy and relevance of the insights gained from the analytics process.

Step 6: Finish

Review and confirm the summary of selections and settings made in the previous steps. Click 'Finish' to start the analytics process and gain insights into your software development and delivery performance.


Once the analysis is completed, you can see the results on the Development Analytics page. Click on the repository name and navigate to the analytics result.


Notes

  • Make sure to select the correct Source Code Management tool and provide accurate details about your project's coding repository.

  • When choosing a CICD strategy, ensure it aligns with your delivery workflow to avoid inaccurate analytics and DORA Metrics.

  • Provide accurate details of your production deployment pipeline to ensure precise measurement of DORA Metrics.

  • Select the appropriate development practice (trunk-based or pull request based) for accurate metric calculation.

  • Integrate incident tracking tools and specify incident detection sources to accurately calculate the Change Failure Rate and Time to Restore Service metrics of DORA.

  • Use caution when fine-tuning settings, as incorrect configurations may lead to inaccurate analysis results.

Tips for Efficiency

  • Double-check the accuracy of the information you provide at each step to avoid errors.

  • Take advantage of tutorials and resources provided by Oobeya to maximize your use of the platform.

PreviousImpact Ratio (team-level)NextGit Analytics Exclusions

Last updated 12 months ago

Was this helpful?

Contact Oobeya via their website () if you have any questions or need further assistance.

oobeya.io