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
  • Introduction
  • Requirements
  • Key Features
  • Widget Filters and Settings
  • Metric Definitions
  • Conclusion

Was this helpful?

  1. Team Health

Project Analytics (Scrum Teams) Widget

Let's learn about the Project Analytics (Scrum Teams) widget.

PreviousTeam ScorecardNextTest Quality Report Widget

Last updated 3 months ago

Was this helpful?

Introduction

The Project Analytics (Scrum Teams) widget on the team scorecard provides agile teams with in-depth insights into their performance and progress. Integrated seamlessly with Oobeya's AgileSpace module, gathering data from Jira or Azure Boards, this widget empowers teams to track sprint metrics, assess backlog health, and manage resource allocation effectively. It is designed to help stakeholders make informed, data-driven decisions to optimize team performance.


Requirements

To use the Project Analytics (Scrum Teams) widget effectively, the following requirements must be met:

  • Team Setup: A team must be created within Oobeya to enable data aggregation and analysis.

  • Agile Space Analysis: An Agile Space analysis must be set up and configured properly to retrieve relevant data from Jira or Azure Boards.

  • Analysis Association: The Agile Space analysis must be linked to the corresponding team for accurate reporting and tracking.

  • Team Scorecard Creation: A Team Scorecard must be created for the designated team to visualize and analyze the collected data effectively.

For detailed instructions on setting up teams and Agile Space analysis check out Team Health and Project Analytics - AgileSpace.


Key Features

Summary

This section provides a comprehensive high-level overview of metrics that represent team performance. It serves as the starting point for quick evaluation of key areas, enabling users to:

  • Monitor Sprint Metrics: Quickly view critical data such as completed sprints, velocity, cycle time, and predictability.

  • Assess Overall Productivity: Metrics such as productivity and predictability help assess how effectively the team distributes their efforts across delivering planned work and handling operational tasks. These metrics provide a clear picture of team efficiency and capacity to meet objectives.

  • Navigate Agile Boards: Board names are clickable links that redirect users to AgileSpace, offering deeper task-level details.


Delivery Report

The Delivery Report focuses on visualizing the team’s sprint performance over time. It helps users understand trends and evaluate areas for improvement:

  • Velocity Trends: Displays the average work completed across sprints, helping assess delivery capacity and consistency.

  • Predictability Insights: Shows the team's ability to plan and deliver accurately. The closer predictability is to 100%, the better the team is at meeting commitments.

  • Productivity Comparisons: Provides a breakdown of total completed work, including unplanned or pulled-in tasks, highlighting responsiveness and team efficiency.


Backlog Health

Backlog Health provides insights into the readiness and relevance of tasks waiting to be worked on. It ensures that the backlog is actionable and aligned with team priorities:

  • Backlog Age: Highlights the maximum time items have spent in the backlog, helping identify and address items at risk of becoming irrelevant.

  • Backlog Size: Reflects the number of uncompleted tasks in the backlog, excluding work in progress. This helps gauge whether the backlog is sufficient for upcoming sprints.

  • Bug Tracking: Helps teams keep track of unresolved bugs, ensuring they are addressed and managed efficiently.

  • Sprint Removals: Monitors the number of items removed from sprints. This ensures accountability and helps teams analyze why tasks were removed, whether due to reprioritization, blockers, or other factors affecting sprint execution.


Allocations

The Allocations tab highlights how team resources are distributed across different task categories. This breakdown supports balanced prioritization and sustainable growth:

  • Innovation Rate: Focuses on the percentage of resources dedicated to product growth through new features or enhancements, relative to operational tasks.

  • Effort Distribution: Displays how much effort is dedicated to bug fixes, maintenance, innovation, and uncategorized tasks.

  • Trend Analysis: Offers both bar and line chart visualizations to monitor how allocation trends evolve over time.


Widget Filters and Settings

Sprint Range

This widget offers flexibility in sprint analysis by allowing users to select specific sprint ranges, such as 'Last 5 Sprints,' 'Last 10 Sprints,' or 'Last 20 Sprints.' It does not rely on the global date filter, ensuring precise and tailored data insights.

Visualization Modes

  • Item Count vs Effort: Users can toggle between metrics based on item count or the estimated/actual effort.

  • Bar and Line Charts: The widget provides visual representations of metrics like innovation rate, predictability, and productivity across selected sprints, helping to identify trends and areas for improvement.

  • Downloadable Charts: Users can download bar and line charts as images for reporting and analysis.

  • Exportable Tables: All tables in the widget can be exported as Excel files for further data manipulation and record-keeping.


Metric Definitions

  • Board Name: Lists the names of the boards linked to the widget. Each board name is a clickable link to its corresponding AgileSpace board.

  • Completed Sprints: Number of sprints successfully started and completed by the team during the selected period.

  • Velocity per Sprint: Average work completed by the team in each sprint. Indicates the team’s delivery capacity.

  • Predictability: Calculated as (Completed Items / Planned Items) × 100%. Reflects how accurately the team estimates and delivers on their commitments. High predictability indicates reliable sprint planning and execution.

  • Productivity: Evaluates the team's total output relative to the initial plan, including both planned and extra work that was completed. It is calculated by adding the completed planned tasks and any additional tasks (pulled-in work) that were done, divided by the total planned tasks, and then multiplying by 100. This metric shows the team's overall capacity and responsiveness by including any additional work taken on beyond the original plan.

  • Avg Cycle Time: Average duration from when work starts on a task to when it is completed. Lower values indicate faster throughput. Useful for identifying bottlenecks in the workflow.

  • Avg Lead Time: Average duration from task creation to its completion. Reflects the total time taken to deliver work items. Helps in understanding the overall efficiency of the development process.

  • Backlog Age: The maximum time items have been in the backlog. Aged items may lose relevance.

  • Backlog Size: The number of uncompleted items in the backlog, excluding in-progress work items. Helps gauge workload readiness.

  • Innovation Rate: The percentage of the time, story points, or work items allocated to innovation (e.g., building new features) relative to the total effort (innovation + maintenance + bug fixes). A higher rate indicates a focus on driving product growth and competitiveness.


Conclusion

The Project Analytics (Scrum Teams) widget is a powerful tool that provides teams with actionable insights into their sprint performance, backlog health, and resource allocation. By leveraging key metrics, visual reports, and historical trends, teams can make informed decisions to optimize workflows, improve predictability, and enhance overall efficiency. The ability to export data and download charts further supports transparency and reporting needs. This widget is an essential component for agile teams striving to continuously improve and deliver value effectively.