Skip to main content

Azure DevOps portfolio reporting: a practical guide

Azure DevOps holds the work for many engineering organizations, but leaders rarely read it directly. This guide shows how to structure Azure Boards so a portfolio can be reported from it, what to put on one page for executives, and how to keep the reported status honest.

By the Tarivra team · · 7 min read

Structure the work so it can be reported

  • One item per program. Use an Epic, or a Feature for smaller programs, as the item a program's work rolls up to, with a Target Date and an owner.
  • Children under it. Every Feature, User Story or Product Backlog Item that belongs to the program sits under that item, so a Tree of Work Items query returns all of it.
  • States that mean something. Check that each process state maps to the right state category (Proposed, In Progress, Completed) in your process settings.
  • A way to mark blocked work. Use a Blocked field or a consistent tag, so blocked items can be counted.
  • Area paths per team, so the same report can be filtered by team or department.

The queries every program needs

Four queries per program, all built from Boards > Queries, give the numbers a status depends on:

Finished per week

How many child items reached a completed state in each of the last eight weeks?

How to check:
Parent = the program's Epic, State in your done states, Closed Date in the last 56 days, grouped by week.
Red flag:
A falling count three weeks in a row.

Work left

How many child items are still open?

How to check:
Same tree, State not in your done states. Divide by the weekly finish rate to get weeks of work left.
Red flag:
More weeks of work left than weeks to the Target Date.

Scope added

How much work was created after the program started?

How to check:
Same tree, Created Date after the program's start.
Red flag:
Scope up by a fifth or more with the Target Date unchanged.

Stuck work

What is blocked or untouched?

How to check:
Same tree, open items tagged blocked, or with Changed Date older than 14 days.
Red flag:
Stuck work above a quarter of what is open.

A one-page executive view

Executives need one row per program, not a board. For each program show:

  • The status the owner reports, and the status the four queries support.
  • The finish rate and the forecast finish against the Target Date.
  • Scope added and stuck work, as two numbers.
  • Open decisions from the last review, with owners and due dates.

Put the programs where the reported and supported status disagree at the top. Dashboards with Query Tile and Chart widgets can show most of this; Delivery Plans show the dates across teams.

Pitfalls specific to Azure DevOps

  • Progress rollup columns show completion, not whether the date will hold. Pair them with the forecast.
  • Different processes (Agile, Scrum, CMMI) name their done states differently; map them once and use the same mapping everywhere.
  • Work spread across several projects or organizations needs one query per project, or a reporting layer above them.
  • Teams that also use Jira or ServiceNow will be missing from an Azure DevOps-only view; link related items across tools so dependencies stay visible.

Where Tarivra fits

Tarivra produces this view automatically from Azure DevOps, and from Jira, ServiceNow, GitHub and GitLab where other teams work. It reads the items under each labeled program every 15 minutes, checks the reported status against them, and writes leadership decisions back to Azure Boards as work items.

Questions

Can Azure DevOps report a portfolio on its own?

Yes, with queries, dashboards and Delivery Plans. It takes some setup per program, and it covers only the work that lives in Azure DevOps.

Which work item should a program be?

Usually an Epic, or a Feature for a smaller program. What matters is that all of the program's work sits under that one item.

How do I forecast a date from Azure DevOps?

Divide the open child items by the number finished per week over the last six to eight weeks, and compare the result with the weeks left to the Target Date.