Azure DevOps vs. IBM Cloud Continuous Delivery

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure DevOps
Score 8.0 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
IBM Cloud Continuous Delivery
Score 8.2 out of 10
N/A
IBM Cloud Continuous Delivery, available on IBM Cloud, allows users to provision an integrated toolchain using customizable, shareable templates with tools from IBM, third parties and open source. Automate builds and tests with Tekton-based delivery pipelines, and control quality with analytics.
$0
Pricing
Azure DevOpsIBM Cloud Continuous Delivery
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Lite
$0.00
Professional
$35.00
Authorized user per month
Offerings
Pricing Offerings
Azure DevOpsIBM Cloud Continuous Delivery
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Azure DevOpsIBM Cloud Continuous Delivery
Considered Both Products
Azure DevOps
Chose Azure DevOps
This is the first platform our dev team shared to us so I can't really compare but overall its such a great tool to have even if you are not from tech or dev team.
Chose Azure DevOps
We would use App Center for distributing our app to testers, and we could implement the same functionality as was handled by App Center, and as far as I remember we even had some automatic conversion of our jobs from App Center. After the conversion, we could see that Azure …
Chose Azure DevOps
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as Monday.com and doesn't work as well OOTB as ServiceNow SPM however.
Chose Azure DevOps
It is a similar tools with its pros and cons but does not really a differential - I would say it does the same but its own way, sometimes better, other times worst. It is a matter of preference or demands that come from superior decisions, so you just have to take it.
Chose Azure DevOps
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing …
Chose Azure DevOps
Azure DevOps provides integrated environment vs Jira is dependent on third party for couple of features
Chose Azure DevOps
The moment I have been working with this tool everything has benn operating efficiently. The software development process has borne positive results under scalable environment. The cost of running Azure DevOps Services us much lower as compared to other tools in the market. It …
Chose Azure DevOps
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, …
Chose Azure DevOps
Jira is super clunky and doesn't behave in a modern fashion. monday.com is too flexible and doesn't provide enough feature set. AWS is the most competitive, but it's hard to wrap your brain around all of the features and offerings provided by amazon. ADO does a better job of …
Chose Azure DevOps
Azure DevOps has a drag and drop editor so that you can quickly drag build steps into a build or release pipeline. This is much faster than looking up the correct yaml syntax. Additionally, its support for Microsoft and Azure is great. If you're on the .net stack or you use …
Chose Azure DevOps
Azure DevOps has more services and better integration with other tools. When it. Comes to the overall software development process management ecosystem.
Chose Azure DevOps
As a cloud services user of Azure, using Azure DevOps made sense because it has the most support tailored for Azure ecosystem.
Chose Azure DevOps
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or …
Chose Azure DevOps
Graphically it overtakes the grade of traceability of artifacts delivered to environments More user-friendly to orchestrate the deliveries.
Chose Azure DevOps
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.
Chose Azure DevOps
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.
Chose Azure DevOps
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 …
Chose Azure DevOps
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 …
Chose Azure DevOps
Azure DevOps is a completed product and ecosystem. It offers a robust ecosystem that does everything that is needed. The above products do lack features like pipelines tasks, third-party integrations. Besides all cloud benefits, the main advantage of Azure DevOps Services …
Chose Azure DevOps
Currently, we use both products, however, we use more the Atlassian suite. We have started recently using Azure DevOps for specific implementations and projects. We don't have any plan yet to migrate all our projects to Azure DevOps, we may in the next couple of years. …
Chose Azure DevOps
We tested alternatives for Azure DevOps over time. We tested GitHub a while ago and back then lack of some features that now hast, like the project boards and private repositories. We will check GitHub next year.

We also tested AWS CodeCommit and found it very cryptic, …
Chose Azure DevOps
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software.
On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
Chose Azure DevOps
The greatest strength of Azure DevOps Services (formerly VSTS) is that it's a one-stop solution for all agile project management instead of setting up bits of different software put together for each and every need. Azure DevOps Services (formerly VSTS) has a great ecosystem …
Chose Azure DevOps
I prefer Azure Devops over all other code repository / ci/cd systems that I've used in the past. All features are integrated into a single service (back log, repo mgmt, deployment pipelines, artifacts, etc.). The tools are easy to use and super powerful.
Chose Azure DevOps
Our company is already using a lot of Azure services and it makes more sense to start using Azure DevOps Services (formerly VSTS) when we needed a CI/CD tool. We tested different features of Azure DevOps Services (formerly VSTS) and found out that the build and release …
IBM Cloud Continuous Delivery
Chose IBM Cloud Continuous Delivery
Its better than them
Chose IBM Cloud Continuous Delivery
Best fit for IBM Cloud and IBM Hybrid cloud strategy. Very well suited for RedHat Openshift and cloud-native build packs. Complementary solution for Enterprise Java workloads transformation and modernization journey such as java microservices development lifecycle and also …
Chose IBM Cloud Continuous Delivery
We chose IBM Cloud Developer Tools for multiple reasons. Cost, current infrastructure vendor list, and Cloud Operations team experience were key driving factors for us. Palo Alto's Prisma Cloud product was slick for sure but we found it more difficult to deploy and integrate …
Chose IBM Cloud Continuous Delivery
IBM Cloud developer tools had good support for mobile and web based applications and seemed relatively easy to integrate to our applications. We have other IBM tools so it had a slight edge over others when we compared.
Chose IBM Cloud Continuous Delivery
Google Cloud AI provides better speech-to-text integration for applications in which the word recognition ability is far good.
Chose IBM Cloud Continuous Delivery
IBM Cloud Developer Tools stack up against Visual Studios and other integration suites, with an agnostic approach. IBM Cloud Developer tools integrate seamlessly with your existing stack to augment and accelerate data science and analytics projects at large. Tools are designed …
Chose IBM Cloud Continuous Delivery
This is recommended over other applications as it has a continuous delivery for non-mission critical applications also which has simple proof of concepts and this is reliable. Also, the integration to different platforms along with cloud implementation is an add-on. The ease of …
Chose IBM Cloud Continuous Delivery
IBM Cloud Developer Tools is way easier than Jenkins and most of the features Jenkins has are not useful for us and the features we wanted were absent ButIBM Cloud Developer Tools saved our lives and is perfect in all aspects as we can easily develop and deploy. The only thing …
Chose IBM Cloud Continuous Delivery
Both competitors listed work in a similar manner; you can automate the deployment of servers using configuration files and the command line. The difference is that Ansible and Terraform are provider-agnostic, meaning you can use them for other hosting providers as well (AWS, …
Chose IBM Cloud Continuous Delivery
Mainly, AWS offers 5G services which are futuristic. AWS has More products than IBM Cloud & it offers High Parallel Performance & Computing. Better global coverage than IBM Cloud & Rigid SLAs with credit compensation

Coming to Microsoft Azure, its user interface is very easy to …
Chose IBM Cloud Continuous Delivery
Eclipse with IBM Cloud Foundry and Kubernets we used to develop application in on premises and deployed into the cloud. And we created containers, created many projects and deployed into the cloud by using Continuous Delivery in IBM Cloud. Great service and great support. IBM …
Chose IBM Cloud Continuous Delivery
There's not really a technical background on the decision of using IBM Cloud Continuous delivery. Our CTO assisted to a conference where IBM was promoting their services and offering a free tier. As in that instance the company was starting, every free tier offering was well …
Chose IBM Cloud Continuous Delivery
CI/CD is much more user friendly than Jenkins.
It better integrates to IBM Cloud features.
On the other side, Jenkins deployed in a VM or better, on a K8S cluster is a less expensive solution.
Chose IBM Cloud Continuous Delivery
I find IBM Cloud Continuous Delivery service way easier to set up compared to Travis CI. The visual interface helps you navigate throughout the service effortlessly. I used Travis CI 2 years ago, although it wasn't complicated, I took more time to create and set up an instance …
Features
Azure DevOpsIBM Cloud Continuous Delivery
Project Management
Comparison of Project Management features of Product A and Product B
Azure DevOps
-
Ratings
IBM Cloud Continuous Delivery
8.5
Ratings
13% above category average
Task Management00 Ratings8.20 Ratings
Resource Management00 Ratings8.00 Ratings
Gantt Charts00 Ratings8.30 Ratings
Scheduling00 Ratings8.80 Ratings
Support for Agile Methodology00 Ratings8.00 Ratings
Support for Waterfall Methodology00 Ratings7.60 Ratings
Document Management00 Ratings8.70 Ratings
Email integration00 Ratings8.60 Ratings
Mobile Access00 Ratings8.70 Ratings
Timesheet Tracking00 Ratings8.70 Ratings
Change request and Case Management00 Ratings8.60 Ratings
Budget and Expense Management00 Ratings8.30 Ratings
Search00 Ratings9.00 Ratings
Visual planning tools00 Ratings9.00 Ratings
Agile Development
Comparison of Agile Development features of Product A and Product B
Azure DevOps
-
Ratings
IBM Cloud Continuous Delivery
7.6
Ratings
2% below category average
DevOps Tool Integrations00 Ratings8.60 Ratings
Code Review00 Ratings7.40 Ratings
Code Collaboration00 Ratings7.70 Ratings
Velocity Calculation00 Ratings6.80 Ratings
Dependencies and Blockers00 Ratings7.20 Ratings
Best Alternatives
Azure DevOpsIBM Cloud Continuous Delivery
Small Businesses
GitHub
GitHub
Score 9.2 out of 10
GitLab
GitLab
Score 8.8 out of 10
Medium-sized Companies
GitHub
GitHub
Score 9.2 out of 10
Planview AgilePlace
Planview AgilePlace
Score 7.9 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.4 out of 10
Planview AgilePlace
Planview AgilePlace
Score 7.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure DevOpsIBM Cloud Continuous Delivery
Likelihood to Recommend
8.8
(0 ratings)
8.5
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
9.1
(0 ratings)
Usability
8.3
(0 ratings)
8.2
(0 ratings)
Support Rating
8.1
(0 ratings)
7.0
(0 ratings)
Implementation Rating
10.0
(0 ratings)
-
(0 ratings)
User Testimonials
Azure DevOpsIBM Cloud Continuous Delivery
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.
Read full review
It provides a cloud-based integrated development environment that integrates with other IBM Cloud services to provide a streamlined development workflow. This includes real-time collaboration and code sharing capabilities, making it easy for teams to work together on projects. This feature is very useful for our app to maintain the code
Read full review
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.
Read full review
  • It contains the deployment templates which are much more time saving and is of great use.
  • This has the integration of the Cloud applications which makes the work much more convenient.
  • This is flexible when it comes to development, deployment, and delivery.
  • [It] also has a much more reasonable pricing.
  • Provides space for the data storage.
  • [IBM Cloud Developer Tools] also can support many useful tools.
Read full review
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.
Read full review
  • Its price is quite high and this made it unsuitable for us as we cannot afford such high rates.
  • Its Setup takes much longer time and this is frustrating.
  • Its interface needs to be improved and easy even for the Newbies.
Read full review
Likelihood to Renew
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Read full review
It's a great platform to develop, run, test and deploy the applications easily. And it makes very easier and secure the implementation of continuous delivery process. For first time and experts also can use this service so easily. Great service provided by the IBM Cloud Continuous Service. There are more services that helps a lot to work on it. Thanks a lot.
Read full review
Usability
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
Read full review
Nothing special to say : the UX is clear and simple.
Read full review
Support Rating
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Read full review
In more than a year using the IBM Cloud Continuous Delivery tool, I haven't had any major complaints or problems. However, in the last month, IBM suffered from a couple of problems through several of its services, and for a short period of time, I couldn't deploy successfully my projects. The problem was brief and was quickly fixed.
Read full review
Implementation Rating
Was not part of the process.
Read full review
No answers on this topic
Alternatives Considered
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as monday.com and doesn't work as well OOTB as ServiceNow SPM however.
Read full review
We chose IBM Cloud Developer Tools for multiple reasons. Cost, current infrastructure vendor list, and Cloud Operations team experience were key driving factors for us. Palo Alto's Prisma Cloud product was slick for sure but we found it more difficult to deploy and integrate with our current environment and applications
Read full review
Return on Investment
  • Increased dev team efficiency through more streamlined development processes and task automation.
  • Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
  • Better collaboration between the dev team, business analysts, and agile project managers.
Read full review
  • This has made the configuration files much easier to access.
  • Has made the commands more logical as well as easy for use and learning.
  • Contains great AI capabilities
  • The documentation needs improvement.
  • Error received from commands are pretty hard to understand.
Read full review
ScreenShots