Getting Started With Azure DevOps

Introduction

This is a series of articles to get our hands dirty with Azure DevOps (previously known as VSTS).

In this article, we will focus on the board section of Azure DevOps and on Wiki, these two features are alternatives for JIRA and Confluence (Atlassian products).

Please refer to the previous articles to understand the basics of Azure DevOps and a hands-on lab.

It will cover the following things.

Hands-on Lab – Create work items of different types + Assign
Hands-on Lab – Try moving work items across the board
Hands-on Lab – Create a sprint and move the work item into it
Hands-on Lab – Show the usage of queries
Hands-on Lab – Create a WIKI and link it to the work item

Hands-on Lab – Create work items of different types + assign

Steps to be followed:

Open https://dev.azure.com/ and log in using your Azure credentials.

Go to the boards tab and select the “Work Items” tab and add a new work item to see the options.

Click on the User Story and give a name to user-story – “User-Story-1” and assign it to me (Gourav Jain) and click "Save".

Click on “Add link” under related work and add a work item of type “Task” in it and name it “Task-1” and assign it to me and save it.

Now, we will have two work items in the list of type “User Story” and “Task”.

Hands-on Lab – Try moving work items across the board

Steps to be followed:

Open https://dev.azure.com/ and log in using your Azure credentials.

Go to the Boards tab, open the board tab and see the work items there in the New section.

Let’s move the story into the active section.

Hands-on Lab – Create a sprint and move the work items into it

Steps to be followed:

Open https://dev.azure.com/ and log in using your Azure credentials.

Go to the Boards tab and select “Sprint” tab and add a sprint with the current date to one more day, i.e., sprint will last for two days – tomorrow and the day after.

After that, choose a “task board” option from the Sprints menu and move the story into the current iteration of the Sprint.

Then, give the capacity of the person to 8 hrs (working) per day.

Go to the task and fill the estimate and fill the hours and close the task.

Go to the task board and check for the burn chart and here, you can see, 8hrs of burn-out is remaining which needs to be completed by the 30^th as per an ideal process.

Hands-on Lab – Show the usage of queries

Steps to be followed:

Open https://dev.azure.com/ and log in using your Azure credentials

Go to the Boards tab and select the “Queries” tab and create a query to show all work items assigned to me which are in ‘CLOSED’ state. There, we will see only one item; i.e. task which has been closed by us.

Hands-on Lab – Create a WIKI and link it to the work item

Steps to be followed,

Open https://dev.azure.com/ and log in using your Azure credentials

Go to the Overview tab and select “WIKI” tab and create a WIKI page there named “Wiki-1” and save it.

After that, we can link the wiki to any work item and can see that wiki page is shown in the work item, here we have pointed Task-1 to the wiki page created in the last step.

Stay tuned for the next series of articles which will cover a deep dive into Azure DevOps.

Happy Learning!

Getting Started With Azure DevOps - Part Four

Reactions

Introduction

Hands-on Lab – Create work items of different types + assign

Hands-on Lab – Try moving work items across the board

Hands-on Lab – Create a sprint and move the work items into it

Hands-on Lab – Show the usage of queries

Hands-on Lab – Create a WIKI and link it to the work item

Comments