Scrum and Azure DevOps

As we have already mentioned in previous posts, we are utilizing Azure DevOps as a single solution for all things planning, SCRUM, Git, CI/CD, automated/manual testing and so on. After weeks of using it, we must say that we are pretty much satisfied with it. There’s no need to leave the tool for other tasks, it has everything we need just like a Swiss Army knife.

IDE Integration

• 

Team backend uses Visual Studio 2019 whereas team frontend uses Visual Studio Code for their workload. Both environments are deeply integrated with Azure DevOps and share some features in commonality.

📝 Tasks, Pull Requests & CI/CD

On the right side of Visual Studio, you notice that there’s a panel with all tasks that are assigned to me. Visual Studio allows us to connect to an Azure DevOps project and look into work-related items without leaving the IDE.

We are also able to look into pull requests and CI builds as shown in the gallery above. Click on the images to view them.

🍴 Git

Of course, there’s also a Git client built-in in Visual Studio. I won’t add anything extraordinary to it since it’s pretty much self-explanatory:

SCRUM Board

At the heart of Azure DevOps, there’s boards that allow us to do our planning. There are several frameworks available like Agile, Basic and SCRUM, but we obviously went for the latter.

As you can see in the screenshot above, these are our tasks of this week, each assigned to a parent backlog item, to someone who is committed enough to deal with them and with an estimated time.

Furthermore, we can analyze our sprints and generate burndown charts:

We don’t have a perfect burndown just yet, but this is how it looks like. Azure DevOps also allows us to export data/queries to Power BI and create visualizations in there.

You can have a look around here. Unfortunately, some features are hidden for guest users, so you might not see all aspects that are covered in this post.

That should cover it all for now. Cheers.