Introduction
As a project team member, you are committed to delivering business value with quality and agility. EasyInsights is a platform that supports your efforts by providing standard project-level dashboards for informed decision-making and gives you a head start in the journey toward delivering customer outcomes and satisfaction.
EasyInsights currently supports projects using Azure DevOps Services (formerly VSTS) as the primary DevOps tool.
Indicators
| Indicator |
Description |
| Deployment Frequency |
Deployment Frequency in Azure DevOps (ADO) refers to the frequency of deployments made to an environment within a specific time frame. This metric serves as a crucial indicator of the team's agility and the maturity of the continuous delivery process. Teams with high deployment frequency often exhibit high performance and adhere to DevOps principles. |
| Deployment Failure |
Deployment failure rate is a key performance indicator (KPI) for delivery agility in the DORA report. The primary purpose of this metric is to help project teams understand the agility of their assembly lines in delivering value to their customers. |
| Average Cycle Time |
Cycle time measures the time it takes for a team to build functionality and put it in the hands of end users. It is an important part of understanding the team’s throughput and therefore how quickly they can deliver value. |
| WorkItem Health |
Work Item Health refers to the health index rating on the structure and content hygiene of work items (Requirements/Stories/PBI, Features, Tasks, Bugs, etc.) maintained on a daily basis. This metric is crucial for identifying work items that are not properly structured, ensuring hygiene in Azure DevOps (ADO). |
| Defect Ageing |
Defects Ageing is a breakdown of how the open defects are ageing. If teams aren’t able to properly manage bugs, the backlog of defects will continue to grow and could indicate a quality problem |
What is Deployment Frequency
Deployment Frequency in Azure DevOps (ADO) refers to the frequency of deployments made to an environment within a specific time frame. This metric serves as a crucial indicator of the team's agility and the maturity of the continuous delivery process. Teams with high deployment frequency often exhibit high performance and adhere to DevOps principles.
Understanding the output
Average no of Deployments
The average is calculated based on the total number of successful deployments divided by the number of days in the last selected rolling period.
Note: If the creation date of the pipeline is less than 6 months from the current date, the difference between the pipeline creation date and the current date will be considered.
|
Vertical Bar Chart
The bar chart, based on the selected pipeline and stages, shows the total number of successful deployments for the selected stages.
|
Release Pipeline Hyperlink
The hyperlink in the widget redirects the user to the Release Pipeline page, where all release pipelines are listed.
|
| Field Name |
Description |
| Title |
Text field to add custom name to the widget. |
| Size |
Size dropdown to resize the width and height of the widget in the dashboard. |
| Release Pipeline Dropdown |
Dropdown to select any one release pipeline - Classic or YAML both are supported. |
| Stages Dropdown |
Display environments or stages available within the release pipeline. |
| Color Picker |
Color picker to change the color of the release pipeline bar color, visible only after selecting the release pipeline. |
| Clear Custom Color |
Reset the release pipeline bar color to the default color. |
| Rolling period |
Select up to 6 months for visualization. Only working days will be considered for calculation |
What is Deployment Failure
Deployment failure rate is a key performance indicator (KPI) for delivery agility in the DORA report. The primary purpose of this metric is to help project teams understand the agility of their assembly lines in delivering value to their customers.
Understanding the output
Average no of Deployments
The average is calculated based on the total number of failed deployments divided by the number of days in the last 6 months.
Note: If the creation date of the pipeline is less than 6 months from the current date, the difference between the pipeline creation date and the current date will be considered.
|
Vertical Bar Chart
The bar chart, based on the selected pipeline and stages, shows the total number of failed deployments for the selected stages.
|
Release Pipeline Hyperlink
The hyperlink in the widget redirects the user to the Release Pipeline page, where all release pipelines are listed.
|
| Field Name |
Description |
| Title |
Text field to add custom name to the widget. |
| Size |
Size dropdown to resize the width and height of the widget in the dashboard. |
| Release Pipeline Dropdown |
Dropdown to select any one release pipeline - Classic or YAML both are supported. |
| Stages Dropdown |
Display environments or stages available within the release pipeline. |
| Color Picker |
Color picker to change the color of the release pipeline bar color, visible only after selecting the release pipeline. |
| Clear Custom Color |
Reset the release pipeline bar color to the default color. |
| Rolling period |
Select up to 6 months for visualization. Only working days will be considered for calculation |
| Clarity |
Help us understand how the metric is being utilized by enabling the user behavior analytics tool
Clarity.
Clarity is safe to use and does not collect or store any Personally Identifiable Information (PII) or sensitive data.
|
What is Average Cycle Time
Cycle time measures the time it takes for a team to build functionality and put it in the hands of end users. It is an important part of understanding the team’s throughput and therefore how quickly they can deliver value.
Understanding the output
Total Count of the Work Items
Clicking on the work Item Type hyperlink redirects to a custom query, displaying the list of all work items in a closed state.
Note: For the current/running month, the workitems closed from the first day of the calendar month till today is included in the metric calculation.
|
Vertical Bar Chart
The bar chart displays the average of the work items based on the selected feature teams and work item type.
|
Average Cycle time per day
The average is calculated as the time difference between the work item's activated date and closed date, divided by the total number of work items.
|
Forecast Bar Chart
The forecast bar appears next to the current month, with forecast values displayed in a lighter shade than the actual bars. Forecast bars will be shown when the rolling period exceeds 1 month.
|
| Field Name |
Description |
| Title |
Text field to add custom name to the widget. |
| Size |
Size dropdown to resize the width and height of the widget in the dashboard. |
| Feature Teams |
Dropdown to select the feature teams available in the project |
| Work Item Type |
Dropdown to select the Work Item type in the project. |
| Rolling period |
Select up to 6 months for visualization. Only working days will be considered for calculation |
| Clarity |
Help us understand how the metric is being utilized by enabling the user behavior analytics tool
Clarity.
Clarity is safe to use and does not collect or store any Personally Identifiable Information (PII) or sensitive data.
|
Work Item Health
Work Item Health refers to the health index rating on the structure and content hygiene of work items (Requirements/Stories/PBI, Features, Tasks, Bugs, etc.) maintained on a daily basis. This metric is crucial for identifying work items that are not properly structured, ensuring hygiene in Azure DevOps (ADO).
| Field Name |
Description |
| Title |
Text field to add a custom name to the widget. |
| Select Health Rules |
Dropdown to select multiple rules based on which the rating will be calculated. Queries have to be added in the shared query -> EasyInsights Work Item Health folder. Any query returning values will be considered as an unsatisfied rule.
Example: User Story without Parent |
| Clarity |
Help us understand how the metric is being utilized by enabling the user behavior analytics tool
Clarity.
Clarity is safe to use and does not collect or store any Personally Identifiable Information (PII) or sensitive data.
|
Defect Ageing
Defect Ageing is a breakdown of how the open defects are ageing. If teams aren’t able to properly manage bugs, the backlog of defects will continue to grow and could indicate a quality problem.
| Field Name |
Description |
| Title |
Text field to add a custom name to the widget. |
| Feature Teams |
Dropdown to select the feature teams available in the project. |
| Severity |
Dropdown to filter out bugs based on the Severity field. |
| Priority |
Dropdown to filter out bugs based on the Priority field. |
| Include Resolved Bugs |
Option to include resolved bugs as part of the ageing calculation. If resolved is your closed state, uncheck the field. |
| Rolling Period |
Select up to 6 months for visualization. Only working days will be considered for calculation. |
| Clarity |
Help us understand how the metric is being utilized by enabling the user behavior analytics tool
Clarity.
Clarity is safe to use and does not collect or store any Personally Identifiable Information (PII) or sensitive data.
|
Frontend libraries
- "@fluentui/react-charting": "^5.21.18",
- "azure-devops-extension-api": "^4.234.0",
- "azure-devops-extension-sdk": "^3.1.2",
- "azure-devops-ui": "^2.167.63",
- "react": "~16.13.1",
- "react-color": "^2.19.3",
- "react-dom": "~16.13.1"
Having a question?
Use Q & A section to post your question and report any bug.
