Azure DevOps, Formerly VSTS, Makes your Life Better
January 11, 2019

Azure DevOps, Formerly VSTS, Makes your Life Better

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Microsoft Visual Studio Team System

We use Microsoft VSTS, now Azure DevOps, in the IT department for our software development management. In the past, we used TFS coupled with other items. Since we're a Microsoft shop, it made complete sense to make the jump to VSTS.

The automated features are great; we especially enjoy the build and deploy automation. We also like the board capabilities, better query option, and increased visibility Microsoft VSTS has given us over TFS. Microsoft is always adding new features as well, which helps us streamline or automate our processes even further.
  • Board view of the work we're doing. Project management has found this to be especially helpful and has enjoyed how configurable it is to our needs.
  • Automation: From testing to the publishing process, there are plenty of options to automate workflows and processes. This has freed up resources and time for our teams to get more meaningful work done.
  • Collaboration: Since we came from TFS, it's the small things that have enabled greater collaboration within the team and with other departments/stakeholders like the ability to tag individuals in comments, following an item and receive email updates, etc.
  • It would be nice to have a master board to see everything going on across all projects. This is more of a management view, I would think. For me, I'm having to jump back and forth between our projects. I would like to be able to projects on the master board if this view were available.
  • All positive so far. The automation mentioned previously has been a jump forward, freeing up department resources and time.
Compared to other tools we have used, Microsoft STS has been a much more complete tool. Communication, collaboration, tracking, management, automation, testing, speed to production—all these areas have been improved since we started using Microsoft STS. We have been looking for ways to be more transparent as a department too and Microsoft VSTS has helped in that journey.
For us, as a Microsoft shop, it fits very well into what we're doing. This is especially true since we had used TFS for years. In fact, we wish we had made the transition sooner. Like all tools, there is a learning curve for everyone involved in the transition. It's taken our team time to learn the ins and out. And it's been a great leap forward for us. Microsoft VSTS may not be as friendly depending on the technologies you use. We've found it works well, even with non-Microsoft technologies. We're excited to see further tie-ins with GitHub and other technologies in the future.