What’s New?

We’ve added Lead Time and Cycle Time views to the Delivery Report in the Project Analytics (Scrum Teams) widget, giving you a clear, sprint-by-sprint visualization of delivery performance.

📍 Navigate to: Team Scorecard > Project Analytics (Scrum Teams) > Delivery Report

What You’ll See:

• Cycle Time: Time from when work starts (in progress) to when it’s done.
• Lead Time: Time from when work is created to when it's completed.

• Both metrics are calculated per sprint, helping teams understand and improve how efficiently work moves through their system.
• Each line in the chart represents a board, showing how their delivery pace has evolved over the last 5, 10, or 20 sprints.

Why It Matters?

• Spot delivery slowdowns across teams and boards
• Track trends visually and identify outliers
• Enable data-driven targeted discussions on where to improve the delivery flow

Start tracking Lead Time and Cycle Time per sprint to gain deeper insight into how work flows through your teams and where it slows down.

What’s New?

We’re excited to introduce Quality Analytics [BETA], a brand-new module in Oobeya that brings deeper visibility into software quality by analyzing data from tools like SonarQube and SonarCloud.

With Quality Analytics, you get actionable insights into security vulnerabilities, code maintainability issues, technical debt, and custom quality metrics like Total Code Quality Index (TCQI) and Issue Risk.

Why We Built It

• We now store Sonar data historically in Oobeya’s database, enabling trend analysis and longitudinal reporting
• Quality data is mapped to individuals and team structures across different levels
• We’ve developed Oobeya-native quality metrics like Issue Risk and TCQI
• Quality data will be correlated with delivery, velocity, and productivity metrics, giving teams a more holistic view.

Why It Matters

• Track how code quality evolves over time
• Identify high-risk areas before they impact production
• Align engineering quality efforts with business and product goals
• Drive continuous improvement with team-level accountability.

What’s New?

Oobeya now supports automatic user removal when a user is removed from a synced Azure AD group.

Previously, users removed from Azure AD groups were only blocked from logging in. With this enhancement, their Oobeya accounts will be fully removed during the next sync cycle, just like in our LDAP integration.

Why It Matters?

• Ensures cleaner user management and reduces manual effort.
• Helps maintain security and access control compliance.
• Aligns Azure AD integration with existing enterprise-grade LDAP behaviors.

📌 This update is based on direct feedback from enterprise users—thank you for helping us improve!

What’s New?

Admins can now exclude specific work item types (e.g., subtasks, questions, or custom types) from AgileSpace metrics analysis to ensure more accurate, goal-oriented reporting.

📍 Location: Admin Settings > AgileSpace > Work Item Type Exclusion

• Supports both Azure Boards and Jira
• Includes a multi-select dropdown for choosing one or more work item types
• Starts with an empty exclusion list—nothing is excluded unless configured

Why It Matters?

• Keeps AgileSpace metrics focused on meaningful work
• Removes noise from subtasks, non-actionable items, or irrelevant custom types
• Helps teams align insights with productivity and workflow goals

This new exclusion setting will fine-tune your Agile analytics for clearer, more relevant metrics.

We’ve launched a powerful new Allocations tab in the Team Health module to help Product Owners, Agile Coaches, and Engineering Leaders track how team efforts are distributed across:

• Innovation (new feature development)
• Maintenance
• Bug Fixing

The first release introduces the Innovation Rate view, measuring the percentage of effort dedicated to innovation relative to total team effort.

📍 Where to Find It:

• View: Team Health > Scorecard > Project Analytics Widget > Allocations > Innovation Rate
• Settings: Administration > AgileSpace > Category Mapping Settings

Key Capabilities

Innovation Rate (%):

• Shows how much of the team's effort is spent on building new value.
• Tooltip includes full breakdown: Innovation Rate, Maintenance Rate, Bug Fix Rate, and Total Effort or Work Item Count.

Three Insightful Views:

1. Table View:
2. • Sprint-level breakdown of Innovation Rate by team (hierarchical: L5 to L2).
   • Predictability-style view with tooltips for detailed metrics.
3. Line Chart (Trend View):
4. • Track how the Innovation Rate evolves over multiple sprints.
   • Great for visualizing long-term focus and direction.
5. Stacked Bar Chart (Distribution View):
6. • See the full breakdown of work categories for a single team over time.
   • 100% bars segmented by work type:
     🟩 Innovation, 🟦 Maintenance, 🟥 Bug Fixing

Effort vs. Count Toggle:

• Switch between viewing by effort (e.g., story points) or item count.
• Smart validation ensures incompatible data (e.g., mixed units) is handled gracefully.

Drill-Down Navigation:

• Click any team or sprint to jump into detailed AgileSpace views for further exploration.

Why It Matters?

• Ensures strategic balance between innovation and ongoing maintenance.
• Helps leaders align resources with product growth goals.
• Provides transparency into how team efforts are spent over time.

To better align with our customers’ needs, we’ve expanded the predefined role options in Oobeya.

What’s New?

We’ve added two new predefined company roles:

• Agile Coach
• Tribe Lead

These roles are now available in the Oobeya company role list, making it easier to structure teams and assign responsibilities efficiently.

Why It Matters?

By introducing these predefined roles, we aim to align with modern agile structures and make role management smoother for teams adopting scaled agile methodologies.

2025-02-05 | Backend Version: 2.0.538 | Frontend Version: 2.0.395

What’s New?

We’ve introduced the Project Analytics (Scrum Teams) Widget, providing a comprehensive overview of team performance and key insights into delivery trends, work allocation, and backlog health.

This widget, now available under Team Health > Team Scorecard, helps Scrum teams track their efficiency and make data-driven decisions.

Why It Matters?

• Provides a centralized view of team sprint metrics in one place.
• Helps teams stay aligned with goals through clear delivery metrics.
• Enhances agility and planning with deeper insights.

Click and navigate to the documentation.

2025-01-08 | Backend Version: 2.0.522 | Frontend Version: 2.0.382