Azure DevOps for Scrum Masters: Boards, Work Items, and Sprint Reporting

Azure DevOps is the dominant project management tool in Microsoft-stack enterprises — banks, insurers, government digital services, and large consultancies. Yet almost no Scrum Master certification tests ADO knowledge. CREA-SM is the exception, dedicating substantial module coverage to real ADO skills. This guide covers what you need to know.

Azure DevOps vs Jira: When You Are Using ADO

If your organisation uses Microsoft Azure, .NET, or Microsoft 365 extensively, there is a strong chance delivery teams are on Azure DevOps rather than Jira. ADO is also dominant in UK public sector and defence. The Scrum Master who can configure and interpret ADO boards is significantly more valuable in these environments than one who knows only Jira.

Work Item Types in ADO Scrum

Azure DevOps uses a different hierarchy from Jira. In the Scrum process template:

• Epic — highest level, maps to a business objective or major initiative
• Feature — functional deliverable under an Epic, typically spanning multiple sprints
• Product Backlog Item (PBI) — equivalent to a Jira Story. This is the atomic delivery unit in ADO Scrum.
• Task — breakdown of work within a PBI, assigned to individuals
• Bug — defect item, can be tracked at PBI level or as a child task
• Impediment — ADO has a native Impediment work item type, which Jira does not. Use it.

Configuring the Sprint Board

The ADO Boards view is your primary facilitation tool. Five critical configuration steps every SM should know:

1. Column mapping — map board columns to your team's Definition of Done stages. ADO's default columns (Active, Resolved, Closed) are rarely sufficient. Customise to reflect your actual workflow.
2. WIP limits — ADO supports native WIP limits per column. Set these in Board Settings → Columns. When WIP is exceeded, the column header turns red — use this as a Daily Scrum conversation trigger.
3. Swimlanes — use swimlanes to separate expedited work, bugs, and tech debt from planned sprint work. Keeps the board readable at a glance.
4. Card colours — colour-code by work item type or by assigned person using Styles rules. Instant visual sprint status at a distance.
5. Definition of Done checklist — ADO allows you to add a checklist to card templates. Use this to embed your DoD directly into every PBI card.

Essential WIQL Queries for Scrum Masters

WIQL (Work Item Query Language) is ADO's equivalent of Jira's JQL. Five queries that cover 80% of SM needs:

• All open PBIs in current sprint: SELECT * FROM WorkItems WHERE [System.TeamProject] = @project AND [System.IterationPath] = @currentIteration AND [System.State] <> 'Closed'
• Impediments unresolved: SELECT * FROM WorkItems WHERE [System.WorkItemType] = 'Impediment' AND [System.State] <> 'Closed'
• Items not updated in 2+ days: SELECT * FROM WorkItems WHERE [System.State] = 'Active' AND [System.ChangedDate] < @today - 2
• Bugs created this sprint: SELECT * FROM WorkItems WHERE [System.WorkItemType] = 'Bug' AND [System.IterationPath] = @currentIteration
• Unassigned items in sprint: SELECT * FROM WorkItems WHERE [System.IterationPath] = @currentIteration AND [System.AssignedTo] = ''

Velocity and Burndown in ADO

ADO has built-in Velocity and Burndown charts under Analytics. The Velocity chart shows completed Story Points per sprint with a configurable rolling average — use this in Sprint Reviews and for capacity planning. The Burndown chart in ADO defaults to hours (task-level) rather than story points — switch to Story Points in the chart settings for a more meaningful sprint health view.

ADO's Delivery Plans view (under Boards → Delivery Plans) is a multi-team roadmap view not available natively in Jira. If your teams need cross-team dependency visibility, Delivery Plans is one of ADO's strongest differentiators.