Azure Boards
What it is
Azure Boards is the Azure DevOps service for planning, tracking, and discussing work. It organizes work items—such as epics, features, user stories, tasks, and bugs—into backlogs, boards, sprints, queries, and delivery plans.
Why it exists
Delivery begins with a clear problem and a way to track its outcome. Boards connects a work item to branches, commits, pull requests, builds, and releases, giving the team evidence of how an idea moved toward production.
Key ideas
- Work items: record the requested outcome, acceptance criteria, ownership, state, discussion, and links. Item types depend on the selected process.
- Boards: visualize flow as cards moving through columns; useful for Kanban-style work.
- Backlogs and sprints: prioritize work and plan a time-boxed iteration.
- Queries, dashboards, and analytics: show selected work and trends. Metrics are conversation aids, not a substitute for user value or quality.
- Traceability: connect work to Azure Repos or GitHub branches, pull requests, builds, and releases.
Northwind example
Priya creates a work item for “customers can download an order receipt,” including the acceptance criterion that only the order owner may retrieve it. Luis links his pull request and pipeline run to that item. When the release reaches production, the work item provides a trail from the customer need to the reviewed code and deployment evidence. A board card moving to “Done” is a status claim; the team still verifies the feature works for users.
Exam notes
- Boards = work tracking; Repos = source; Pipelines = automation; Artifacts = package feeds.
- Linking work items to code changes improves traceability but does not automatically prove a requirement was met.
Related
github · pull-request · delivery-pipeline
Diagram
Diagrams courtesy of Microsoft Learn / Azure docs: azure/devops/boards/get-started/what-is-azure-boards
📘 Source: Microsoft Learn — What is Azure Boards?