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 for me is a one stop solution for managing my project work. With managing what i emphasize on if regular creation and maintenance of user stories on how and where is project headed to, bugs maintenance, team retrospective, source control management for codes and last but not the least continuous integration and deponent of my code to production
Pros
Continuous integration
Continuous deployment
User stories creations
Bug tracking
Cons
Cost
Provide its Training
External tools integration
Likelihood to Recommend
It can be best suited for projects that jave extensive relying on Microsoft projects and it can seamlessly Integrate with Microsoft active directory. Another work scenario suited best could be if the project is agile development, Azure DevOps Services gives a lot of tools and it's services that could proce efficient for agile projects such as boards, retrospectives etc.
We use ADO for a wide range of things. We create work items in there, essentially being a unique number that we can associate with a project. We also use ADO to create features, user stories, acceptance criteria, and test cases in ADO. The linking system in ADO allows good visibility across these.
Pros
The use of the scrum-like board, which can be customized to your liking.
Excellent linking and visibility across items in ADO e.g. user stories, features, test cases, tasks, etc.
Storing Test Cases.
Cons
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
It could improve the search slightly better.
Likelihood to Recommend
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Alternatives
Atlassian Confluence
ADO has better linking than Confluence and is adaptable for a specific need, whereas Confluence might be a bit more rigid, but it's also sort of along the same lines as to what can be done with both tools. ADO also had an ease of use to it and can do a bunch of stuff with it, e.g., store test cases, create user stories, deployments, etc.
VU
Verified User
Professional in Professional Services (Information Technology & Services company, 10,001+ 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
Alternatives
Jenkins
As a cloud services user of Azure, using Azure DevOps made sense because it has the most support tailored for Azure ecosystem.
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 (Information Technology & Services company, 11-50 employees)
We use Azure DevOps for the CI CD of our applications and the scrum boards. We also create artifacts and consume those artifacts in our applications All our reports are also available on it. With another extension, we can add our time tracking for items in the PBI. To get an overview of open PR, we configured some dashboards.
Pros
The scrum board is pretty good.
CI/CD.
Repos
Cons
For PM, it's not really easy to bulk import a lot of items.
The search in code does not always find some things.
Likelihood to Recommend
It's great to use when you use Scrum, Repos, and CI/CD. This way, you don't need multiple applications, but you can just use Azure DevOps. For development, I find it pretty good. You can link your items to your Pull request, and you will be able to see what changes have been made. The only downside is that if you want to make your board visible to a lot of stakeholders, it won't be that easy.
Alternatives
Jira Software and Trello
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
VU
Verified User
Employee in Information Technology (Human Resources company, 201-500 employees)
We are currently using Azure DevOps Services to manage the entire software development cycle. Azure Board, pipelines, and test cases are wonderful features in one platform. when you use pipelines, you will have drag and drop choices for quickly building your CI/CD pipelines. Azure Board will help you to manage your project management in an effective way.
Pros
Azure Board to project management
Azure pipelines to automation in your project
Azure test cases to manage your test cases management
Cons
improvement in dashboard
improvement in repository access
improvement in Azure artifact management
Likelihood to Recommend
- project management for Azure Board - code management for Azure repo - continuous integration and continuous delivery we have Azure pipelines - Artifact management we do have Azure Artifact - Test case management we have Azure test cases
Alternatives
GitLab and GitHub
Azure DevOps Services have huge functionality and are well supported by Microsoft as well. You will get plenty of features in the marketplace and learning documentation.
VU
Verified User
Consultant in Information Technology (Information Technology & Services company, 201-500 employees)
In my opinion, This is one of the Hottest products right now booming in the market. This has solved lot of problems in terms of Automation and End to End Deployments. In our organization, We are using this for 1. To track Team's Efforts in terms of User stories and Assigning Tasks. 2. Storing all the code and performing End to End Deployment and Testing from Development phase to Production Phase.
This has actually solved a lot of problems which all the Team members used to face few years back, setting the tasks, scope, completion is now smoother and easier for everyone. We also have the option to Integrate with other software's and perform the deployments which is a huge plus.
Pros
Azure Boards to Assign tasks, User stories to team members and track their time so easily.
Azure Repos used to store all the code used from Development phase to Production Phase.
Azure Pipelines - Great feature to deploy the products with End to End testing.
Automating any kind of solution/problem on Azure Cloud using PowerShell/CLI scripting.
Cons
Security of the Third Party Plugins Integrated with the Pipelines.
Notification of the Tasks which are getting closer in time.
Can Improve in terms of integrating few more required software.
Likelihood to Recommend
Well Suited: To Automate End to End Solution on any cloud. Deploying End to End product with End to End Testing. Maintaining all the Team's Efforts, bit much in Agile Methodology.
Less Appropriate: Using Extra Software's when required is bit hard to Integrate.
Alternatives
Databricks Lakehouse Platform (Unified Analytics Platform), Azure App Service, Azure Blob Storage, Microsoft Teams, Microsoft Visual Studio Code and Azure Virtual Machines
Writing the Docker Images, Storing them in Azure Container Registry and then Deploying onto Azure Kubernetes Services is an Easier process which no other software/product is currently providing in the market. Best till date in terms of End to End deployment and maintaining after deployment.
Azure DevOps is used for project management of our sprint tickets to assign within team and provide the dashboard information to our project managers. The user story is easy to create and assign to the owner and then create the sub-task to assign within the user for different tasks like (Development, Peer QA, Final QA e.t.c)
Pros
User Story
Dashboard
Sub Task Creation
Reporting
Cons
Divide sub task and timings
Time divide between each task
Integration with other tools is difficult
Likelihood to Recommend
As the other project tool management it is good because of the part of Azure family. Being a Microsoft tools it is quite compatible with the other azure products. Azure DevOps is very useful for the operational project to create all the user stories with the same task including various ad-hoc tasks
Alternatives
Atlassian Jira Align (formerly AgileCraft)
Azure DevOps is widely used because of its collaboration and integration with various other tools. Here the assign of the sub task is quite easy compare to Jira. Also Azure Devops can we integrate easily with Git for better code representation and versioning. It reporting is very much helpful for senior management to understand the project health.
VU
Verified User
Employee in Information Technology (Information Technology & Services company, 5001-10,000 employees)
We are using Azure DevOps across most teams, leveraging both Kanban and Scrum methodologies. The tool is used for SDLC workflow, source control, and documentation.
Pros
Source control integration.
Templates for multiple Agile types.
Cons
Document management (implement something similar to Sharepoint libraries).
Streamlined permissions structure.
Likelihood to Recommend
Azure DevOps, on the whole, is very easy to set up and use if you have any experience with Agile processes. The initial barriers to entry are extremely low as the first 5 users can leverage the tool for free. I found the overall feature/functionality easier to use and more approachable than similar tools. It is also leaps and bounds better than TFS if you haven't looked at it in a while. If you are already a git user, this is directly integrated with git repos, making the transition easy. The tool is also integrated with many other Microsoft products, so if you are a Microsoft-centric shop, you can leverage the broader ecosystem.
Alternatives
DevOps is more full-featured than its on-prem predecessor or any of the above with the possible exception of the Atlassian suite. I would say those two are roughly comparable. However, the ease of integration is much better with DevOps and other Microsoft products (although it has been a couple of years since I reviewed Atlassian). Again, if you are Microsoft-centric, DevOps is a no-brainer. If you are not, then Atlassian is definitely worth a look.
VU
Verified User
Professional in Information Technology (Architecture & Planning company, 1001-5000 employees)
Azure DevOps is being used by our development department. It addresses the problem of not having a central source code storage location with team collaboration. It is used to store and collaborate on development projects. All team members are checking in/out their source code and pipelines/team collaboration is in use.
Pros
Ease of use/integration with Visual Studio.
Very responsive and easy to maintain a site.
Has full Git capabilities.
Capability to store unlimited numbers of projects.
Cons
The price/license per user could be a little less than many of the open-source type source code platforms on the market.
Ease of integration with other development IDE's than Visual Studio.
Likelihood to Recommend
No matter how many developers you have within the company, a robust source code control/DevOps pipeline is a must. When a new software development project is needed it can be initiated within DevOps by any team member/manager. The project can be tracked from start to finish with alerts and message ability directly in the product. The QA team can also monitor and provide feedback directly within the product.
Alternatives
GitHub and Gitlab
GitHub seemed to be more of an open-source development environment and made it a little challenge to keep our source private and onsite at our own facilities. Gitlab did not have the full Dev Ops pipeline and seemed to have a lot of different bugs when using it. We used the VSTS product and continue to use it when it became Azure DevOps and have not had the types of issues described.
VU
Verified User
Manager in Engineering (Information Technology and Services company, 1001-5000 employees)