What’s new in Azure DevOps Sprint 155

Anisha Pindoria

Sprint 155 has just finished rolling out to all organisations and you can check out all the cool features in the release notes. Here are just some of the features that you can start using today.

Manage pipeline variables in YAML editor

We updated the experience for managing pipeline variables in the YAML editor. You no longer have to go to the classic editor to add or update variables in your YAML pipelines.

Get insights into your team’s health with three new Azure Boards reports

You can’t fix what you can’t see. Therefore, you want to keep a close eye on the state and health of their work processes. With these reports, we are making it easier for you to track important metrics with minimal effort in Azure Boards.

The three new interactive reports are: Burndown, Cumulative Flow Diagram (CFD) and Velocity. You can see the reports in the new analytics tab.

Metrics like sprint burndown, flow of work and team velocity give you the visibility into your team’s progress and help answer questions such as:

  • How much work do we have left in this sprint? Are we on track to complete it?
  • What step of the development process is taking the longest?
  • Can we do something about it? Based on previous iterations, how much work should we plan for next the sprint?

With these new reports, it is super easy to answer all these and more. The new reports are fully interactive and allow you to adjust them for your needs. You can find the new reports under the Analytics tab in each hub. Check out the video for a demo on these as well as the release notes.

These are just the tip of the iceberg, and there are plenty more features that we’ve released in Sprint 155. Check out the full list of features for this sprint in the release notes.


Discussion is closed. Login to edit/delete existing comments.

  • Shayki Abramczyk 0

    The approvals in the yaml pipelines are great, but now they are available only for Environments, do they will be also for regular Multi Stage pipelines? 

    • Gopinath ChigakkagariMicrosoft employee 0

      We want to move away from adding approvals to “stages” to “resources”. We are thinking of protecting all key resources with Approvals – it includes Environments for now and later point Pools, Service Connections.. etc… Would love to understand your scenario of protecting a statge?

Feedback usabilla icon