An Azure DevOps dashboard extension for sprint, flow and forecasts

What sits on the Azure DevOps dashboard

The Agile Analytics Azure DevOps dashboard is one connected view that ties together the four questions a delivery lead asks every week: is this sprint on track, how is flow trending, when are we likely to finish, and what is silently going wrong.

• Sprint health: commitment vs completed story points, burndown with the original commitment line, and a sprint summary that exposes scope additions instead of hiding them.
• Flow analytics: a cycle-time scatterplot with P50/P85 percentile lines, throughput by item type, and a Flow Efficiency view that splits active work time from queue time.
• Forecasting: a Monte Carlo simulation against your last six sprints of throughput, so you can give a confidence range for the next milestone rather than a single optimistic date.
• Operational early warnings: WIP monitoring, aging work, and blocked-item detection, which are the signals that usually surface in a retrospective a week too late.

Why a single Azure DevOps dashboard usually beats a Power BI rebuild

Most teams who arrive at this page have already considered building the same dashboard in Power BI. The trade-off comes down to time-to-first-chart and ongoing maintenance. A Power BI rebuild needs a dataset connector, a semantic model that mirrors your work-item types and states, DAX measures for cycle time and throughput, refresh schedules, and a workspace permission strategy, usually six to ten weeks before the first stakeholder sees a chart. The Azure DevOps dashboard in Agile Analytics ships those views pre-wired and rendered inside Azure DevOps, so the first chart is live in minutes after install. There is no separate workspace to log into, no exported dataset, and no publisher-hosted analytics backend; every chart reads your Boards data live through the standard Azure DevOps extension surface. When your process changes (new state, new team, new work-item type), the dashboard follows automatically because it joins on the same Azure DevOps schema your team already maintains.

Rolling the Azure DevOps dashboard out across multiple teams

Once one team has the dashboard pinned, the second and third teams are almost free to onboard. Every team inside the same Azure DevOps organisation inherits the same install, so there is no per-team setup, no per-team licence assignment, and no per-team data pipeline to wire up. Each team can scope the dashboard to its own area path, iteration, or filter set without affecting other teams, so the Scrum team and the Kanban team next door each see only their own work even though both use the same underlying extension. For organisations rolling the dashboard out beyond engineering (to a PMO, a delivery committee, or executive stakeholders), viewers need Basic access in Azure DevOps (the first five Basic users in an organisation are free), because Stakeholder access cannot read the work item data the dashboard is built from. Combined with one annual price per organisation, sized by assigned seats (Team 2, Business 6, Premium unlimited) rather than by how many people look at a pinned dashboard, this keeps cost predictable as adoption widens.