Back to Blog
BlogArticle
DevOpsAzure DevOpsBoardsAgilework trackingScrumKanbansprint planningDevOps

Azure DevOps Boards: Hướng Dẫn Work Tracking & Agile 2026

Hướng dẫn Azure DevOps Boards: work items, sprints, Kanban/Scrum boards, queries, dashboards. Agile project management cho dev teams Việt Nam.

P
PUPAM Tech Team
Content Writer
Updated: 2026-02-28
18 phút min read
NaN words

Hướng Dẫn Azure DevOps Boards: Work Tracking & Agile Project Management Toàn Diện

Azure DevOps Boards Work Tracking và Agile Management Hình 1: Tổng quan Azure DevOps Boards — từ work item hierarchy đến Kanban/Scrum boards và dashboards.

Azure DevOps Boards = work tracking tool cho software teams — quản lý Epics, Features, User Stories, Tasks, Bugs theo Agile/Scrum/Kanban. Tích hợp end-to-end với Azure Repos (code), Azure Pipelines (CI/CD), Azure Test Plans (testing). Auth qua Microsoft Entra ID (SSO với Microsoft 365), permissions qua RBAC, audit qua Microsoft Purview compliance.

Admin quản lý organization settings, process templates, team configurations qua Azure DevOps portal (dev.azure.com). Bài viết hướng dẫn chi tiết từ work item hierarchy đến dashboard analytics cho dev teams Việt Nam.

TL;DR: Azure DevOps Boards quản lý Agile work tracking end-to-end — Epic → Feature → Story → Task. Hỗ trợ đồng thời Kanban board (continuous flow) + Sprint board (time-boxed). Free cho ≤5 Basic users + unlimited stakeholders. Native integration với Azure Repos, Pipelines, Test Plans — traceability từ requirement đến deployment. SSO qua Microsoft Entra ID, audit qua Microsoft Purview.

🚀 PUPAM triển khai Azure DevOps Boards cho dev teams Việt Nam — thiết kế workflow, sprint planning, dashboard, GitHub integration trong 1 tuần. Liên hệ tư vấn miễn phí


Work Item Hierarchy

LevelWork ItemPurposeTimeframe
PortfolioEpicLarge initiative, themeQuarters/Year
PortfolioFeatureDeliverable functionalitySprint(s)/Month
RequirementUser StoryEnd-user requirement1 Sprint
RequirementBugDefect to fix1 Sprint
TaskTaskDeveloper work unitHours/Days

Ví Dụ Hierarchy (E-commerce Project)

Epic: "Online Payment System" (Q1–Q2 2026)

  • Feature: "Credit Card Processing"
    • User Story: "As a customer, I can pay with Visa/MC"
      • Task: Design payment form UI
      • Task: Integrate Stripe API
      • Task: Write unit tests
      • Task: Security review
    • User Story: "As a customer, I get email receipt"
      • Task: Create email template
      • Task: Integrate SendGrid
    • Bug: "Payment fails on Safari mobile"
      • Task: Reproduce issue
      • Task: Fix CSS viewport
  • Feature: "E-Wallet Integration"
    • User Story: "As a customer, I can pay with MoMo"
    • User Story: "As a customer, I can pay with ZaloPay"
  • Feature: "Payment Analytics Dashboard"
    • User Story: "As admin, I see daily revenue"

Best Practices

  • Epics: 3–6 per quarter (strategic goals)
  • Features: 3–8 per Epic
  • User Stories: follow INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable)
  • Tasks: 2–8 hours mỗi task (không bao giờ > 1 day)

Process Templates

TemplateWork ItemsBest ForMethodology
AgileEpic, Feature, User Story, Task, BugMost teamsGeneral Agile
ScrumEpic, Feature, PBI, Task, Bug, ImpedimentScrum teamsScrum framework
CMMIEpic, Feature, Requirement, Task, Bug, ReviewRegulated industriesFormal process
BasicEpic, Issue, TaskSmall teamsMinimal overhead
  • User Stories với Story Points
  • Flexible workflow states
  • Activity-based capacity planning
  • Best for: startup, product teams

Scrum

  • Product Backlog Items (PBI) với Effort
  • Sprint commitment (Sprint Backlog) + Impediment tracking
  • Best for: certified Scrum teams

CMMI

  • Requirements với formal approval + change request tracking
  • Review/audit trail
  • Best for: government, healthcare, defense

Basic

  • Issues (simple) — no ceremony
  • Best for: small teams, open-source, quick projects

Đổi process: Organization Settings → Process → Change. Agile ↔ Scrum: seamless migration. Custom process: inherit from base template → add custom fields/states.


Boards (Kanban)

Cấu Hình Columns

Cấu HìnhDefaultRecommended
ColumnsNew → Active → Resolved → ClosedBacklog → Ready → In Progress → In Review → Testing → Done
WIP limitsKhông cóIn Progress = 3 (per person)
Split columnsKhôngDoing | Done (within "In Progress")
Definition of DoneKhôngChecklist per column

Swimlanes

  • Expedite (top): urgent items (P0/P1)
  • Default: normal work
  • Blocked: items waiting on external dependency

Card Customization

  • Show: Assigned to, Story Points, Tags
  • Color rules: Bug = red, Story = blue, Task = green
  • Annotations: show child tasks count, test status
  • Filters: by iteration (sprint), assigned to, tag, parent (Feature/Epic)

Cumulative Flow Diagram (CFD)

  • Boards → Analytics → CFD — shows work distribution across columns over time
  • Healthy: parallel bands (steady flow)
  • Unhealthy: widening bands (bottleneck) → cần address ngay

Sprints (Scrum)

Sprint PhaseActivitiesDuration
PlanningSelect PBIs, estimate, create tasks2–4 hours
Daily StandupYesterday/Today/Blockers15 min
Sprint WorkDevelopment, testing, reviews1–4 weeks
ReviewDemo to stakeholders1–2 hours
RetrospectiveWhat went well/improve1 hour

Sprint Setup

  1. Project Settings → Team configuration → Iterations
  2. + New iteration: "Sprint 1" (2 weeks) — Start: March 4, End: March 15
  3. Add child iterations: Sprint 2, Sprint 3...
  4. Team → select iterations this team works on

Sprint Planning

  1. Backlogs → right-click item → "Move to iteration" → Sprint 1
  2. Hoặc: drag-drop trên Sprint planning pane
  3. Set capacity: Team → Capacity → Hours/day per person
  4. Sprint burns down automatically

Burndown Chart

  • Sprints → Analytics → Sprint Burndown
  • Ideal line: linear từ total xuống 0
  • Actual line: should follow ideal closely
  • Above ideal = behind schedule, below ideal = ahead of schedule

Velocity

  • Analytics → Velocity → shows story points per sprint
  • Average velocity = predictable sprint capacity
  • Dùng cho: sprint planning, release forecasting

💡 Cần hỗ trợ thiết kế Azure DevOps Boards workflow? PUPAM tư vấn sprint planning, Kanban setup, dashboard analytics — tối ưu Agile process cho dev teams. Tìm hiểu thêm


Backlogs & Prioritization

Product Backlog

  • Tất cả user stories/PBIs theo priority order
  • Stack rank: drag to reorder — top = highest priority = next sprint
  • Bottom = future consideration

Backlog Levels

LevelViewMục Đích
Level 1EpicsStrategic view
Level 2FeaturesRelease planning
Level 3Stories/PBIsSprint planning

Prioritization Techniques

  • MoSCoW: Must, Should, Could, Won't
  • RICE: Reach × Impact × Confidence / Effort
  • Story mapping: horizontal (user flow) × vertical (priority)
  • Value vs Effort matrix (2×2 grid)

Refinement

  • Weekly grooming session (1 hour) — review top 2 sprints worth of items
  • Add acceptance criteria
  • Estimate story points (Fibonacci: 1, 2, 3, 5, 8, 13)
  • Split large stories (> 8 points)

Forecasting

  • Backlogs → Forecast → toggle ON
  • Shows sprint boundaries based on velocity
  • Ví dụ: "Feature X will be done in Sprint 5"

Queries & Charts

Query TypeDescriptionVí Dụ
Flat listSimple filterAll bugs assigned to me
Work item and direct linksParent-child relationshipsFeatures and their stories
TreeFull hierarchyEpic → Feature → Story → Task

Queries Hữu Ích

QueryĐiều KiệnMục Đích
My active itemsAssigned to = @Me, State = Active OR In ProgressXem việc đang làm
Sprint bugsType = Bug, Iteration = @CurrentIteration, State ≠ ClosedTrack bugs trong sprint
Stale itemsChanged Date < @Today - 30, State ≠ ClosedBacklog cleanup
Unestimated storiesType = User Story, Story Points = emptyCần estimate

Query Charts

  • Queries → query → Charts → + New Chart
  • Pie chart: bugs by severity
  • Bar chart: stories by state
  • Trend chart: bugs over time (opened vs closed)
  • Pin charts to dashboard

Dashboards

WidgetMô TảDashboard
Sprint BurndownCurrent sprint progressTeam
VelocityStory points per sprint trendTeam, Manager
Cumulative Flow DiagramWorkflow healthTeam
Query TileBug count, active items countAll
Chart for Work ItemsPie/bar chartsAll
Test Results TrendPass/fail over timeManager
Build HistoryCI/CD statusTeam
MarkdownTeam notes, linksAll

Dashboard Examples

  • Team Dashboard: Sprint Burndown + Velocity + Active Bugs + Active Stories + CFD + Sprint Board embed
  • Manager Dashboard: Epic Progress + Feature Timeline + Bug Trend + Team Velocity + Release Burndown + Test Coverage
  • Stakeholder Dashboard: Release Progress + Feature Status + Demo Schedule + Quality Metrics

Sharing: Dashboard permissions (team, project, or specific users) · Favorite (star) cho quick access · Auto-refresh configurable.


GitHub Integration

Setup

  1. Project Settings → GitHub connections → + Connect
  2. Authorize Azure Boards app trong GitHub
  3. Select repositories to connect

Linking Work Items

  • Trong GitHub commit message: Fixed AB#123 — AB#123 = Azure Boards work item ID
  • Auto-links commit to work item
  • Auto-transitions: Fixes AB#123 → closes work item automatically

GitHub PR → Azure Boards

  • PR title: "Feature: Payment form AB#456"
  • Work item shows linked PR + PR status visible on board card

Branch Policy & Traceability

  • Require work item linked to PR — ensure every code change has tracked requirement
  • Azure Pipelines + Boards: build triggers linked work items show build status
  • Release: "Deployed in Release 5" auto-added to work items
  • Full traceability: requirement → code → build → deploy → test

Checklist Azure DevOps Boards

  • Create Azure DevOps organization (dev.azure.com) + project với Agile process template
  • Configure iteration paths (sprints, 2-week cadence) + set team capacity
  • Tạo Epic → Feature → User Story hierarchy cho sprint đầu tiên
  • Customize board columns (Backlog → Ready → In Progress → Review → Testing → Done) + WIP limits
  • Create essential queries (my items, sprint bugs, stale items, unestimated stories)
  • Build team dashboard với Sprint Burndown, Velocity, CFD, Query Tiles
  • Connect GitHub repositories + cấu hình AB# linking cho auto-close work items
  • Train team: workflow, sprint planning, burndown chart, board usage best practices

FAQ

Azure DevOps Boards vs Jira — nào tốt hơn cho Microsoft teams?

Azure DevOps Boards tốt hơn nếu team đã dùng Microsoft stack. Native integration với Azure Repos, Azure Pipelines, Azure Test Plans — traceability end-to-end từ requirement → code → build → deploy → test trong 1 platform. SSO qua Microsoft Entra ID — không cần account riêng. Jira mạnh hơn ở marketplace (3000+ apps), flexibility, Confluence wiki integration. Cost: Azure DevOps free cho ≤5 users (Basic plan), Jira free cho ≤10 users. Enterprise: Azure DevOps tích hợp Microsoft Purview audit, Conditional Access policies — Jira cần Atlassian Access (thêm $$$).

Boards có hỗ trợ Kanban và Scrum cùng lúc không?

Có — Azure DevOps support cả Kanban board + Sprint board đồng thời. Mỗi team có Kanban board (Boards tab) + Sprint board (Sprints tab). Kanban: continuous flow, WIP limits, no time-boxes. Scrum: sprint-based, burndown chart, velocity. Hybrid approach: dùng Kanban board cho visual workflow + Sprint iterations cho time-boxing. Customize board columns, card colors, swimlanes — mỗi board riêng settings. Admin config: Project Settings → Team configuration.

Custom fields và workflow states có được không?

Có — inherited process cho phép custom fields, states, rules, work item types. Organization Settings → Process → chọn process (vd: "MyAgile" inherited from Agile). Add custom field: Work Item Type → + New Field → type (text, number, picklist, identity, date). Add custom state: Work Item Type → States → + New State (vd: "In Review" between Active và Resolved). Rules: auto-assign, auto-set field value, required on state change. Custom work item type: + New Type → define fields, states, form layout.

Azure DevOps Boards có free không?

Có — free cho ≤5 users (Basic plan), unlimited stakeholders. Basic plan (free ≤5): full Boards, Repos, Pipelines (1,800 CI/CD minutes), Artifacts (2 GB). Stakeholder access (free, unlimited): view boards, create/edit work items, view dashboards — KHÔNG access code, builds, test plans. Basic plan (paid): $6/user/month (6th user onwards). Organization cost example: 20 developers ($6×15 paid + 5 free = $90/mo) + 50 stakeholders ($0) = $90/month total.

Làm sao migrate từ Jira sang Azure DevOps Boards?

Dùng Azure DevOps Migration Tools (free, open-source) hoặc OpsHub. Migration steps: Export Jira data → Map fields (Issue Type → Work Item Type, Story Points → Story Points) → Run migration tool → Verify → Redirect team. Azure DevOps Migration Tools (GitHub: nkdAgility): free, support Jira + TFS migration, preserves history, links, attachments. OpsHub: commercial, GUI-based, continuous sync. Timeline: small team (< 1,000 items) = 1–2 days, large team (10,000+ items) = 1–2 weeks. Setup Microsoft Entra ID user mapping trước khi migrate.

Dashboards có share cho stakeholders không phải dev được không?

Có — Stakeholder access hoàn toàn free và unlimited. Stakeholders xem dashboards, boards, work items mà không tốn license. Tạo dashboard riêng cho stakeholders: Release Progress, Feature Status, Quality Metrics — không cần expose technical details (code, builds). Dashboard permissions: set "Team" hoặc "Project" level. Stakeholders có thể create/edit work items (feedback, bugs) trực tiếp trên board. Auto-refresh dashboards hiển thị real-time progress. Export reports: dashboard widgets → Power BI cho executive reporting.


Nguồn Tham Khảo


Hành Động Ngay Hôm Nay

  1. Tạo Azure DevOps organization tại dev.azure.com — chọn Agile process template, tạo Epics → Features → User Stories cho sprint đầu tiên
  2. Kết nối GitHub repository và cấu hình AB# linking để auto-close work items qua commits — setup branch policy require work item linked to PR
  3. Build team dashboard với Sprint Burndown + Velocity + CFD + Query Tiles — share cho stakeholders với Stakeholder access (free, unlimited)

Bài Liên Quan Nên Đọc


Kết Luận

Thành PhầnKhuyến NghịChi Tiết
Phù hợp choDev teams 5–200 người dùng Microsoft stackFree ≤5 Basic users + unlimited stakeholders
Lợi ích chínhEnd-to-end traceability: requirement → code → build → deployNative integration Azure Repos, Pipelines, Test Plans
Bước tiếp theoTạo org + Agile template + GitHub integrationSprint planning + dashboard trong 1 tuần

Azure DevOps Boards = complete Agile work tracking cho Microsoft teams. Epic → Feature → Story → Task hierarchy cho full traceability. Kanban boards + Sprint boards chạy đồng thời — flexible cho mọi methodology. Native integration với Azure Repos, Pipelines, Test Plans — end-to-end traceability từ requirement đến deployment. SSO qua Microsoft Entra ID, audit qua Microsoft Purview, free cho ≤5 Basic users + unlimited stakeholders.

📧 Cần hỗ trợ thiết kế Azure DevOps Boards workflow? PUPAM tư vấn và triển khai Agile work tracking, sprint planning, dashboard, GitHub integration cho dev teams. Liên hệ hello@pupam.com

Was this article helpful?

Your feedback helps us improve our content.

Join the conversation

24 reactions

Share your thoughts, ask questions, or discuss this article with other readers.

Comments are coming soon. In the meantime, email us at hello@pupam.com with your thoughts.
P

PUPAM Tech Team

Passionate about email automation and helping teams work more efficiently. Follow me for more insights on productivity and modern communication tools.

Stay updated with our latest articles

Join thousands of readers who get our best content delivered directly to their inbox every week.

No spam. Unsubscribe anytime.

Ready to transform your email workflow?

Join thousands of teams already using Pupam to streamline their communications.

Get Started Free