Azure Boards – Work Item Management, Agile Planning & Tracking

1. What is Azure Boards?

Azure Boards is a project management and work-tracking service in Azure DevOps used to plan, organize, assign, and track software development activities.

It helps development teams manage requirements, user stories, tasks, bugs, and sprints throughout the Software Development Life Cycle (SDLC).

Azure Boards supports Agile methodologies such as Scrum and Kanban.

Simple example

Suppose your team is developing a Banking Application using ASP.NET Core Web API, Angular, and SQL Server.

The project includes:

• Customer Login

• Fund Transfer

• Account Balance

• Transaction History

Each feature requires development, testing, and bug fixing.

Using Azure Boards, the Project Manager or Scrum Master can create work items, assign them to developers, and monitor their progress.

Main purpose: Azure Boards helps teams understand what needs to be developed, who is responsible, and how much work has been completed.

2. Why do we need Azure Boards?

Without a work-tracking tool, development teams may face problems such as:

• Requirements are not properly documented.

• Developers are unclear about assigned tasks.

• Project managers cannot easily monitor progress.

• Bugs are not tracked systematically.

• Sprint planning becomes difficult.

• Teams cannot easily identify pending work.

Azure Boards provides a centralized system to manage these activities.

Advantages

3. Important Concepts in Azure Boards

Azure Boards uses Work Items to represent development activities.

A Work Item is a record that describes something the team needs to develop, investigate, test, or fix.

Common Work Item Types

Important: Available work item types depend on the selected Azure DevOps process, such as Agile, Scrum, Basic, or CMMI. For example, Agile uses User Stories, while Scrum uses Product Backlog Items.

Work Item Hierarchy

Consider the following example:

This hierarchy helps teams break large business requirements into manageable development tasks.

4. Main Features of Azure Boards

Azure Boards provides several features for planning and monitoring work.

A. Work Items

Work Items are used to record and track development activities.

A typical work item contains:

• Title: Name of the requirement or task.

• Description: Detailed explanation.

• Assigned To: Responsible team member.

• State: Current progress.

• Priority: Importance of the work.

• Iteration Path: Sprint or iteration.

• Area Path: Team or functional area.

• Parent/Child Links: Relationship with other work items.

Example:

Work Item ID : 105
Type         : Task
Title        : Develop Customer Login API
Assigned To  : Developer A
State        : Active
Priority     : 1
Iteration    : Sprint 1

The exact fields and states vary by work item type and process configuration.

B. Backlogs

A Backlog is a prioritized list of work that the team plans to complete.

Example:

The Product Owner typically prioritizes backlog items based on business requirements.

C. Kanban Boards

A Kanban Board visually represents work items and their progress.

As work progresses, team members move items between columns.

Kanban boards can be customized with additional columns, work-in-progress limits, and swimlanes.

D. Sprints

A Sprint is a fixed period during which a development team works on a selected set of backlog items.

Common sprint durations are 1, 2, or 4 weeks.

Example:

Sprint 1 – Two Weeks

Azure Boards provides sprint backlogs, taskboards, and capacity planning to monitor sprint progress.

E. Queries and Dashboards

Queries allow teams to search and filter work items based on conditions.

Examples:

• All active bugs.

• Tasks assigned to a specific developer.

• High-priority work items.

• Work items in the current sprint.

Dashboards display project information using widgets such as charts, query results, and sprint metrics.

These help Scrum Masters, Tech Leads, and Project Managers monitor project progress.

5. How Does Azure Boards Work in a Real Project?

Consider a requirement to implement Fund Transfer functionality.

Product Owner
      ↓
Creates Requirement
      ↓
Creates Epic / Feature / User Story
      ↓
Adds Items to Product Backlog
      ↓
Sprint Planning
      ↓
Assigns Tasks to Developers
      ↓
Developers Implement Code
      ↓
Update Work Item Status
      ↓
Code Review and Testing
      ↓
Fix Bugs if Required
      ↓
Mark Work as Completed

Step-by-step explanation

Step 1 – Requirement creation

Product Owner creates a User Story:

As a banking customer, I want to transfer money to another account so that I can make payments online.

Step 2 – Task breakdown

The development team creates tasks:

• Develop Fund Transfer Web API.

• Implement SQL Server transaction logic.

• Develop Angular UI.

• Write unit tests.

Step 3 – Assign tasks

The Scrum Master or team assigns tasks to developers during sprint planning.

Step 4 – Development

Developers implement functionality and update their work item status.

Step 5 – Integration with Azure Repos

Developers can link work items to commits and Pull Requests.

For example, a commit message can reference a work item:

git commit -m "Implemented Fund Transfer API AB#105"

When integrated with Azure Boards, AB#105 can associate the commit with work item 105.

Step 6 – Testing and completion

After code review and testing, the work item is moved to the appropriate completed state.

6. Azure Boards vs Azure Repos vs Azure Pipelines

These services work together:

Azure Boards
(Requirement / Task)
        ↓
Azure Repos
(Code / Pull Request)
        ↓
Azure Pipelines
(Build / Test / Deploy)
        ↓
Azure Boards
(Update Work Item Progress)

Work item status updates can be manual or automated through configured integrations and workflows.

7. Important Interview Questions and Answers

Q1. What is Azure Boards?

Azure Boards is an Azure DevOps service used to manage requirements, user stories, tasks, bugs, backlogs, and sprints using Agile methodologies.

Q2. What is a Work Item?

A Work Item represents a requirement, task, bug, or other development activity that needs to be tracked.

Q3. What is the difference between an Epic, Feature, User Story, and Task?

• Epic: Large business objective.

• Feature: Major functionality within an Epic.

• User Story: Specific user requirement.

• Task: Technical activity required to implement the requirement.

Q4. What is the difference between Backlog and Kanban Board?

A Backlog is a prioritized list of pending work. A Kanban Board visually displays work items and their current progress.

Q5. What is a Sprint in Azure Boards?

A Sprint is a time-boxed development iteration during which a team completes selected backlog items.

Q6. What is the difference between Area Path and Iteration Path?

Area Path identifies the team, product area, or functional ownership of a work item.

Iteration Path identifies the sprint or iteration in which the work is planned.

Q7. Can Azure Boards integrate with Git commits and Pull Requests?

Yes. Azure Boards can link work items to commits, branches, and Pull Requests in supported repository integrations, providing traceability between requirements and code changes.

Q8. Can we use Azure Boards without Azure Repos?

Yes. Azure Boards can be used independently for project and work tracking. Developers can use GitHub or other source control systems.

8. Key Points for Interview

• Azure Boards is used for Agile project planning and work tracking.

• Work Items represent requirements, tasks, bugs, and other activities.

• Epics, Features, User Stories, and Tasks organize development work.

• Backlogs maintain prioritized requirements.

• Kanban Boards visualize work progress.

• Sprints organize work into fixed development iterations.

• Queries and Dashboards help monitor progress.

• Azure Boards integrates with Azure Repos and Pipelines for development traceability.

Interview-ready answer

Azure Boards is a work-tracking and Agile project management service in Azure DevOps. It helps development teams manage requirements, user stories, tasks, bugs, backlogs, and sprints.

In a real project, the Product Owner creates requirements, the development team breaks them into tasks, and developers update their progress through Kanban boards or sprint taskboards. Azure Boards can also link work items with Git commits, Pull Requests, and builds.

This provides better visibility, team collaboration, and end-to-end traceability throughout the software development lifecycle.