IBM Engineering Workflow Management vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

IBM Engineering Workflow Ma...
Ranking in Enterprise Agile Planning Tools
10th
Average Rating
6.8
Number of Reviews
15
Ranking in other categories
Software Configuration Management (5th)
Microsoft Azure DevOps
Ranking in Enterprise Agile Planning Tools
1st
Average Rating
8.2
Number of Reviews
127
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st)
 

Market share comparison

As of June 2024, in the Enterprise Agile Planning Tools category, the market share of IBM Engineering Workflow Management is 1.2% and it increased by 68.1% compared to the previous year. The market share of Microsoft Azure DevOps is 41.9% and it increased by 13.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
Unique Categories:
Software Configuration Management
2.8%
Application Lifecycle Management (ALM) Suites
20.0%
Release Automation
39.3%
 

Featured Reviews

Suvajit Chakraborty - PeerSpot reviewer
Oct 31, 2023
Offers good traceability elements but UI needs improvement
There is room for improvement in the UI. The UI has to improve a lot compared to the competitive tools, like Atlassian Jira, for example. It's very easy to use. It is easy to manage and easy to use. Anybody can learn it right quickly and start with it. But IBM ELM is something where somebody has to have good knowledge, training, and understanding and then only start using it. But there's a big known knowledge curve for IBM ELM. But once that is there, it's normally; organizations do have their own internal team to basically manage it IBM ELM portfolio, the tool chain. So if they have internal teams who are doing it for quite some time, not something new, then it is definitely better. But if there's if somebody is starting new, definitely there is a knowledge curve time it can take at least a year or maybe a couple of years before they can start realizing the benefits.
Akshat Prakash - PeerSpot reviewer
Apr 10, 2024
Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling
My company has experienced benefits from using it or from recent updates in Azure Pipelines. For instance, we can manage different code versions from the same repository across different environments. We also use feature flags; the code is deployed, but the feature can be made visible to the end user at a later time. Additionally, as part of the deployment, we integrate automated and regression testing, which stops the deployment if testing fails, thus preventing regression bugs. This saves time and increases productivity by reducing the need for manual testing. Lastly, it integrates with the project management aspects, allowing us to link code deployments with project milestones. Azure DevOps supported our shift towards DevOps culture or practices. We shifted to the cloud environment and started migrating from our data centers about eight or nine years back. It has been a long journey. However, we have used Azure DevOps for almost five to six years in every project. We also use automation testing in Azure, so we have an integrated test suite that allows us to perform functional and regression testing effectively via the Azure DevOps system.

Quotes from Members

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

Pros

"Good for managing stories, sprints, hydration and releases."
"Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data."
"Traceability reporting is inbuilt and includes all your requirements."
"The most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"Work distribution among team members and accountability for completion with a clearer picture."
"The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS."
"There are a lot of helpful features available for tracking dependencies."
"It's got something that you won't find in other products."
"Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support."
"It's a complete solution that has everything you need."
"The product is easy to use and very stable."
"Azure enables us to create a staging environment through to a production environment in an easier way and then get the code and run that."
"The product is easy to use...It is a stable solution."
 

Cons

"We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it."
"Some administrative tasks are difficult to perform. These could be simplified."
"Lacks ability to customize and reporting can be slow."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load."
"The solution is very heavily vendor dependent."
"I would like to see improvement in the metrics and the dependencies."
"There could more integration with other platforms."
"I have not been able to use the integration with automation features, such as test management automation, with a framework that is written in Java."
"The optimization feature in Microsoft Azure DevOps needs improvement. Control over multiple projects could also be improved."
"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."
"Right now, they tend to have a limit of 1,000 tasks per sprint, and some of their web-based boards, such as the Kanban boards, no longer display tasks. Once you hit over a certain number of task limits, you need to increase those limits."
"They have brought a lot of new collaboration features in the latest version. We haven't used those features, but they should continue to expand it more on the collaboration front so that two developers can look at the code and work at the same time. It will be helpful for working from home."
"I would like to see a bit more project tracking."
 

Pricing and Cost Advice

"It is not a free tool. We use a token-based licensing model, which is specific to IBM. The cost per token is around $115-$120."
"I've heard IBM Engineering Workflow Management is more expensive than other tools."
"It's an expensive investment to make, so the decision should be driven on individual requirements."
"Licensing: The solution cost is high and should be brought down to increase competition."
"The price is reasonable for the solution."
"The main agile features are very expensive."
"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 solution is expensive."
"Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users."
"Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective."
"Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
787,061 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
22%
Government
13%
Computer Software Company
10%
Financial Services Firm
8%
Computer Software Company
13%
Manufacturing Company
12%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about IBM Engineering Workflow Management?
We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data.
What is your experience regarding pricing and costs for IBM Engineering Workflow Management?
I've heard IBM Engineering Workflow Management is more expensive than other tools. On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.
What needs improvement with IBM Engineering Workflow Management?
If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load. We have already created some cases with IBM, and they are looking into it.
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...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
 

Also Known As

IBM Rational Team Concert (IBM ALM), IBM RTC
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Learn More

Video not available
 

Overview

 

Sample Customers

Telstra Corporation, Visteon, Atos SE, Panasonic Automotive Systems, IBM Global Technology Services, CareCore National, JTEKT Corp., ItaÒ BBA, Avea, CACEIS, Danske Bank Group, APIS IT
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about IBM Engineering Workflow Management vs. Microsoft Azure DevOps and other solutions. Updated: May 2024.
787,061 professionals have used our research since 2012.