> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/software-engineering-insights/use-software-engineering-insights/setup-sei/configure-integrations/azure-devops/sei-azure-devops-recommendations.md).

# Azure DevOps Use Cases

This page includes use cases for some of the most popular widgets used to measure developer metrics with the Azure DevOps integration.

### Key widgets <a href="#key-widgets" id="key-widgets"></a>

#### Measure Trellis Scores <a href="#measure-trellis-scores" id="measure-trellis-scores"></a>

[Trellis Scores](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md) are a proprietary productivity metric developed by SEI to provide a holistic view of team and individual performance in software development. These scores are derived from a combination of key performance factors, including [Code Quality](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#quality), [Code Volume](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#volume), [Speed](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#speed), [Impact](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#impact), [Proficiency](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#proficiency), and [Collaboration](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/sei-trellis-scores-overview.md#leadership-and-collaboration).

Using Azure Repos data, the Trellis widgets help measure essential metrics across these factors, such as Rework, Coding Days, Lines of Code, Cycle Time, and more. Follow the resources below to set up a Trellis profile and use the Trellis widgets for viewing insights into your engineering team’s performance.

* [Create Trellis profile](/software-engineering-insights/use-software-engineering-insights/setup-sei/sei-profiles/trellis-profile.md)
* [Trellis Score widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/trellis-score-reports.md#trellis-score-report)
* [Trellis Scores by Collection widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/trellis-score-reports.md#trellis-score-by-collection)
* [Individual Raw Stats widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/trellis-score-reports.md#individual-raw-stats)
* [Individual Raw Stats by Collection widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/trellis-scores/trellis-score-reports.md#raw-stats-by-collection)

#### Measure DORA <a href="#measure-dora" id="measure-dora"></a>

For teams working on DevOps, DORA metrics like Lead Time for Changes and Mean Time to Restore (MTTR) are important. If your team uses Azure Repos as the SCM or Azure Boards as the issue management the widgets below can help identify delays in delivery or recovery from issues.

* [Lead Time for Changes](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/dora-metrics/dora-metrics.md#lead-time-for-changes)
* [Mean Time to Restore](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/dora-metrics/dora-metrics.md#mean-time-to-restore-mttr)

#### Business alignment <a href="#business-alignment" id="business-alignment"></a>

A measure of how effectively engineering efforts contribute to strategic business outcomes, such as customer satisfaction, adoption, and operational efficiency. Use the Azure Boards integration to set up a Business Alignment profile within SEI, and use the Business Alignment widget to track key alignment metrics.

* [Create Business Alignment profile](/software-engineering-insights/use-software-engineering-insights/setup-sei/sei-profiles/business-alignment-profile.md)
* [Configure the Business Alignment widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/sei-business-alignment.md)

#### Sprint activity tracking <a href="#sprint-activity-tracking" id="sprint-activity-tracking"></a>

Use these widgets to measure crucial sprint metrics, like Velocity and Predictability, providing insight into how consistently teams deliver within a sprint.

* [Single Stats](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/agile-metrics/sei-sprints-metrics-reports.md#sprint-metrics-single-stat)
* [Trend Report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/agile-metrics/sei-sprints-metrics-reports.md#sprint-metrics-percentage-trend-report)

#### Track hygiene <a href="#track-hygiene" id="track-hygiene"></a>

Hygiene refers to how well the team manages and tracks ongoing work, which supports effective planning. Good hygiene practices reflect a team’s discipline in tracking issues, addressing backlogs, and planning future work. Use these widgets to pinpoint areas that need attention, identify process bottlenecks, and ensure work management practices align with the team’s goals.

* [Hygiene report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/hygiene-metrics.md)
* [Issues report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/issues-reports.md)
* [Issues Backlog Trend report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/issues-reports.md)
* [Issue Resolution Time report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/efficiency/issues-reports.md)

#### Developer contributions <a href="#developer-contributions" id="developer-contributions"></a>

Monitor individual contributions to understand how often developers are committing code and contributing to the codebase. These metrics can highlight engagement, focus areas, and workload distribution among team members. The following widgets are commonly used:

* [SCM Coding Days Report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-coding-days-report)
* [SCM Coding Days Single Stat](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-coding-days-report)

#### Pull request activity <a href="#pull-request-activity" id="pull-request-activity"></a>

Use SCM PR widgets to analyze the flow of PRs through your repositories, assess PR lead time, and understand team collaboration during reviews. These widgets help identify bottlenecks, improve efficiency, and ensure code quality through better collaboration.

* [SCM PRs Report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-prs-report)
* [SCM PR Lead Time by Stage Report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-pr-lead-time-by-stage-report)
* [SCM Review Collaboration Report](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-review-collaboration-report)

#### Code rework and quality <a href="#code-rework-and-quality" id="code-rework-and-quality"></a>

Understanding rework is essential to improving code quality and maintaining high standards in development. The [SCM Rework widget](/software-engineering-insights/use-software-engineering-insights/analytics-and-reporting/productivity/developer-insights.md#scm-rework-report) tracks rework volumes over time, helping teams identify which areas of code are more prone to revisions and need improvement.

{% hint style="info" %}
The Azure DevOps integration in Harness SEI supports numerous other widgets. For more recommendations or to explore additional reports, contact [Harness Support](/software-engineering-insights/troubleshooting-and-resources/sei-support.md) for guidance.
{% endhint %}