Kanban Board Azure DevOps

In this article, I’m going to walk you through everything you need to know about mastering the Kanban board in Azure DevOps. We’ll cover everything from initial setup to advanced flow optimization techniques that will turn your team into a high-velocity system.

Kanban Board Azure DevOps

What is a Kanban Board in Azure DevOps?

At its core, a Kanban board is a visual system for managing work as it moves through various stages. In Azure DevOps, the Kanban board transforms your flat list of “User Stories” or “Product Backlog Items” into a dynamic, interactive visualization.

Unlike a Sprint taskboard—which resets every two weeks—the Kanban board is continuous. It focuses on the Flow of work. It answers three critical questions for any Project Manager:

1. What are we doing right now?
2. What is blocked?
3. Where is the bottleneck?

Step 1: Accessing and Initializing Your Board

When you first create a project in Azure DevOps, whether you choose the Agile, Scrum, or CMMI process template, a Kanban board is automatically provisioned for you.

To find it, navigate to Boards > Boards in the left-hand sidebar. Check out the screenshot below for your reference.

Choosing the Right Backlog Level

Before you start moving cards, you need to decide which level of work you are managing. Most teams manage at the Stories (Agile) or Backlog Items (Scrum) level.

• Epics Board: High-level strategic initiatives for leadership.
• Features Board: Major shippable units for Product Owners.
• Stories Board: The “Execution” board for the dev team.

Always recommend starting with the Stories board.

Step 2: Customizing Columns to Reflect Your Reality

The default columns in Azure DevOps are “New,” “Active,” “Resolved,” and “Closed.” Honestly? These are rarely enough for a professional enterprise. Your board should reflect your Actual workflow, not a generic one.

How to Customize Columns:

1. Click the Gear Icon (Settings) in the top right of the Board view.
2. Select Columns.
3. Add or rename columns to match your process. Check out the screenshot below for your reference.

A Professional Example:

| Column Name | State Mapping | Definition of Done (Done Criteria) |

| :— | :— | :— |

| New | New / Proposed | Stakeholder has approved the requirement. |

| Analysis | Active | Requirements are fully documented. |

| Development | Active | Code is written and unit tests pass. |

| Peer Review | Active | Pull Request (PR) has been approved by a teammate. |

| Testing/QA | Resolved | Passed all automated and manual regression tests. |

| Deployment | Closed | Successfully pushed to Production. |

Step 3: Implementing Work-In-Progress (WIP) Limits

This is where Kanban becomes “Kanban” and stops just being a “To-Do list.” WIP Limits prevent your team from multi-tasking and ensure that they focus on finishing work rather than just starting it.

In Azure DevOps, you can set a maximum number of items allowed in any given column. If I’m managing a team with three developers, I might set the “Development” WIP limit to 4. If a 5th item enters that column, the header turns red.

Why WIP Limits Matter:

• Identification of Bottlenecks: If your “Testing” column is always red, you don’t need more developers; you need more QA testers.
• Improved Cycle Time: By doing fewer things at once, each item gets finished faster.
• Focus: It gives your team permission to say “No” to new work until current work is moved along.

Step 4: Using Swimlanes for Expedited Work

Imagine our VP of Engineering, calls with a “Production Hotfix” that needs to happen now. You don’t want that hotfix buried in your standard list of tasks. This is where Swimlanes come in.

Swimlanes are horizontal rows on your board that allow you to categorize work by priority or type.

Common Swimlane Configurations:

• Expedite/Emergency: For critical bugs that bypass the standard queue.
• Standard: Your day-to-day feature work.
• Regulatory/Compliance: For tasks related to audits or legal requirements.

By creating an “Expedite” lane at the top of your board, you ensure that the most important work is never invisible.

Step 5: Setting “Definition of Done” (DoD)

Azure DevOps allows you to add a Definition of Done directly to each column header. When a team member hovers over the “i” icon in the column, they see a checklist.

• Example for “Peer Review” Column:
  • PR has at least two approvals.
  • No merge conflicts exist.
  • Comments from reviewers have been addressed.

Step 6: Tagging and Styling for Instant Visibility

When you’re looking at a board with 40 cards, you need to be able to “scan” it in seconds. Azure DevOps provides Card Styling rules that act like a heat map for your project.

Professional Styling Ideas:

• High Priority: Make the card border Red if Priority = 1.
• Stale Work: Change the card color to Yellow if it hasn’t been moved in 7 days.
• Blocked Items: Use a specific “Blocked” tag that turns the card Purple.

Step 7: The “Power of the Pull”: Split Columns

In a traditional push system, a developer finishes code and “pushes” it to testing. In a professional Kanban system, work is Pulled.

Azure DevOps supports Split Columns (Doing/Done). When a developer finishes their work in the “Development” column, they move it to the “Done” sub-column. This signals to the QA engineer that the item is ready to be Pulled into the “Testing” column.

This tiny change eliminates the need for “Is this ready?” pings in Teams. The board tells the story.

Step 8: Analyzing Flow with Cumulative Flow Diagrams (CFD)

If you aren’t looking at your analytics, you aren’t really managing the project—you’re just watching it happen. The Cumulative Flow Diagram (CFD) is the most important chart in the Kanban world.

To find it, click the Analytics tab in the top right of your Board view.

How to Read a CFD:

• Wider Bands: Indicate a bottleneck in that specific stage.
• Narrowing Bands: Indicate that you are “starving” a process (work isn’t coming in fast enough).
• Smooth Slopes: Indicate a healthy, predictable delivery pace.

Summary of Kanban Board Best Practices

Follow this checklist:

• Keep it Live: The board is the source of truth. If it’s not on the board, it isn’t being worked on.
• Review WIP Limits: Every two weeks, check if your limits are too high or too low.
• Automate State Changes: Use “Successor” and “Predecessor” links to ensure the board stays organized.
• Use the Discussion Thread: Encourage developers to leave notes directly on the card so history is preserved.

Video Tutorial

Conclusion:

Mastering the Kanban board in Azure DevOps is about maintaining a well-designed dashboard for your project that not only increases productivity but also streamlines processes.

When you configure your board with Custom Columns, WIP Limits, and Swimlanes, you stop asking about status and check the “flow.”

You may also like the following articles:

• Azure DevOps CI CD Pipeline Step By Step
• Azure DevOps Tutorial For Beginners
• How To Use Azure Devops For Project Management
• How To Create A Feature In Azure Devops
• How To Delete A User Story In Azure DevOps
• How To Merge Two Branches In Azure DevOps

Rajkishore

I am Rajkishore, and I am a Microsoft Certified IT Consultant. I have over 14 years of experience in Microsoft Azure and AWS, with good experience in Azure Functions, Storage, Virtual Machines, Logic Apps, PowerShell Commands, CLI Commands, Machine Learning, AI, Azure Cognitive Services, DevOps, etc. Not only that, I do have good real-time experience in designing and developing cloud-native data integrations on Azure or AWS, etc. I hope you will learn from these practical Azure tutorials. Read more.