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

IBM Engineering Workflow Management vs JIRA Portfolio 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)
JIRA Portfolio
Ranking in Enterprise Agile Planning Tools
4th
Average Rating
8.2
Number of Reviews
57
Ranking in other categories
No ranking in other categories
 

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 JIRA Portfolio is 1.2%, down from 2.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
 

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.
Gary Craven - PeerSpot reviewer
Jan 4, 2024
Powerful, flexible solution with a bit of a learning curve
The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve. It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly. Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.

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."
"The most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"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."
"Good for managing stories, sprints, hydration and releases."
"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."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"The backlog view feature is highly valuable"
"In a PC environment, it is quite stable."
"JIRA Portfolio has many wonderful features."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"Portfolio's most valuable features are that it's user-friendly and customer-centric."
 

Cons

"Lacks ability to customize and reporting can be slow."
"Some administrative tasks are difficult to perform. These could be simplified."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"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."
"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."
"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."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"We are based in India; I would like the product to integrate local pricing. We earn in rupees but spend in dollars. Its pricing could also be lowered."
"There is room for improvement in terms of scalability."
"Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up."
"Requires some effort to insert functionalities and that could be simplified."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"JIRA Portfolio's configuration management could be improved."
 

Pricing and Cost Advice

"It's an expensive investment to make, so the decision should be driven on individual requirements."
"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."
"Licensing: The solution cost is high and should be brought down to increase competition."
"I've heard IBM Engineering Workflow Management is more expensive than other tools."
"I use the free version for personal use."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight."
"When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard they increased a lot, so we decided to stop using it."
"The price could be improved."
"We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
"The pricing continues to get higher."
"The price is reasonable"
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
814,649 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
20%
Government
15%
Computer Software Company
11%
Healthcare Company
8%
Financial Services Firm
22%
Computer Software Company
16%
Manufacturing Company
11%
Government
6%
 

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...
What do you like most about JIRA Portfolio?
The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
What is your experience regarding pricing and costs for JIRA Portfolio?
When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard t...
What needs improvement with JIRA Portfolio?
The tool needs to improve its speed and response time.
 

Also Known As

IBM Rational Team Concert (IBM ALM), IBM RTC
Portfolio for JIRA
 

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
Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
Find out what your peers are saying about IBM Engineering Workflow Management vs. JIRA Portfolio and other solutions. Updated: July 2024.
814,649 professionals have used our research since 2012.