DevOps Tech Lead at a computer software company with 11-50 employees
Real User
Top 20
Aug 29, 2024
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 releases lags behind. Also, Maven SCM 2.0.0 has deprecated the provider "maven-scm-provider-jazz". So there is some wonder about the future of the product. It may be perfect for big companies that are more formal and need process/audit/documentation/access control.
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.
Manager, Digital Engineering at Harman International
Real User
Oct 31, 2023
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.
Vice President Delivery - Enterprise Solutions and Infrastructure Services at a financial services firm with 10,001+ employees
Real User
Nov 18, 2021
One of the downfalls of this product is that we are not able to customize it for our specific requirements. I'm not sure whether that's an issue with the product or with the company's implementation.
Learn what your peers think about IBM Engineering Workflow Management. Get advice and tips from experienced pros sharing their opinions. Updated: May 2026.
Manager, Digital Engineering at Harman International
Real User
Feb 24, 2021
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.
Applications Developer Specialist at a comms service provider with 1,001-5,000 employees
Real User
Sep 24, 2019
We are currently using version four, but we looked at versions five and six and they are getting better and better. They're making planning easier. In version six they have something called a Quick Planner which would be nice to have in our version. In fact, if many of the features they have in five and six could be offered in four as well, that would be beneficial to us. Some administrative tasks are difficult to perform. These could be simplified. For example: setup sprint/iteration period - start and end. It may be simple to have a button to End Sprint / Start new Sprint and the application handle setup and definition. Another example in user holiday's handling to have one click to apply general holiday that applies to all team members.
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.
IBM Engineering Workflow Management offers change and task management with seamless integration into development processes. It supports compliance and progress tracking and provides collaborative tools, configuration management integration, and isolated sandboxes.IBM Engineering Workflow Management aids Agile software development by facilitating project and sprint planning, load distribution, task tracking, and more. It offers comprehensive reporting, traceability, and sophisticated resource...
IBM Engineering Workflow Management can be improved by enhancing its pricing structure, specifically the cost and licensing of this solution.
Improved graphics in terms of metrics and connectivity to SharePoint from Microsoft products would be beneficial.
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 releases lags behind. Also, Maven SCM 2.0.0 has deprecated the provider "maven-scm-provider-jazz". So there is some wonder about the future of the product. It may be perfect for big companies that are more formal and need process/audit/documentation/access control.
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.
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.
One of the downfalls of this product is that we are not able to customize it for our specific requirements. I'm not sure whether that's an issue with the product or with the company's implementation.
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.
We are currently using version four, but we looked at versions five and six and they are getting better and better. They're making planning easier. In version six they have something called a Quick Planner which would be nice to have in our version. In fact, if many of the features they have in five and six could be offered in four as well, that would be beneficial to us. Some administrative tasks are difficult to perform. These could be simplified. For example: setup sprint/iteration period - start and end. It may be simple to have a button to End Sprint / Start new Sprint and the application handle setup and definition. Another example in user holiday's handling to have one click to apply general holiday that applies to all team members.
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.
Upgrades, even minor versions, seem too labour intensive, especially with the enhanced objects, which is why the Jazz platform should be so good.