Try our new research platform with insights from 80,000+ expert users

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.6
Number of Reviews
16
Ranking in other categories
Software Configuration Management (5th)
Microsoft Azure DevOps
Ranking in Enterprise Agile Planning Tools
1st
Average Rating
8.2
Reviews Sentiment
7.6
Number of Reviews
130
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st)
 

Mindshare comparison

As of November 2024, in the Enterprise Agile Planning Tools category, the mindshare of IBM Engineering Workflow Management is 0.9%, up from 0.9% compared to the previous year. The mindshare of Microsoft Azure DevOps is 42.3%, up from 38.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
 

Featured Reviews

Suvajit Chakraborty - PeerSpot reviewer
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
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

"The most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"Good for managing stories, sprints, hydration and releases."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"Traceability reporting is inbuilt and includes all your requirements."
"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."
"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."
"Work distribution among team members and accountability for completion with a clearer picture."
"It was an all-in-one solution for source code, integrated source control, defect tracking, and project planning."
"The simplicity is very good and the customer experience is also great."
"My first impression of DevOps, after using Jira, is that it has a much better, more intuitive, and more user-friendly interface."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"You get a complete solution with Azure DevOps. You can do everything in one place, starting from requirement gathering until you release the product. It is a reliable, scalable, and handy product."
"The most valuable feature is automation with version control."
"The most valuable feature is the complete integration between test cases, pipelines, and issue management."
"My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good."
"The product is easy to use...It is a stable solution."
 

Cons

"It's becoming less relevant. For example, Maven has evolved, and in its later versions, there are plugins for integrating with source control systems, such as Git-based systems. Support for these plugins is diminishing."
"Lacks ability to customize and reporting can be slow."
"Some administrative tasks are difficult to perform. These could be simplified."
"If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"The solution is very heavily vendor dependent."
"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."
"When you compare with Jira, there is a lack of progress features."
"When converting to DevOps, it was difficult to map."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective. Just like any other tool, it depends on how it is configured. I am not happy with the way it is set up. It is configured more from a development side, and it doesn't necessarily cater to all the other areas that probably need to use it, such as testing data, etc."
"Some things like project management, tasks, progress, and having work progress views require us to use some external tools, or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps."
"The tool has a logical link between epic feature, user story, and task, but when you try to generate a report to show the delivery progress against a feature, it is not easy. To see the percentage completion for a feature or progress of any delivery, it is not easy to draw a report."
"Service monitoring should be improved."
"I'd like to have something better for the test plan."
"When we don't have some permissions, we have to research how to get them."
 

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 main agile features are very expensive."
"There are additional costs for some functionality, such as increased scalability."
"The price is reasonable, but of course, you can find others that are cheaper such as Atlassian."
"I am not aware of any licensing subscriptions for the solution."
"We pay a monthly license for Microsoft Azure DevOps."
"We do not pay licenses for this solution."
"There is a licensing fee of $6/user per month."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
21%
Government
15%
Computer Software Company
12%
Healthcare Company
8%
Manufacturing Company
13%
Computer Software 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?
It's becoming less relevant for us, as we move to cloud-based and more contemporary cloud-based SCM systems such as GitHub. As new JDKs have been released over the years, tooling support in new rel...
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: October 2024.
816,406 professionals have used our research since 2012.