Starting an Agile Board Analysis
This guide explains how to initialize Project Analytics → Agile Board Analysis using an existing Agile data source.
Step 0 – Create a New Analysis
To start an Agile Board Analytics setup:
Open Analytics from the left-hand menu.
Navigate to Project Analytics.
Click New Analysis in the top-right corner.
This opens the Agile Board Analysis initialization wizard.
Step 1 – General Settings
In this step, you define the main context of the analysis.
Required fields
Data Source: Select one of the previously configured Agile data sources (e.g. Jira Cloud, Jira Data Center, Azure DevOps)
Board: Select the Agile board to analyze
Board Type: Scrum or Kanban
Optional fields
Area: For Azure DevOps boards, select one or more Areas. If no Area is selected, all Areas will be included in the calculations.
Product Owner: Select the responsible Product Owner
Scrum Master: Select the Scrum Master
Team(s): Associate one or more teams with this analysis
Analysis Date Range: Time period to analyze (default: Last 24 Months)
Click Next to continue.
Step 2 – State Mapping
Map workflow states to Oobeya’s standard flow categories. By default, Oobeya automatically maps states using the selected board’s workflow configuration.
Required mappings
To Do: States representing work that has not started (e.g. Backlog, To Do, Open, Analysis, Blocked)
In Progress: States representing active work (e.g. Development, Code Review)
Done: Final states (e.g. Done, Cancelled)
Additional settings
Method for Actual Reaction Time Defines when the reaction time calculation starts (e.g. From Work Item Creation Date).
Flow Efficiency – Active States Select the In Progress states that should be considered in Cycle Time and Flow Efficiency calculations. If no state is selected, all In Progress states will be included by default.
Click Next to continue.
Step 3 – Field Mapping
Configure how effort and sprint planning behavior are interpreted.
Required
Effort Field: Field used to calculate effort (commonly Story Points)
Optional
Ignore sprint scope changes made on planning day Excludes scope changes occurring on the sprint planning day.
Planning Days Number of days considered as sprint planning (default: 1).
Click Next to proceed.
Step 4 – Finish
Review the configuration and complete the setup. Once finished, Oobeya starts analyzing historical data for the selected board and date range.
Last updated