TrustRadius Insights for Azure DevOps Services are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Customizable Scrum Board: Users have appreciated the scrum-like board in Azure DevOps for its high level of customization options, enabling them to tailor it according to their specific project requirements and team preferences. This flexibility allows teams to adapt the board layout, columns, and cards based on their unique Agile methodologies.
Efficient Test Cases Management: Many users have found the Test Cases storage feature in Azure DevOps beneficial for efficiently managing testing processes within their projects and streamlining test case organization and execution. By centralizing test cases within the platform, teams can easily track testing progress, link tests to user stories or features, and ensure comprehensive test coverage.
Seamless CI/CD Pipelines: Users highly value Azure DevOps for its exceptional ease in creating build and deploy pipelines, strong GitHub integration, robust support for continuous integration and continuous deployment processes, contributing to smoother development workflows. The seamless pipeline creation process includes built-in connectors for Azure services, simplifying pipeline setup and enabling automated deployments with minimal manual intervention.
Azure DevOps Services Reviews
12 Reviews
Small Businesses (1-50 employees)
Search is temporarily unavailable. Filters are still applied.
We use ADO to manage our entire pipeline of work. Backlog items, tasks, and bugs, code repositories and pull requests, code reviews, pipeline management, releases and CI/CD, testing, deployment, and oversight. Overall, our whole process depends on the capabilities that DevOps brings to the table and wouldn't be the same, otherwise.
Pros
Backlog management
Build / Release management
Code review and pull requests
Cons
Tracing where security rules are coming from
wiki management
Mass-editing values (adding tasks, etc...)
Likelihood to Recommend
Definitely great for developing .net applications and keeping track of a backlog in a SCRUM environment. I think managing a backlog and the associated schedule are also very strong.
I would think that managing an application with a non-microsoft environment would be less appropriate (ie: a node.js back-end application with a react front end, for instance...)
We use Azure DevOps as our continuous deployment solution. Essentially, anytime we merge code into staging or master, we use Azure DevOps to automatically build and deploy.
Pros
It makes it super easy to create build and deploy pipelines
It has built in connectors for most of Azure
It ingrates well with GitHub
Cons
The Azure service connection's secrets expire annually by default. Not a big deal, but it's a little annoying when builds start to fail because of an expired connection.
Likelihood to Recommend
Anytime you're deploying to Azure it's the way to go. It works great for CI/CD.
VU
Verified User
Director in Information Technology (11-50 employees)
I use Azure DevOps to schedule runs for automated test cases. It provides the feature to share results via Webhooks. So the team is able to know about the status of the test runs by alerts configured via Webhooks.It helps to track builds and perform dependency checks. It helps to create builds and deploy them.
Pros
Dependency check for builds
Deploy the builds in the respective environments
Run the tests in different stages within Azure DevOps
Cons
When I cancel a release, it asks for adding comments however, finding that comment later is difficult, the automated emails shared for each build do not contain the comments as well.
The UI/UX can be improved to be more intuitive
Likelihood to Recommend
Scenarios where it is suited:
1. Separating the builds into specific purposes into different pipelines 2. Automatically performing dependency checks, deploying the build and running tests on it 3. Tracking the status of different stages
Scenarios where it is less appropriate:
1. Companies which work on the waterfall model 2. Companies that don't utilize CI/CD
Azure DevOps Services are used to manage our daily work tasks. This helps us to keep track of the progress of each task accordingly, with this we can check the status of each task from one stage to another, we can assign the task to the correct personnel within the organization, and leave comments/attachments inside as well.
Pros
Keep track of working tasks across organization.
Set up automated CI/CD pipelines.
Overview/detailed view of overall working progress.
Cons
UI can be more user-friendly.
Navigation between tasks can be smoother.
Warning before leaving the page when there's a draft can be useful.
Likelihood to Recommend
Azure DevOps Services provide many different useful services, some of which I'm using is the Azure boards and pipelines. It is very useful to keep track of the status of each task within projects. The query function is also useful to check on tasks per person/status easily. However, the UI can be more user-friendly.
VU
Verified User
Engineer in Information Technology (11-50 employees)
It is being used Organization wide and helps us solve with our software development and deployment.
Pros
Azure DevOps is great at managing and securing git repos. Reviewing pull requests and seeing diffs is great. You can even communicate back and forth with your team members right there in the code review screen.
Pipelines is a powerful feature for allowing you to deploy to anywhere (cloud, on prem, etc.) You can secure your pipelines and track your artifacts with ease.
Boards is a great tool for managing your work task as well as associating your commits with the work item.
Cons
I love Azure DevOps. I can't think of anything that requires improvement.
Likelihood to Recommend
It is well suited for managing software development. Code management, deployment, work item tracking. It allows remote teams to work together easily.
VU
Verified User
Partner in Information Technology (1-10 employees)
We use Azure DevOps to manage all our projects across the whole organization. The project manager usually translates all software requirements to Azure DevOps and assign appropriate tasks to programmers. It is a very flexible tool to implement DevOps methodology. The project development is followed through the platform, as well as the team performance.
Pros
Easy representation of software requirements in user stories and tasks.
It allows the tracking of activities and team performance
It allows interaction between team members in a specific task
You can use only a few tools to complement your existent workflow
There is a free version for small teams (up to 5 users)
Cons
Some small improvements could be done in the user interface.
Sometimes the performance is low (some requests/queries are slow)
Likelihood to Recommend
Azure DevOps allows you to start with DevOps methodology in a fast and easy way. The graphical interface is great and it is suitable to small and big teams. It really helps you to manage projects, tasks and teams.
We're implementing entire product workflows with Azure DevOps: building, testing, staging and deploying. It's the perfect companion for Visual Studio and Git, so everyone just loves using it. It's a dream come true not having to switch to different front-ends to get our job done throughout the day, while keeping an amazing user experience.
Pros
Unified environment for all DevOps tasks and procedures
Amazing User Experience within a beautiful UI
Great marketplace extensions collection
Cons
Code merging has room for improvement
Such a broad set of features can become confusing for the novice user
Likelihood to Recommend
It's a great way to normalize DevOps wokflows, allowing you to replace lots of different tools and get the job done with a unified package. Testing support is second to none. If you're just focusing on development with version control, than Visual Studio packed with Git will probably cover all your needs.
Using VSTS in an agile fashion, we are using the change management features like view history, view changesets, compare, create shelvesets, and to create work items. We optionally could use VSTS for continuous integration/delivery to Azure, but the expense far outweighs AWS. VSTS has made us into a .net shop that is useful for checking in artifacts from Example Author, Microsoft Office/365, or other third party vendors.
Well suited for .net shops, distributed/offshore outsourcing, or small scale development. Less suitable for isolated or modular component development. Although the API is suitable, the licensing cost may be prohibitive for open source projects. VSTS is an end to end change management and collaboration tool that has a robust feature set for the enterprise. A VS Code-like analog companion similar to VSTS for no charge would be excellent.
It is used across the organization. We use it for tracking tasks as well as for CICD.
Pros
Task management
Capacity Management
CICD
Cons
Once you add a new sprint, it does not automatically reflect in the left panel of work items. You have to select the iteration under default teams settings. This is a bit confusing and difficult to figure out if you don't know.
When a task is marked as Resolved, the remaining time does not become 0 like it happens when you close the task. It may be a good idea to reset it to 0 for resolved tasks as well.
The system allows you to close a user story which has open tasks under it. A warning mentioning this while closing the user story will be good.
Likelihood to Recommend
I believe it can be used in all projects, big or small. All projects are broken down into subtasks and VSTS is a great tool to manage subtasks and capacity.
We use VSTS as source repository for all the web projects. We also manage and assign the tasks of the development team. The continuous integration and the continuous deployment are provided with a mix of on premise installations and Azure instances. The project management monitor the projects advancement with customized reports.
Pros
Easy to install.
Full integrated: source control, task management, report tools.
Plugin for VS, Eclipse, Rider and many others.
Cons
Backup and restore is really slow.
Likelihood to Recommend
VSTS is recommended in a scenario where a very lot of projects have to be managed on premise. The possibility to mix the on premise version with the online version allows to create customized scenario to easily adapt to every teams and technologies. The task management integrated in the IDE is a plus.
