TrustRadius Insights for Azure DevOps Server are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Task Management: Users have found Azure Boards fast and easy to use once a good structure is established, enabling quick creation or modification of task types. This reduces administrative overhead and facilitates the creation of numerous smaller tasks.
Simplified Setup Process: Reviewers appreciate Azure Repos for its simplicity in setup compared to other solutions, with most options readily available including user management. The out-of-the-box features streamline the onboarding process.
Powerful CI/CD Pipelines: The Pipelines tool within Azure stands out for its robust capabilities, allowing users to swiftly create pipelines, automate workflows, and easily track their progress effectively throughout the development cycle.
It is being used for complete ci/cd process, used to create pipelines and manage project with ado board.
Pros
Continuous integration
Continuous development
Project management
Cons
Ease of usage
More integration with open source
Navigation
Likelihood to Recommend
It is well suited for creating build pipelines to automate the complete release process and to create testing pipelines. Create and assign different task on ado board. It is also used for code analysis by integrating it with sonar . But it is less user friendly then hira board to mage the scrum and kanban board
The firm as a whole makes use of Azure DevOps Server for project management, with its efficient capability to prioritize and approve project needs. Our IT team uses this top-notch application to streamline project management tasks like code versioning and test script administration and to make sure all of our requirements are met through thorough testing.
Pros
Simple tracking of progress throughout the project.
Perform project management duties with superior ability to set priorities and approve work.
In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
Cons
It doesn't work well with tools from other companies.
Improvements can be made to the user interface to make it more natural to use.
I also think capacity planning may use some fine-tuning.
Likelihood to Recommend
Integrating with Visual Studio makes it easy to see where things stand in terms of different projects' requirements, and the product is great for prioritizing and approving changes as they come up. An easy-to-use tracking and testing system ensures that all criteria are met, making this a great tool for project managers trying to keep their projects within their allotted parameters.
We work according to Agile methodology and Azure DevOps Server (formerly known as TMS) helps us to track and follow the progress of our work efficiently. We use it for version control as well as to review backlog. As we are more of a Microsoft-based company, it helps us a lot since all Microsoft products can be integrated effortlessly with Azure DevOps Server which enhances user experience.
Pros
You can integrate it effortlessly with almost all Microsoft products
Supports Agile and can be used for version control
Bug tracking
Ease of use
Cons
I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
The user interface could have been better
Agile boards can be better
Likelihood to Recommend
Scenarios where Azure DevOps Server is well suited: When the other tools you need to use are also Microsoft products bug tracking version control (although GitHub is better) Agile management backlog management scenarios where Azure DevOps Server is not well suited: When you need to integrate services other than Microsoft owned.
VU
Verified User
Engineer in Information Technology (Information Technology & Services company, 10,001+ employees)
Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments. Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.
Pros
Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
Cons
Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
Likelihood to Recommend
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
VU
Verified User
Engineer in Engineering (Computer Software company, 10,001+ employees)
I work with an agile development team and we use DevOps for capturing and managing user stories and bugs. User stories are categorised into Epics and Features with ease, and it's a very valuable tool for planning and resource management.
Pros
Resource management
Sprint planning
Organising requirements
Cons
Could use a more intuitive interface
On-screen demo/tips would be helpful for new users
Likelihood to Recommend
DevOps is great for managing backlogs, requirements and resources. I don't have enough experience with this sort of software to comment on any downsides, my use is fairly limited but, it's great for my requirements.
VU
Verified User
Consultant in Marketing (Design company, 10,001+ employees)
Managing software development across several phases can be extremely difficult due two it’s complexity. DevOps and CI/CD can help to control this complexity. However, these methodologies need software solutions that suit this agile approach. In this case Microsoft DevOps is the best suite available at the moment. We use Microsoft DevOps end to end to manage the development of a cross-platform mobile application. As said we use the suite end to end. Starting with „Azure Boards“ to derive, document, and manage backlogs; „Azure Repos“ to manage repositories and changes/change requests; ending with automating testing and pipelines with „Azures Testing“ and „Azure Pipeline“. Integration and extensibility features are used for productivity purposes as well. In this way, Azure DevOps brings together all levels of information at code in one single tool. Especially the automation options in the pipeline Tier helped us to automate delivery processes for both platforms (iOS & Android).
Pros
Integration and Extensibility Features.
Pipeline automations.
Configuration and flow of change requests workflows.
Configuration of Boards (backlogs).
Flexibility and ease of use of dashboards.
Change logs of items.
Cons
Expand automation options for iOS pipeline (include further triggers).
Mass handling of backlog items could be improved.
Likelihood to Recommend
The repro Feature “Azure Repros” was especially valuable in our use case as it was very easy to orchestrate the development of several developers via change requests. In this way, tasks/bugs execution was easy to plan and assign via boards and dashboards, and commits were documented in relation to planning objects and reviewed via the four-eye principle. Senior developers were able to oversee and review junior developers' work easily.
We leverage Azure DevOps to manage the Agile backlog of one of our biggest internal platforms. The main functionality is leveraged to track stories and move things along from requirement drafting, to design and right through the development and QA. Some other functionality that is leveraged is the calendar to ensure that we are capturing the agile team's OOOs since most of us are from various orgs/teams throughout the enterprise.
Pros
Organizes tasks with space for all the added context one would need (requirements, design links, etc.)
Ability to capture a backlog of items to better visualize a roadmap to help with planning/prioritizing.
Streamlines the work being done across a large project team with various specialists.
Intuitive to use with minimal learning curve for those new to the tool.
Cons
It is very utilitarian looking, maybe consider a more personable UI aesthetic
Likelihood to Recommend
Our project team uses Azure DevOps to manage the epics and stories associated with one of our biggest internal enterprise-wide tools. It easily captures all stories in a simples way, creating room to include story points (for estimations), requirement notes, and design links (once ready). Additionally, it is simple to move tickets through the various stages of the process making it easy to tell the status of any given task - the ability to color-code tickets has made it exceptionally easy for me to locate the tickets specifically created for my design team to address.
We use Azure DevOps in our business unit as an end to end solution for our ALM / SDLC. We have several organizations with various projects, repos and pipelines. We are following Scaled Agile Framework (SAFe) which is well served by Azure DevOps backlog module. We are happy that we could back trace a cloud release through the pipelines back to the work items in the backlog.
Pros
End to end tracing of released artifacts
Scaled Agile Framework implementation with Azure DevOps backlog
Versatile and powerful pipelines as code
Cons
Ability to automatically link automated tests executions to Test Cases
A better file editor (like VS code) in the git repo UI
Likelihood to Recommend
Well suited:
Large teams developing heterogeneous applications
Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
Company undergoes regular external audits of their SDLC practices
Comprehensive reporting is required
Pipeline templating is required
Many git repositories are needed having to link to a unified backlog
Access to backlog work items and reporting is required for business stakeholders
Azure DevOps Server is being used across the organization as a defect/bug tracking system for IT projects similar to JIRA. The business problems it addresses are mainly related to issue tracking and traceability. There is a multitude of IT deployments at our company, and hence, lots of QA/UAT testing. When defects are captured during these phases, they are logged in Azure DevOps Server and tracked.
Pros
Organization
Defect tracking
Severity
Escalation
Issue/user traceability
Cons
Easier interface.
Less drop downs and tabs.
Email notifications.
Likelihood to Recommend
The best use for Azure DevOps Server is for issue tracking and reconciliation for defects during the QA process.
VU
Verified User
Project Manager in Information Technology (Non-profit Organization Management company, 1001-5000 employees)
Azure DevOps is being used by the entire company. We use that to build our build and release pipeline to continually release our deployment. For our department, we build infrastructure with Terraform and deploy it to the Google Cloud Platform. It solves our problem of not having a CI/CD pipeline. It makes our development cycle much faster.
Pros
It is compatible with so many services. You can deploy to GCP, AWS, and with any kind of developing language.
It has a clear developing logic. You build first and then deploy things to the destination you want.
When you develop with Microsoft products, you can do a lot more.
Cons
There is a little window tells you small jokes and information. It just annoys me.
The UI might use more careful design. it can be confusing when you want to find the thing you want.
There are small things can be added to improve productivity, such as cloning the whole agent job.
Likelihood to Recommend
For companies, especially big companies, when they adopt the way of CI/CD, they need a build pipeline to realize all these. Either they develop websites with languages like Python, Ruby, or C#, or they set up infrastructure with Terraform, Ansible, or Puppet. Azure DevOps integrates everything together and provides a solution that works with all the technologies you use.
VU
Verified User
Engineer in Information Technology (Insurance company, 10,001+ employees)
