No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Engineering Lifecycle Management (ELM) vs Microsoft Azure DevOps comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 3, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Engineering Lifecycle M...
Ranking in Application Lifecycle Management (ALM) Suites
11th
Average Rating
7.2
Reviews Sentiment
6.1
Number of Reviews
20
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Ranking in Application Lifecycle Management (ALM) Suites
2nd
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
139
Ranking in other categories
Release Automation (1st), Enterprise Agile Planning Tools (1st)
 

Mindshare comparison

As of September 2026, in the Application Lifecycle Management (ALM) Suites category, the mindshare of IBM Engineering Lifecycle Management (ELM) is 3.5%, down from 3.8% compared to the previous year. The mindshare of Microsoft Azure DevOps is 9.8%, down from 13.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites Mindshare Distribution
ProductMindshare (%)
Microsoft Azure DevOps9.8%
IBM Engineering Lifecycle Management (ELM)3.5%
Other86.7%
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

LasseMikkonen - PeerSpot reviewer
CEO at byte
Has supported highly regulated documentation needs but requires a modernized user experience
I think usability should be improved in IBM Engineering Lifecycle Management (ELM) as the top priority. If you look at the UI, it was literally designed ten years ago, and even at the time it was introduced, it was already somewhat outdated. Even though it is a professional tool, nowadays people expect at least some level of usability from their tools, regardless of how professional the task is. Additionally, if you want to utilize it on a wide scale in an organization, you need to train every person to use it. There is always a threshold for new users to start using it.
Bharadwaj Deepak Mohapatra - PeerSpot reviewer
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Have built reliable end-to-end pipelines and streamlined cloud provisioning through consistent collaboration practices
I am currently working with open-source tools such as Jenkins for my main CI/CD pipeline, and for enterprise clients, I am using Microsoft Azure DevOps CI/CD pipeline. For other clients, I have also implemented CI/CD YAML pipelines through GitLab CI/CD workflow and GitHub Actions. I am creating the end-to-end CI/CD pipeline from development to deployment and monitoring all of this. Azure Boards is easier than Jira for my understanding because there are very easy points to manage the Agile methodology which we work on. Because it is a GUI, sometimes the process may take a few minutes more than the CLI process since the backend is running the exact CLI, but we are commanding through the GUI. There is definitely a time lag, but it is more secure. Microsoft Azure DevOps pipelines work very seamlessly rather than other CI/CD pipelines, as of my understanding. The downside is that the process may take more time when deploying some clusters, Kubernetes, Azure AKS service, or some vast microservice architecture deployments. There may be a little bit of lag I feel, though I cannot tell very strictly that this is a disadvantage, but sometimes it takes a little more time than other cloud infrastructures. All the major things are done by GUI, which is somewhat a little slow. However, if considering automations, process, monitoring, and provisioning, then it is the best cloud service across all the other service providers. Our implementation is a hybrid cloud. Microsoft Azure DevOps is definitely easily scalable. I have worked on many Kubernetes infrastructures and microservice deployments, and I have seen that replication is very good because it is very easy. The replication process is very straightforward. I definitely advocate for using less code because it is very time-consuming. If using GCP or Amazon Web Service, there is more interaction related to work over the CLI process. In terms of Microsoft Azure DevOps, there are many things done by the GUI, which is the best part.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It has improved relations with the customer through the Product Backlog and prioritizing their needs before launch."
"It is very flexible and powerful for creating workflows, and in fact, it is the best solution available for creating workflows."
"It is relatively easy to use and user-friendly once the setup is complete."
"Abilities to share ideas in terms of tasks, lifecycle traceability from requirement to development to testing and designs gives a clear understanding of the system."
"We have something called the GC (global configuration), which is a unique feature compared to any other competitor we have in the ALM space."
"The most valuable feature is the reporting of the CPU usage on the dashboard."
"It's easy to use."
"You can customize the board according to your needs."
"If you're looking for a cross-platform solution that end-to-end does everything in the development life cycle, this would be a very good solution for you."
"They have been lately adding features to the services on a regular basis. Every two weeks, they are adding functionality to Azure DevOps Services to match it with what Azure DevOps Server or on-prem would offer. So, we continue to get more robust functionality. My favorite right now is that they are starting to open up the API availability within Azure DevOps Services. Another thing that I like about Azure DevOps is that you can use it with any of the products that are on the market. You can integrate it with Jenkins and other open-source products to complete that fully functional CI, CD, CT, CM, and CS pipeline. It continues to enhance."
"Technical support has been excellent; on that side, Microsoft is very good, and the customer support of Microsoft has really improved this past year, and on the cloud side also we are very satisfied because it offers very good support."
"It is stable, and we have had no issues with it."
"Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap."
"I found the Kanban board to be the most useful for my needs."
"The solution's most valuable features are backlog management, build release pipeline, and testing."
"The most valuable feature in automating our build and release processes with Azure DevOps is the scheduling capability."
 

Cons

"I think nowadays people are getting into Jira and other tools. What is happening is, this solution is becoming more traditional, whereas Jira and other tools are more attractive for the new users to learn and start using because of the graphical interfaces."
"The interconnectivity between packages is a major support problem and can be improved."
"Improvement is needed in bridging DNG and Rhapsody and vice versa for better data exchange from both sides with some trigger technologies."
"The stability of this solution can be improved."
"I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply."
"This is not a very stable solution. We have to reboot frequently."
"One of the complaints from users is that they have to click buttons too many times for just a simple task. Changing this would lead to a better user experience."
"The reporting functionality needs to be improved."
"A notable improvement would be adding more notifications."
"The solution's roadmap and Gantt charts could be improved."
"Testing is very important. Microsoft Azure DevOps tests very well. However, DevOps teams need to be aware of what they are impacting when someone updates anything on the system."
"One thing I would note is that it's hard to know what is included or not in the product."
"All of the tests of the applications are done on the mobile or web interface and it could be improved."
"I would like to see better interoperability with the agile scaling frameworks."
"It is essential that you get buy-in from the top management down to everyone in the pipeline."
"Improvements can be made mostly on the team management aspects."
 

Pricing and Cost Advice

"IBM Rational ALM has both monthly and yearly licensing options."
"We have a contract, but I am not aware of the details."
"The price of the solution could be reduced. Many of our customers are not using all the features and this could be why our clients feel the price is too high."
"The solution is not cheap."
"This product is a little expensive and we had to pay extra to have them set it up for us."
"The costs are moderate and justify the value provided."
"The licensing costs are reasonable."
"There is a license for this solution."
"It has an annual subscription. It can be cheaper for partners. Many open-source products are available in the market, and it would be great if they can be a little bit more competitive in terms of pricing. A lot of startups are looking for an open-source, free, or cheap solution. If they can accommodate such requirements, it will be good for the product in the long run."
"The cost is quite affordable."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"It is a subscription model and I only pay for what I use."
"The solution is expensive."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
16%
Government
9%
Comms Service Provider
9%
Outsourcing Company
8%
Manufacturing Company
13%
Financial Services Firm
9%
Government
7%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise12
By reviewers
Company SizeCount
Small Business44
Midsize Enterprise28
Large Enterprise70
 

Questions from the Community

What needs improvement with IBM Rational ALM?
I think usability should be improved in IBM Engineering Lifecycle Management (ELM) as the top priority. If you look at the UI, it was literally designed ten years ago, and even at the time it was i...
What is your primary use case for IBM Rational ALM?
For companies in heavily regulated industries who are doing product development, IBM Engineering Lifecycle Management (ELM) is a good tool. It helps them create documentation that satisfies auditors.
What advice do you have for others considering IBM Rational ALM?
I would rate IBM Engineering Lifecycle Management (ELM) eight out of ten overall, but it is of course difficult to tell compared to what. If it is compared to tools for advanced requirements manage...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
Microsoft Azure DevOps: what is your experience regarding pricing and costs ?
I am not much involved in the pricing, licensing, or costing aspects. However, one of my colleagues is involved in the licensing and pricing part, and it is very efficient. We are Microsoft Gold Pa...
 

Also Known As

IBM Engineering Rhapsody, Rational ALM, MKS
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

Tennis Australia, WeCloud AB, Port Otago Limited, Logicalis US, Valmer, The Chevrolet Volt, Ashurst
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about IBM Engineering Lifecycle Management (ELM) vs. Microsoft Azure DevOps and other solutions. Updated: September 2026.
913,683 professionals have used our research since 2012.