Azure DevOps Services vs. IBM Cloud Continuous Delivery

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.

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

Incentivized

• 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.

Incentivized

• 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.

Incentivized

• 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

Incentivized

• 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.

Incentivized

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.

Incentivized

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.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

Nothing special to say : the UX is clear and simple.

Incentivized

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.

Incentivized

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.

Incentivized

Was not part of the process.

Incentivized

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 interfaces, I feel it would be a complete project management system.

Incentivized

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

Incentivized

• 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.

Incentivized

• 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.

Incentivized