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

IBM Engineering Workflow Management vs Visual Studio Team System comparison

 

Comparison Buyer's Guide

Executive Summary

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 Workflow Ma...
Ranking in Software Configuration Management
3rd
Average Rating
6.8
Reviews Sentiment
6.3
Number of Reviews
17
Ranking in other categories
Enterprise Agile Planning Tools (11th)
Visual Studio Team System
Ranking in Software Configuration Management
4th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
14
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Software Configuration Management category, the mindshare of IBM Engineering Workflow Management is 3.9%, up from 3.0% compared to the previous year. The mindshare of Visual Studio Team System is 2.1%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Software Configuration Management
 

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.
Mustapha Sedki Ben Romdhane - PeerSpot reviewer
A scalable and efficient solution that can be used to perform tasks involved in developing information systems
We can use the tool to perform limited tasks in developing information systems The product is efficient. It is an accepted tool globally. The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with…

Quotes from Members

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

Pros

"Traceability reporting is inbuilt and includes all your requirements."
"Good for managing stories, sprints, hydration and releases."
"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."
"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."
"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."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"The tool provides traceability and reporting, which are important for compliance and measuring progress."
"Visual Studio Team System is the most powerful IDE available in the market."
"The solution is pretty stable."
"The solution is scalable, stable and has allowed us to upgrade our frameworks."
"The product is efficient."
"IntelliSense and CodeLens are helpful because they can show you details about your function, such as how many times it is called from other places within the code."
"The solution has a good framework that is user friendly and scalable."
"The most valuable feature is the code management, where there is sharing of code for developers and it is distributed within the organization."
"The solution is very stable."
 

Cons

"Some administrative tasks are difficult to perform. These could be simplified."
"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."
"I would rate the IBM Engineering Workflow Management a seven or an eight. I am leaning closer to seven based on a couple of items I mentioned that I would like to see or know more about, such as improved reporting."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"Improved graphics in terms of metrics and connectivity to SharePoint from Microsoft products would be beneficial."
"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."
"Lacks ability to customize and reporting can be slow."
"The stability of the product could be better."
"I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see."
"The overall customer support needs to improve."
"When you go into the front-end, the web portal, if, for example, you pick up an issue, it would be ideal if the branch was automatically created in the repository. Right now, this isn't the case."
"The product should be priced better."
"The technical support could be better."
"The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms."
"The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved."
 

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."
"It's an expensive investment to make, so the decision should be driven on individual requirements."
"I've heard IBM Engineering Workflow Management is more expensive than other tools."
"Licensing: The solution cost is high and should be brought down to increase competition."
"There is no fee for the solution's community version."
"The tool's licensing costs are yearly."
"It is an open-source product from Microsoft."
"You can choose pricing from a variety of options. I would rate the product's pricing a six out of ten."
"The price could be better."
report
Use our free recommendation engine to learn which Software Configuration Management solutions are best for your needs.
859,129 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
18%
Government
12%
Computer Software Company
11%
Healthcare Company
8%
No data available
 

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?
Improved graphics in terms of metrics and connectivity to SharePoint from Microsoft products would be beneficial.
What needs improvement with Visual Studio Team System?
The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with internal and external processes.
What is your primary use case for Visual Studio Team System?
We can use the tool to perform limited tasks in developing information systems.
 

Also Known As

IBM Rational Team Concert (IBM ALM), IBM RTC
No data 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
Bluegarden A/S, Tracasa, Rabobank Group, Borusan Otomotiv, Arelik, Alfa Bank
Find out what your peers are saying about IBM Engineering Workflow Management vs. Visual Studio Team System and other solutions. Updated: June 2025.
859,129 professionals have used our research since 2012.