OOBEYA-2.0.0

Oobeya 2.0 released with Git Analytics feature.

OOBEYA-2.0.0 🚀 - Git Analytics: Commit Work Type, Commit Impact, Scorecards Enhancements, and more...

🎉 We are excited to introduce major features under "Git Analytics" that strive to make your teams more productive. We have improved Gitwiser (our analyzer for Git repositories) to analyze coding activities deeper and to pinpoint bottlenecks in the software development process.

Oobeya 2.0 now provides you more metrics and insights to open the black-boxes of your engineering processes.

🆕 NEW FEATURES

Gitwiser Git Analytics - A deeper understanding of development activities.

We've added new features to Gitwiser -Oobeya's git repository analyzer. Gitwiser started to analyze all the commits data of repositories. Therefore, we are ready now to provide you more metrics and insights in Oobeya. We have enhanced both Individual and Team Scorecards with Git Analytics metrics.

After upgrading Oobeya, Git commits analysis will be performed in the first reanalyze process for your existing analyses.

Commit Work Type Analysis 🚥

Gitwiser analyzes all commits in the code repositories and identifies the work type of each coding activity. Work type analysis provides you more insight into the health of your development lifecycle.

See below the Git commit work types:

• 🆕New Work: Newly written code lines.
• 🛠️Refactor: Edits and updates made on the existing code (written more than 3 weeks old).
• 👩‍💻Help Others (Pairings): Edits and updates made on another developer's recent work (written less than 3 weeks old).
• 🔁Churn (Rework): Code that rewritten or deleted in a short time by the same developer after being written (less than 3 weeks).

Git commit work types & company average line

Git Analytics Metrics: Impact & Efficiency 🎯

Git Analytics offers you also two new metrics to pinpoint bottlenecks, risks, and workloads of your development lifecycle.

• Impact Score: A way of measuring the extent of code changes that occur. Impact Score allows us to find answers to these questions:

  • Approximately how much cognitive load did the engineer perform when implementing these changes?

  • What is the overall impact of these changes on the codebase?

• Efficiency: The percentage of productive work (which is not rework or code churn).

We believe organizations and teams need more than a single dimension or metric to get a deeper understanding of how they are working. Therefore, we calculate and provide commit impact and efficiency metrics at different levels:

• Commit-Level

• Repository-Level (upcoming)

• Individual-Level

• Team-Level

• Organization-Level (upcoming)

Scorecards - New Design And Enhancements ✨

We've received your feedback and made some major UI/UX enhancements on Individual and Team Scorecards. Now Scorecards have a more explicit view than before and it is easier to see trends on metrics.

Individual Scorecard with new metrics and design

Team Scorecard with new metrics and design

Gitwiser Analysis Exclusions ✂️

We've added a new exclusion field for Gitwiser analysis. We give you several options for configuring exactly what will be analyzed in Gitwiser. You can completely exclude some files or directories from Gitwiser analysis.

Example	Scope
**/*.xml	Excludes all xml files from Gitwiser analysis.
**/data.json	Excludes all data.json files from Gitwiser analysis.
**/*sample*/**	Excludes directories that include "sample" in their folder name.

You can set your exclusion patterns while starting a new analysis.

You can also update exclusion list later.

Gitwiser Analysis & Team Relation ⚙️

We've added a new field for selecting Team relation for Gitwiser analysis. This repo & branch selection will be added to your Team Scorecard configuration.

You can set team relation while starting a new analysis.

You can also update Team relation later.

Show Team Info On Gitwiser Main List ℹ️

We've just started to show related Team info on the Gitwiser main list.

Team info on Gitwiser main list

Merge Git Accounts Easily 🤩 With Developer Profiles

You can now easily merge related git accounts (emails, usernames...) with Profiles defined on Oobeya.

Merge related accounts with Oobeya users.

Before this feature, you should go to the Profile detail and open the "Update Profile" popup to add a new related git account.

The old & hard way of adding related account to a profile.