Study guide
1.2 Work Tracking with Azure Boards & GitHub Projects
Microsoft Certified: Azure DevOps Engineer Expert AZ-400
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Flow of Work, Traceability & Work Tracking
1.1 Flow of Work, GitHub Flow & Feedback Cycles 1.2 Work Tracking with Azure Boards & GitHub Projects 1.3 End-to-End DevOps Traceability & Quality Tracking
2 Chapter 2: DevOps Metrics, Dashboards & Team Collaboration
2.1 DORA Metrics, Flow Metrics & Dashboard Design 2.2 Lifecycle Metrics Across the Six DevOps Phases 2.3 Work Item Queries, WIQL Charts & Analytics 2.4 Project Documentation: Wikis, Mermaid Diagrams & Release Notes 2.5 Webhooks, Service Hooks & Microsoft Teams ChatOps
3 Chapter 3: Git Branching Strategies & Pull Request Workflows
3.1 Git Branching Models & Strategy Design 3.2 Pull Request Workflows & Merge Strategies 3.3 Branch Policies, Quality Gates & Compliance Restrictions
4 Chapter 4: Repository Management, Optimization & Git Data Operations
4.1 Git LFS Architecture & .gitattributes Tracking 4.2 LFS History Migration, git-fat & File Locking 4.3 Git Repository Scaling, Scalar & Monorepo Governance 4.4 Repository Permissions & Git Tag Governance 4.5 Git Data Recovery & Sensitive-Data Scrubbing
5 Chapter 5: Package Management & Dependency Versioning
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages 5.2 Feed Scoping, Upstream Sources & Pipeline Authentication 5.3 Package Views, Immutability & Quality Promotion 5.4 Dependency Versioning: SemVer, CalVer & Automated Versioning 5.5 Pipeline Artifact Versioning & Artifact Storage Strategy
6 Chapter 6: Pipeline Infrastructure, Agents & Integration
6.1 Selecting a CI/CD Solution: Azure Pipelines vs. GitHub Actions 6.2 GitHub-Azure Pipelines Integration & Hybrid Migration 6.3 Hosted vs. Self-Hosted Agents & Runners 6.4 VMSS Elastic Pools, Container Jobs & Agent Governance 6.5 Pipeline Triggers, Filters & Concurrency Management
7 Chapter 7: YAML Pipeline Architecture & Reusable Elements
7.1 YAML Pipeline Anatomy: Stages, Jobs, Steps & Workspaces 7.2 Job Execution Order: DAG Dependencies, Parallelism & Conditions 7.3 Reusable Elements: Templates, Parameters & Variables 7.4 Variable Groups, Secret Variables & Key Vault Linking 7.5 YAML Environments, Checks & Deployment Approvals
8 Chapter 8: Testing Strategy, Quality Gates & Code Coverage
8.1 Test Strategy Design: Local, Unit & Integration Testing 8.2 Load, Stress & Performance Testing in Pipelines 8.3 Test Execution Tasks, Agents & Results Integration 8.4 Code Coverage Analysis & SonarQube Integration 8.5 Quality Gates, Release Gates & Governance Checks
9 Chapter 9: Modern Deployment Strategies & Zero-Downtime Delivery
9.1 Progressive Delivery: Blue-Green, Canary & Ring Deployments 9.2 Minimizing Downtime: Deployment Slots & Rolling Updates 9.3 Feature Flags with Azure App Configuration & Feature Manager 9.4 Designing the High-Priority Hotfix Path 9.5 Ordered Dependency Deployments, Resiliency & Rollback
10 Chapter 10: Artifact Deployment & Database DevOps
10.1 Containerized Application Delivery: ACR, AKS & Container Apps 10.2 Binary, Web App, Function & Scripted Deployments 10.3 Database DevOps: State-Based & Migration-Based Strategies
11 Chapter 11: Infrastructure as Code (IaC) & Azure Deployment Environments
11.1 Infrastructure as Code Strategy: Bicep, ARM & Terraform 11.2 Desired State Configuration & Azure Machine Configuration 11.3 Azure Deployment Environments (ADE) & Developer Self-Service
12 Chapter 12: Pipeline Maintenance, Health & Modernization
12.1 Pipeline Health, Flaky Tests & Reliability Engineering 12.2 Pipeline Optimization: Caching, Slicing & Concurrency 12.3 Artifact & Build Retention Governance 12.4 Modernizing CI/CD: Classic to YAML Migration
13 Chapter 13: Authentication, Authorization & Identity Governance
13.1 Microsoft Entra Service Principals & Managed Identities 13.2 Service Connections, Workload Identity & Personal Access Tokens 13.3 Azure DevOps Projects, Teams & Permission Evaluation 13.4 Access Levels, GitHub Roles & Outside Collaborators
14 Chapter 14: Secrets Management, Sensitive Data & DevSecOps Scanning
14.1 Azure Key Vault, Secret Variables & Secretless CI/CD 14.2 Security Scanning Strategy, GHAS & Secret Scanning 14.3 CodeQL SAST in Pipelines and Containers 14.4 Software Supply Chain, Container Scanning & Cloud Defender
15 Chapter 15: Telemetry Collection, Azure Monitor & Alerting
15.1 Azure Monitor Architecture, AMA & Data Collection Rules 15.2 Application Insights & Specialized Azure Monitor Insights 15.3 Alerting Rules, Action Groups & GitHub Repository Insights
16 Chapter 16: Telemetry Analysis, Distributed Tracing & SRE Practices
16.1 Distributed Tracing, Application Map & Exception Triage 16.2 KQL Log Analytics, SRE Observability & Error Budgets
1.2 Work Tracking with Azure Boards & GitHub Projects
Key Takeaways Explain This Topic AI
Azure Boards supports four standard process models: Basic (Issues/Tasks), Agile (User Stories/Points), Scrum (PBIs/Effort), and CMMI (formal Requirements/Change Requests).
Area Paths structure work by organizational, functional, or microservice boundaries, whereas Iteration Paths partition work into timeboxed execution cycles such as sprints.
GitHub Projects (v2) provides a flexible, relational work tracking interface featuring customizable Table, Board, and Roadmap views across multi-repository organizations.
Connecting GitHub Repositories to Azure Boards allows developers to link commits and pull requests by referencing AB#ID in commit messages and PR bodies.
Action verbs like 'Fixes AB#ID' or 'Closes AB#ID' automatically transition Azure Boards work items to Resolved or Done when the pull request merges into the default branch.
Last updated: September 2026
1.2 Work Tracking with Azure Boards & GitHub Projects
Enterprise DevOps solutions require tight alignment between high-level business goals, sprint execution, and low-level source code commits. In hybrid and Microsoft-centric ecosystems, organizations frequently operate across Azure Boards for comprehensive portfolio project management and GitHub Projects for developer-centric task orchestration. This section examines work tracking architectures, process selection, and cross-platform repository integration.
1. Azure Boards Core Architecture & Process Models
Azure Boards is built upon customizable work item tracking engines. A Process in Azure DevOps dictates the available Work Item Types (WITs), state progression rules, field definitions, and backlog hierarchies. [Epic] (Portfolio Level 2)
- │
- [Feature] (Portfolio Level 1)
- │
- ┌─────────────┴─────────────┐
- [Agile] [Scrum] [CMMI]
- [User Story] [Product Backlog Item] [Requirement]
- │ │ │
- ┌────┴────┐ ┌────┴────┐ ┌────┴────┐
- [Task] [Bug] [Task] [Bug] [Task] [Bug]
- The Four Standard Process Models
When creating an Azure DevOps Team Project, organizations select one of four default processes. Each process defines distinct terminology and state transitions:
Basic :
Target Audience : Small teams or startups seeking minimal process overhead without Agile ritual terminology.
Work Item Types : Epic → Issue → Task .
State Workflow : To Do → Doing → Done .
Characteristics : Bugs are tracked as Issues; does not include formal Story Points or User Story hierarchies.
Agile :
Target Audience : Teams practicing standard Agile/Scrum methodologies using user-centric requirements and point-based estimation.
Work Item Types : Epic → Feature → User Story → Task (and Bug ).
State Workflow : New → Active → Resolved → Closed .
Characteristics : Uses Story Points for requirement estimation. Includes a Resolved state that indicates code is complete and deployed to a test environment awaiting validation before being marked Closed .
Scrum :
Target Audience : Teams strictly adhering to the Scrum Guide terminology.
Work Item Types : Epic → Feature → Product Backlog Item (PBI) → Task (and Bug ).
State Workflow : New → Approved → Committed → Done (with an optional Removed state).
Characteristics : Uses Effort for PBI estimation. PBIs move directly from Committed to Done once the Definition of Done is met (there is no intermediate Resolved state). Includes dedicated Impediment tracking.
CMMI (Capability Maturity Model Integration) :
Target Audience : Heavily regulated enterprises (defense, aviation, medical) requiring rigorous audit trails, formal change approval, and traceability of engineering risks.
Work Item Types : Epic → Feature → Requirement → Task (along with Change Request , Review , and Risk ).
State Workflow : Proposed → Active → Resolved → Closed .
Characteristics : Tracks Size for estimations and requires formal root-cause analysis fields on defect records.
Custom and Inherited Processes
System processes (Basic, Agile, Scrum, CMMI) cannot be directly edited. To add custom fields (e.g., "Target Environment", "Cost Center"), create an Inherited Process in Organization Settings. Teams can configure custom business rules, such as making a field mandatory when an item transitions to Closed , or defining custom work item types.
2. Area Paths and Iteration Paths
Azure Boards separates organizational structure from scheduling using two hierarchical trees: Area Paths and Iteration Paths .
Area Paths: Logical and Team Boundaries (The "What" and "Who")
Area Paths group work items by business domain, product feature, functional component, or team ownership. They establish data isolation and team scoping.
- Hierarchy Example : FabrikamFiber
- ├── CorePlatform
- │ ├── Authentication
- │ └── DataLayer
- └── CustomerPortal
- ├── Billing
- └── Checkout
Team Scoping : Each team in Azure DevOps is mapped to a default Area Path. A team can be configured to include child area paths (e.g., CustomerPortal and all sub-areas) or restricted strictly to its leaf node. Area Paths also define security permissions, controlling which groups can create or modify work items within a module.
Iteration Paths: Temporal and Cadence Boundaries (The "When")
Iteration Paths organize work into explicit, non-overlapping timeboxes such as sprints, releases, or milestones.
- Hierarchy Example : FabrikamFiber
- ├── Release 2026
- │ ├── Sprint 1 (2026-09-01 to 2026-09-14)
- │ ├── Sprint 2 (2026-09-15 to 2026-09-28)
- │ └── Sprint 3 (2026-09-29 to 2026-10-12)
Sprint Planning & Metrics : Iterations require explicit StartDate and EndDate values. When a team activates an iteration, Azure Boards automatically calculates team capacity, burndown charts, and historical velocity.
3. GitHub Projects (Projects v2)
GitHub Projects represents GitHub's modern, spreadsheet-like work tracking system built on top of a GraphQL engine. Unlike legacy project boards, Projects v2 operates across entire organizations and aggregates issues and pull requests from multiple repositories.
Core Views
Table View : A high-density grid allowing engineers to slice, sort, group, and batch-edit issues, PRs, and draft items with keyboard shortcuts.
Board View : A traditional Kanban column visualization supporting custom swimlanes and card customizations.
Roadmap View : A Gantt-chart timeline based on custom Date fields or Iteration intervals, enabling portfolio managers to visualize project delivery schedules.
Custom Fields and Automations
GitHub Projects supports rich custom fields beyond native GitHub labels:
Iteration Fields : Allows configuration of sprint durations (e.g., 2-week rolling cycles) with automatic roll-forward.
Single Select & Number Fields : Track estimations (Story Points, T-shirt sizes, impact/effort ratios).
Built-in Workflow Automations : Event-driven rules that trigger based on item state:
Auto-add to project : Automatically add issues created with label area:core into the project.
Item status update : When an associated PR is opened, automatically move the issue from Todo to In Progress .
Auto-close : When an associated PR merges, transition the project card to Done .
4. Integrating Azure Boards with GitHub Repositories
Enterprise organizations often maintain their codebases in GitHub Enterprise while using Azure Boards for enterprise backlog tracking. Azure DevOps supports deep, bi-directional integration with GitHub.
Connection Architecture
Integration is configured under Project Settings → GitHub Connections in Azure DevOps:
Azure Boards App for GitHub : The recommended mechanism via GitHub Marketplace. It installs a GitHub App onto the target organization or select repositories, granting secure webhook communication without requiring personal access tokens (PATs).
OAuth / PAT Fallback : Direct authorization used when organization security policies prevent GitHub App installations.
Mention Syntax and Linking Mechanics
Once the connection is established, developers link commits, branches, and pull requests to Azure Boards work items using the AB# syntax: # Linking a commit to Azure Boards work item #4920
git commit -m "AB#4920 Implement OAuth2 token refresh interceptor"
- # Linking in a branch name
- git checkout -b feature/AB#4920-oauth-refresh
When Azure DevOps receives the GitHub push webhook, it automatically parses the commit message and creates a bi-directional hyperlink in the work item's Development control pointing directly to the GitHub commit URL.
Automatic State Transitions with Action Verbs
Developers can trigger state changes in Azure Boards work items directly from GitHub commit messages or pull request descriptions using recognized action verbs followed by the AB#ID tag:
- Action Syntax Agile State Transition Scrum State Transition Basic State Transition
- Fixes AB#4920 Active → Resolved Committed → Done Doing → Done
- Closes AB#4920 Active → Closed Committed → Done Doing → Done
- Resolves AB#4920 Active → Resolved Committed → Done Doing → Done
Important
Critical Exam Rule : Automatic state transitions do not take effect when the commit is pushed to a feature branch. The state transition triggers only when the commit is merged into the default branch (typically main ) via a pull request.
Managing Work Items via Azure CLI
DevOps engineers can automate Azure Boards work tracking directly from pipelines or terminal scripts using the azure-devops extension for the Azure CLI: # Create a new User Story under a specific Area and Iteration Path
- az boards work-item create \
- -title "Implement Stripe Webhook Consumer" \
- -type "User Story" \
- -area "FabrikamFiber\CustomerPortal\Billing" \
- -iteration "FabrikamFiber\Release 2026\Sprint 1" \
- -fields "Microsoft.VSTS.Scheduling.StoryPoints=5" "System.Description=Process charge.success events"
- # Update an item state to Active and assign it
- az boards work-item update \
- -id 4920 \
- -state "Active" \
- -assigned-to "ranchen@contoso.com"
- 5. Comparative Evaluation: Azure Boards vs. GitHub Projects
Capability Azure Boards GitHub Projects (v2)
Process Formalism Built-in formal models (Agile, Scrum, CMMI, Basic) Flexible, unstructured canvas tailored by custom fields
Work Item Hierarchy Rigid multi-level hierarchy (Epic → Feature → Requirement → Task) Flexible parent-child sub-issues and task lists
Query Engine Powerful Work Item Query Language (WIQL) with macro support ( @CurrentIteration , @Me ) Visual filter syntax ( is:open label:bug iteration:@current )
Capacity Planning Native team capacity by discipline (hours per day per engineer) Iteration field tracking without individual hourly capacity limits
Compliance & Audit Formal electronic signatures, field history audit, CMMI verification Commit and issue activity logs, timeline audit
Cross-Repo Scope Project-wide or cross-project within an organization Cross-repo across entire GitHub organization or enterprise
- 6. Realistic Exam Scenario & Common Traps
- Scenario: Configuring Multi-Team Enterprise Backlogs
Organization : Tailspin Toys has 3 autonomous engineering teams working out of 15 GitHub repositories. The leadership team uses Azure DevOps for portfolio management and sprint capacity planning. Each team operates on independent two-week sprint cadences, but all contribute to a shared microservice ecosystem.
Configuration Strategy :
Maintain a single Azure DevOps Team Project using the Scrum process.
Configure the Area Path tree reflecting team domains: Tailspin\SearchTeam , Tailspin\CatalogTeam , and Tailspin\CheckoutTeam .
Configure distinct Iteration Path trees for each team if their sprint start/end dates differ, or share a root iteration tree if their cadences align.
Install the Azure Boards App from GitHub Marketplace across all 15 GitHub repositories, linking them to the Azure DevOps Project.
Enforce branch policies in GitHub requiring developers to include AB#<ID> in pull request descriptions to guarantee that no pull request is merged without an associated, approved Product Backlog Item.