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.
We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from Work items, Dashboards, Repo, CI/CD pipelines etc..
Pros
Product Management
Delivery Plans
CI/CD
Cons
Integrate GitHub with Azure DevOps and have just one product
Automatic set Start and Target Date for Delivery Plan based on user story sprint assignment
Likelihood to Recommend
For small enterprises to big, it applies to all for efficient and effective product management with full traceability in built.
Azure DevOps is primarily used by our development and technologies business. It is our premiere tool for application lifecycle management. Azure DevOps helps support real-time communication among global teams ensuring efficiency in all stages of the lifecycle. The build and release pipelines help us to manage thousands of customized application releases assuring customers get our critical changes quickly and regularly.
Pros
The backlogs and Kanban boards for planning and tracking work are second to none. Forecasting and capacity management are made easy with the Azure DevOps tools at our disposal.
The ability to customize work items and workflow is crucial to our business. We are in a specialized, highly regulated business with requirements, unlike most software businesses. We continue to strive to keep development and delivery as lean and agile as possible. We are slowly adopting more DevOps principles. This is especially challenging for our business due to government regulations. As a result, we've adopted an Agile/Waterfall hybrid methodology. Customizing the process, work items and workflow gives us the ability to meet our unique needs.
Git integration is a key feature and keeps our developers happy.
Cons
Some of the administrative tasks and management leaves much to be desired. Security and permissions are managed in different places instead of one central location. Alerts and notifications management could use improvement.
Due to the nature of our business, we are not able to move to the cloud and must use the on-prem version. While Microsoft officially supports the on-prem version, they are geared towards the cloud version of Azure DevOps. Microsoft support for many of our on-prem needs seem to be waning.
Work items should be able to be baselined along with code. While we can label the code that was built, there is no way to take a snapshot in time of the historical state of the work items at the time of the build. A feature like this would save our QA department lots of work.
Likelihood to Recommend
Although hosting Azure DevOps in-house with their on-prem version is manageable, it seems that Azure DevOps is better suited for development shops that are able to utilize the cloud version. That said, if your medium to large-sized company is like ours and need your ALM tools on-prem, be prepared to invest in multiple, full-time staff dedicated to administration if choosing Azure DevOps. For small companies, both cloud and on-prem versions are acceptable.
VU
Verified User
Administrator in Information Technology (Pharmaceuticals company, 1001-5000 employees)
Azure DevOps is currently used across the organization. Currently not all groups and departments are utilizing it however we are in the process of rolling out to these groups. Azure DevOps has become our go to application for development. We are using it for full development life cycle, code repository, testing, deployment and verification.
Pros
Once set up it makes deployments to various environments a breeze
YAML backend is a huge plus
Large groups can work on the same solution seamlessly
Cons
More streamlined set up of CI/CD
Better error messaging to explain why sometimes a build is successful and sometimes not
Easier set up of deployment tools
Likelihood to Recommend
Azure DevOps is by far the leader out there. If you are a Microsoft shop there is no need to look elsewhere. This will handle everything you have with ease and then some. If you have older code then you may need to build some customizations to make it work but anything recent is seamless.
We are using Azure DevOps to as part of our Application Lifecycle Management practice. We leverage it to move code up our different developmental landscape and use it to run automated tests and artifact deployments. Additionally, we use it to manage our resource edge points as well as refreshing servers post-deployment.
Pros
Easy to use and set up and extendable through marketplace.
Highly flexible in configuration right out of the box.
Agent allocation and provisioning is very easy.
Cons
Cost can be a little bit more transparent for agents.
More information on their YAML strategy would help us plan better.
More configuration options in agents would be good as well as on premise agents.
Likelihood to Recommend
Azure DevOps is great for daily releases to QA and allowing developers to deploy to their own local environments if needed. Additionally, it's great for use in container fleet management if you want to have instances that can be brought up and torn upon demand based on the pipeline you are trying to use.
VU
Verified User
Manager in Information Technology (Consumer Goods company, 10,001+ employees)
Azure DevOps is the standard at my company for software source code management and project/requirements management. The cloud-hosted software is being used across all teams to coordinate and track development activities, align release planning, and track work items for testing and verification. Previously we used tools such as Rally and Perforce to serve these needs, but we have standardized on Azure DevOps going forward.
Pros
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Cons
Central Dashboard of Development Metrics: AZDO nests its dashboards in workflow-specific tracks, which is useful. Still, I'd like to see a home page personalized for each user which provides relevant updates on the most recent work items (updates to features, etc.) and work progress.
Complex Queries: AZDO is great for simple queries, but complex queries and the display of results doesn't always produce intuitive results. For example, sorting and drag/drop can be unreliable in some views. I suspect the AZDO team will work out these issues over the next few releases.
Lack of Themes: AZDO allows for the tracking of Epics and Initiatives, but there doesn't seem to be a structured interface for tracking product investment themes.
Likelihood to Recommend
For development teams with a history of Microsoft tools alignment, Azure DevOps provides familiar patterns and interfaces. And for product management / product marketing users, the use of use of data entry and the Excel integration provide for easy on-ramps for learning and proficiency development. For teams that have used tools such as FogBugz, the boards and case layouts may take a little getting used to.
VU
Verified User
Manager in Marketing (Electrical/Electronic Manufacturing company, 5001-10,000 employees)
We are using Microsoft VS (2010,2013,2017) with the integration of Team Foundation Server(TFS) with it. We are using it to keep track of the whole software development life cycle. Each developer regularly checks code changes with the addition of Visual Studio to the TFS. As for the integration side, we are using it to clean , build, and deploy the code changes to different servers to upgrade them to the latest version.
Pros
Visual Studio supports many languages like C#,HTML.C++ and many others. We can also make Visual Studio to support other different languages with the help of plugins, like for Java, Python, etc.
We are using TFS with the VS, so it makes it easy to track the code and project changes, and if required we can also track the code of every single line to see what it means, by whom this code is written, and for which problem.
A unique work item change order number is assigned to the changes that you are making, apart from your shelveset creation
We can create the build definition through which we can automate the deployment and upgrade processes.
It provides a lot of menus and options/templates through which we can make our computer application for enterprise or for non-enterprise
We can easily integrate our customized/required menu in the VS through registry files or through deployment of the code
Cons
Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Likelihood to Recommend
It has been a great tool when comes to code compilation. As a developer, it helps a lot for us to find issues in the code, as Microsoft Visual Studio Team System has the best debugging tools. We can also check the code line by line to find the exact line where the error is. Developers can also place their important code at their shelveset and can easily get it from there when they need to. As for integration, it helps us to compile large code and deploy the changes with a single GO.
Microsoft Visual Studio Team System is being used in our organization for development and testing activities across multiple domains and multiple architectures of multiple products. The biggest business problem it addresses is disparity in branches and trunks of the applications that are being developed. Since the company is merging two vast platforms into one coming from TFS, the independent units working on shared libraries of the framework will eventually migrate everything to one unified WPF framework. Couple this with segregated API automation libraries, the global availability of shared resources with very good version controlling solves endless issues that can result in haphazard application delivery.
Pros
Global availability as opposed to having everything done in silos when teams are dispersed all over the world.
Configuration and administration that reaches out to more people and has overall less impact than having to do spotted administration.
Agile project management is easier to deal with in conjunction with some third-party SCRUM/Agile tools.
Test Automation endeavors can be quickly ramped up as opposed to using other third party solutions that require greater technical resource overhead.
Cons
Possibly some test management and ALM desires that are left out.
Some performance issues not related directly to internal network performance bottlenecks.
It may be pricey from an initial outlook (for larger distributed teams) and that may throw off some companies with challenged budgets.
Likelihood to Recommend
In larger distributed teams or even smaller local teams, MVST is a big contender in application/architecture delivery. In areas where there might be a finite amount of resources or the development can be done more out of a "shrink wrapped" solution, without the need for large configuration of an IDE, it may be suited to stay simpler and do something else besides MVST.
Microsoft Visual Studio is heavily used by our organization. We perform data maintenance on millions of data lists, and Visual Studio makes it very easy to do that. Data files of various formats can be imported into Visual FoxPro. SQL is then used for queries on the data set.
Pros
Easy to use. I began my career as a data analyst without any prior knowledge of Visual Studio, and with very little training, I am a completely independent worker.
In the business of database management, it is important to have a software that can handle millions of records effectively.
Cons
My company uses Microsoft Visual FoxPro for database management for clients. It would be helpful if FoxPro fully supported SQL. It currently accepts some SQL commands, but it is not fully compliant.
Likelihood to Recommend
This software is well suited for database management. It allows the analyst to easily add to and modify the list, no matter what size.
