We just raised a $30M Series A: Read our story

IBM Engineering Workflow Management OverviewUNIXBusinessApplication

IBM Engineering Workflow Management is #1 ranked solution in top Software Configuration Management tools and #11 ranked solution in top Enterprise Agile Planning Tools. IT Central Station users give IBM Engineering Workflow Management an average rating of 6 out of 10. IBM Engineering Workflow Management is most commonly compared to Jira:IBM Engineering Workflow Management vs Jira. The top industry researching this solution are professionals from a computer software company, accounting for 25% of all views.
What is IBM Engineering Workflow Management?

IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of seamlessly integrated tools: IBM Engineering Workflow Management, IBM Engineering Test Management, and IBM Engineering Requirements Management DOORS Next.

IBM Engineering Workflow Management is also known as IBM Rational Team Concert (IBM ALM), IBM RTC.

Buyer's Guide

Download the Enterprise Agile Planning Tools Buyer's Guide including reviews and more. Updated: October 2021

IBM Engineering Workflow Management 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

IBM Engineering Workflow Management Video

Pricing Advice

What users are saying about IBM Engineering Workflow Management pricing:
  • "Licensing: The solution cost is high and should be brought down to increase competition."
  • "It's an expensive investment to make, so the decision should be driven on individual requirements."

IBM Engineering Workflow Management Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
SC
Manager, Digital Engineering at a manufacturing company with 10,001+ employees
Vendor
Top 20Leaderboard
Great inbuilt traceability reporting; unfortunately, the solution is heavily vendor dependent

Pros and Cons

  • "Traceability reporting is inbuilt and includes all your requirements."
  • "The solution is very heavily vendor dependent."

What is our primary use case?

We are customers of IBM and I'm the manager of digital engineering.

What is most valuable?

There is a value in certain things like traceability, from high level requirements to low level requirements, to a test case, to a test plan, to a work item, to a change request, which is very essential to have for any OEM trying to not just create data, but also enable tracing. All those things are valuable. It's helpful that the traceability reporting is inbuilt and includes all your requirements, management and test management. There are also  certain integrations with code repositories, to a level where you can trace back and see who actually tested it, whether it was a pass or fail, the length of the test and steps behind it. Anyone coming in will automatically know that something has changed.

What needs improvement?

Unfortunately, the solution is very heavily vendor dependent. It requires a strong partnership with IBM, and you rely on them for fixes or access to certain things. There are new fixes all the time and each new fix can bring in a new functionality. The development aspect is not well aligned. There's a requirement tool, a testing tool, a project management tool, a reporting tool. They are separate but all work on one platform although they don't function that way. It can take some time to figure out where the responsibility for a problem lies. They need one team rather than inefficient multiple teams. Another issue is that the solution is not yet supported on Docker.

For how long have I used the solution?

I've been using this solution for over 10 years. 

What do I think about the stability of the solution?

In general, it's stable and you won't have many issues. The issue is that it's always customized, the solution is built for that. Workflows, plugins, extensions are created. This can sometimes create performance issues. 

What do I think about the scalability of the solution?

It's scalable but you can't really containerize it, like a newer solution would support.

How are customer service and technical support?

The technical support is very good and provides value to the solution. It also requires a backend application management team for upgrades, and on the front end, a team to work with users and create processes, templates and workflows. 

How was the initial setup?

The initial setup is not that complex, the documentation gives you all the help you need. User adoption is a problem because it's not as intuitive as JIRA and it requires proper training, to understand where things are aligned. Especially in the RTC part of the CLM, or maybe RQM part. There are sometimes bottlenecks. 

What's my experience with pricing, setup cost, and licensing?

This is not a cheap solution but it does include the standard support that IBM offers through their portal, and the support is good. IBM has multiple licensing models, and there is a floating license model, where you buy a fixed number of licenses and you pay for them no matter what. Then there's a flexible, token-based license, where you have, let's say,100 tokens, and based on your usage, these tokens will be distributed amongst users and you can scale up as necessary. 

What other advice do I have?

I think there are probably better and more nimble solutions available on the market. If a company is starting from scratch, it doesn't really need such a heavy solution. If you're in the automobile, healthcare, aerospace industries and the like, where you have a lot of legacy data, and your requirements are crucial and you might be audited, then you do need to have a system which offers safe certification and a few other things. It should support agile templates and a few other things. 

I rate this solution a seven out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Nitin Kaushik
Quality Assurance at Varroc Lighting System
Real User
Top 20
Gives us work distribution among team members, but teams need clearer pictures of resource availability in charts and dashboards

Pros and Cons

  • "Work distribution among team members and accountability for completion with a clearer picture."
  • "Teams need clearer pictures of resource availability in charts and dashboards along with plans."

What is our primary use case?

We are mainly using it for project planning, resource engagement, load distribution, and work allocation. Work distribution among team members and accountability for completion with a clearer picture. This represents the outcome clearly, along with measures to be taken, if any.

How has it helped my organization?

It has improved our organization up to an extent, but it certainly has a lot of areas for improvement related to resource management. Teams need clearer pictures of resource availability in charts and dashboards along with plans. Additionally, the non-availability of a "contributor list" both in plan views and JRS restricts the usability which would have played a greater role for our teams.

What is most valuable?

  • Plan views
  • Reporting (JRS)
  • A clear picture of engagement
  • Resource orientation
  • Chartered views

Plans clearly represent the team's availability with load balance, if any. Reporting in certain formats along with live data is certainly helpful to present to higher management without the need to generate them repeatedly.

What needs improvement?

A lot of room for improvement:

  • Report generation (.xls, .pdf) from filters.
  • "Contributor list" and "enumeration list" in plans and reporting.
  • Extending JavaScript support.
  • Team availability calendar on dashboard and plans.
  • Automatic subscription of users to dedicated types of work items, but not all of them.
  • Plan modifications from widgets to dashboards, if the option is displayed.

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

The application is highly stable, though the environment stability depends on the architecture used for deployment. Considerations should be given during architecture design, review, and planning sessions.

What do I think about the scalability of the solution?

The solution is highly scalable.

Which solution did I use previously and why did I switch?

I have worked with Rational Synergy and Rational Change in the system development domain. It certainly has all the added advantages over its predecessors.

How was the initial setup?

Setup is straightforward. However, there are too many possible permutations and combinations, though it allows for good flexibility.

Setup will include simple application deployment, database, application server, and LDAP configuration.

What about the implementation team?

Implementation was the vendor team in collaboration with an in-house team. It was quite a learning experience, although the process was smooth. It needed considerable thought for deployment, and consideration for scalability and performance, similar to any other solution.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

We evaluated PTC Integrity and TFS.

What other advice do I have?

Overall, it is a good solution. It is flexible and adaptable.

Consider reviews before investing a fortune on it.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
Download our free Enterprise Agile Planning Tools Report and find out what your peers are saying about IBM, Broadcom, Microsoft, and more!