Creating a high-quality user story in Azure DevOps establishes a clear contract between the product owner and the engineering team. In this article, I will walk you through the precise steps to create an authoritative user story within Azure Boards, ensuring your backlog is ready for a high-velocity sprint.
Table of Contents
- How To Create User Story In Azure DevOps
- Using the Discussion for Collaboration
- Video Tutorial
- Summary Checklist for Creating a User Story
How To Create User Story In Azure DevOps
Before we can create a story, we need to be in the right environment. Azure DevOps provides multiple “hubs” for managing work, but for user stories, we focus on Azure Boards.
- Sign in to your Azure DevOps organization (e.g.,
dev.azure.com/YourOrganization). - Select your Project from the dashboard.
- On the left-hand sidebar, hover over Boards and select Work Items or Backlogs. Check out the screenshot below for your reference.
Pro Tip: I always recommend working from the Backlog view. It allows you to see where your new story fits in the overall priority of the product relative to other items.
Creating the User Story: Step-by-Step
There are two primary ways to add a story. You can use the “New Work Item” button for a full-screen entry, or the “Quick Add” feature on the backlog for a rapid way.
Method A: The Full Work Item Form
This is the preferred method when all your requirements are ready.
- Click the + New Work Item button.
- Select User Story from the dropdown menu. (Note: Depending on your process—Agile, Scrum, or CMMI—this might be called a “Product Backlog Item” or “Requirement”).
- Title: Enter a descriptive title. I recommend a “Feature: Action” format, such as “Cart: Add US Sales Tax Calculation.”
Method B: The Quick Add (Backlog View)
If you are in a refinement session with your team, use the green plus sign at the top of the backlog list.
- Type the title.
- Press Enter.
- Click the title afterward to open the full form and add the “meat” of the story.
Check out the screenshot below.
Essential Components of a Professional User Story
A user story in Azure DevOps is only as good as the data within it. To maintain authority and clarity, I insist that my teams fill out these specific fields:
The Description (The “Who, What, Why”)
In the Description field, you should always have:
- As a [Persona, e.g., Raj the Shopper]
- I want to [Action, e.g., see the total tax before checkout]
- So that [Value/Benefit, e.g., I can finalize my budget before the transaction].
Check out the screenshot below for your reference.
Acceptance Criteria (The “How it’s Done”)
This is the most critical field for your QA engineers and Developers. It defines the “Definition of Done” for this specific item. I prefer the Given-When-Then format (Gherkin style):
- Given: The user is on the checkout page.
- When: They enter a California zip code.
- Then: The system applies the correct state and local sales tax to the total.
Check out the screenshot below for your reference.
Classification and Metadata
To ensure your story is “queryable” and shows up in the right reports, you must set the metadata correctly.
| Field | Purpose | Recommendation |
| Area Path | Defines which team or functional area owns the story. | Map this to your specific feature team (e.g., Finance-App\Checkout). |
| Iteration Path | Assigns the story to a specific Sprint. | Keep it in the Backlog until it is officially planned for a Sprint. |
| Priority | Sets the business urgency. | Use 1 for “Must Have” and 4 for “Nice to Have.” |
| Value Area | Categorizes the work type. | Select Business for customer features or Architectural for technical debt. |
Estimating Effort with Story Points
In the Agile process template, you will see a field for Story Points. This is where your team’s collective knowledge comes into play.
- Don’t estimate alone. Use Planning Poker or similar techniques.
- Use the Fibonacci sequence (1, 2, 3, 5, 8, 13) to represent relative complexity rather than hours.
- Input the value in the “Story Points” field on the right side of the Azure DevOps form.
Check out the screenshot below for your reference.
Establishing Traceability: Links and Parents
How to Link a Parent:
- On the User Story form, look for the Related Work section.
- Click Add link > Existing item.
- Select the Link Type as Parent.
- Search for the relevant Feature ID or title (e.g., “Feature: Improved Checkout Experience”).
Using the Discussion for Collaboration
Azure DevOps isn’t just a database; it’s a communication tool. Use the Discussion section at the bottom of the story to:
- @Mention team members (e.g., “@bijay, can you verify the API endpoint for this?”).
- #Reference other work items or bugs that might impact this story.
- Attach screenshots or wireframes directly to the discussion for visual context.
Best Practices for Agile Teams
- Avoid “Dev-Speak”: The title should be understandable by a stakeholder like Michael from Marketing, not just the Lead Engineer.
- Keep it Small: If a story is estimated at 13 points or higher, it’s likely an “Epic” in disguise. Break it down into smaller, testable chunks.
- The “INVEST” Model: Ensure every story is Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Video Tutorial
Summary Checklist for Creating a User Story
Before you hit “Save & Close,” run through this quick checklist:
- Does the Title clearly state the action?
- Is the Description in the “As a… I want… So that…” format?
- Are there at least 3-5 Acceptance Criteria?
- Is the Area Path and Iteration Path set?
- Is it linked to a Parent Feature?
- Has the team provided a Story Point estimate?
By following this structured approach, you ensure that your Azure DevOps project delivers high-quality stories that lead to high-quality code.
You may also like the following articles:
- How To Delete A User Story In Azure DevOps
- How To Move User Story From One Sprint To Another Azure DevOps
- How To Merge Two Branches In Azure DevOps
- How to Create a New Repo in Azure DevOps
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.
