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 use Azure DevOps to coordinate our implementation of development changes and technical processes (configurations / setups) for Business Central. First we create a master document listing all the modifications / extensions from a functional standpoint (master), then have individual tasks with tech design and hours assigned. Each time code with Git is sync'd and merged between one or more developers for the monolith extension app, it is tracked with the task assigned. Finally, as each task is worked through the status is updated and sync'd with the time keeping system (F&O) with PowerAutomate. This gives insight into the progress vs. hours consumed vs. original estimate in real time.
Pros
Utilize Git as a repository to share work between multiple users
Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
Track status of each task
Integrate with Git to utilize branches, merging, approvals, history, etc.
Cons
Have better project management to also be used with functional implementation rather than just development
Have the ability to integrate with a customer facing interface to give visibility into the project status and components.
Smoother integration into time keeping systems such as F&O or Business Central for overall project management reporting / accounting
Likelihood to Recommend
DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.
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 Azure DevOps Services to track our digital project from starting to finish. We need a platform to track all the epics, features, user stories, defects and other relevant task for general agile practice. We also need the platform to be integrate with our repository and pipeline so that we could automate the deployment.
Pros
Customization on fields under user stories
Repository and Peer review can be done easily
Cons
It's hard to track the overall progress of peer review on the new changes
Cannot manage piles of work before starting of development during the problem discovery stage
Likelihood to Recommend
It is suitable for organization looking to automate their software deployment and want a good integration for developer.
Not so well to track items from business' lens as the functionality is heavily IT driven.
We use Azure DevOps for all our digital projects. It helps with organizing features and work with the development team. We have an overview of the sprints and it helps knowing where we are and where we are going.
Pros
Sprint planning
Feature development
Visual representation of digital projects
Cons
New items not showing in board, unless you click on "More items"
The attachment tab is too far away from the details.
You always need to tag people so they get notified when you added comments. It would be nice that it notifies the owner of the item automatically.
Likelihood to Recommend
It's really great for organizing digital projects. I like that you have an historic of everything in the work items. I think it is less appropriate for business analysis. A white board like Miro is best suited in these cases.
VU
Verified User
Strategist in Product Management (5001-10,000 employees)
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.
The application has provided the most suitable agile tools for managing projects in the organization. It tracks closely the task development infrastructure to enhance best implementation practices. My team has been depending on this platform for the last one year and the results have come out with positive ROI. Azure DevOps Services helps each department in performance modelling.
Pros
Monitoring web development process.
Building workflow pipeline.
Customization of dashboards.
Cons
Our goals have been implemented positively.
I have not experienced any missing feature.
Likelihood to Recommend
Our main projects have been developed under the excellent operations of this product. Deployment and testing of new applications has been great step ahead since we deployed this tool. Integration with other Azure services has been successful with top-notch results that have promoted faster production growth. It is easy to learn how this product operates even when you are fresher.
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.
VU
Verified User
Professional in Professional Services (10,001+ employees)
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