Heaad of Automation Devision at Alstom Ferroviaria S.p.A.
Real User
Top 5
2024-10-23T07:04:00Z
Oct 23, 2024
The user interface requires significant improvement as it is overly complex. For business users with no experience in IT, it can be particularly challenging to understand the UI and create test cases or scenarios. Simplifying the technical terminologies and breaking it down to simpler terms would be beneficial, especially for users involved in user acceptance testing.
Product Owner at a manufacturing company with 201-500 employees
Real User
Top 20
2024-02-16T10:24:44Z
Feb 16, 2024
We have some special needs. The product does not support our needs perfectly. The GUI is a little bit outdated. There are not many diagrams that help us organize or plan the work for the team. The reporting capabilities are the bare minimum. There might be a more sophisticated setup, but I do not know about it. I believe Jira could provide a lot more. Planning is not that easy. We can’t plan for sprints. The product is missing a lot of features. The compliance and auditing features are not easy for the users. We need to push the users to use ALM. Otherwise, they do not use it. The GUI must be improved. If we create a story from an epic, there’s always a new window opened. It doesn’t help our workflow as a PO to create stories and keep the overview. The way users are guided through the system must be improved.
Technical Lead at Microgenesis Techsoft Private limited
Real User
Top 10
2023-10-03T11:15:22Z
Oct 3, 2023
Maybe there should be more integration—the possibility with the third-party tools. Looking for more integrations specifically with third-party tools that customers can easily access to perform automation without affecting the system. Additionally, some improvements to the user interface (UI) would be helpful, such as exposing more services to make it easier to customize to the needs of each customer. In the next releases, I would like to see the ability to customize reporting without having to rely on a separate tool. So currently, for any customization with respect to reporting from the tool, we still depend on the reporting tool called the publishing engine. So, instead of depending on the publishing engine, we must have a capability that should be available in the next coming version.
The interconnectivity between packages is a major support problem and can be improved. I would like to have better trace matrix ability in the solution.
In the next release, we expect a traceability metrics configuration where we can configure the user stories. We also expect them to improve or simplify the query process.
Tool Manager at a computer software company with 10,001+ employees
Real User
2022-02-10T16:50:24Z
Feb 10, 2022
The user experience is something that can be improved. People ask me about getting a more modern and more innovative user interface. One of the complaints from users is that they have to click buttons too many times for just a simple task. Changing this would lead to a better user experience. ALM should use Git for code versioning but it doesn't. Instead, we integrate it with Git instead. IBM should buy a Git company such as GitLab because that would greatly improve their version control capabilities in the CI/CD pipeline. With respect to DevOps, both GitLab and GitHub are better than ALM It would be helpful if it were easier to set up. This would save us money because hiring an expert to do it is a little bit expensive. If we could instead do it ourselves then it would save this cost.
Lead Engineer at a transportation company with 5,001-10,000 employees
Real User
2021-07-31T05:32:13Z
Jul 31, 2021
I think nowadays people are getting into Jira and other tools. What is happening is, this solution is becoming more traditional, whereas Jira and other tools are more attractive for the new users to learn and start using because of the graphical interfaces. All the traditional users are continuing with this solution, while new users they are preferring Jira. The solution could improve by providing an entire engineering life cycle management solution. When we want to use the solution we feel that it could be better because currently, we use SAP for a lot of our engineering life cycle management obligations, and IBM Rational ALM is only for mainly software management applications. It should be extended and provide more coverage from end to end, which would be helpful.
Applications Developer Specialist at a comms service provider with 1,001-5,000 employees
Real User
2020-08-13T08:33:46Z
Aug 13, 2020
The reporting functionality needs to be improved. They have developed a reporting model but it is not available out-of-the-box. It is especially important when we are talking about Kanban and KPIs. We have some metrics related to lead time and throughput, but we cannot produce them out-of-the-box. There are two features called the Program Board and Quick Learning that need administrator access to use. This is risky and it is not good practice to have more than one administrator on the tool, so the problem is that we can't give this level of access to normal users and it is an obstacle in the way of using these features.
Support for working with traditional methodologies must be extended if IBM wants to expand horizon in the System engineering domain. You cannot really work in the traditional way of development. In the automotive industry here we tend to follow the Agile methodology. The designer manager is uncivil. The design manager is clearly really unstable. In the next release, I would like to see traditional methodologies working within the tool and a traditional planning book in the toolbar.
Software Product Manager at a computer software company with 11-50 employees
Real User
2019-09-19T08:39:00Z
Sep 19, 2019
Of course, it would be related to customer experience. The solution is not user-friendly at all. It needs an expert to use it, although the reporting feature was okay. I'm fine with the tool. From my point of view, it's all about usability. It should be simplified and it should be more user-friendly.
The cataloguing needs some improvement. It needs to be a bit more in-depth. It's an application that is supposed to do more governance around the application lifecycle. The features should be more intuitive. If I'm looking for something, its location should be easy to locate.
Consultant at a computer software company with 1-10 employees
Consultant
2019-09-08T09:50:00Z
Sep 8, 2019
There are a few ways to potentially improve the product although it performs as expected. Reporting can be easier to do and customize, but it is adequate. Product support could be better for new users by providing more beginner-type tutorials. While the product itself is not so complex, step-by-step instructions that help new users understand the basics will make the product easier to adopt. When we started to use the product it was a little bit of mess because we were not used to using it and implemented it poorly in some ways that would have been easy to avoid. Using the product efficiently will be better if there are step-by-step and interactive guides. It would be nice if there were some more possibilities for storing either custom or standard information like stack information, memory cards type and capacity, or other details about products that can be visualized easily in case they may need to be upgraded to solve performance issues. It was a product we decided to use for educational purposes and to provide some guidance to complete projects on time.
Applications Developer Specialist at a comms service provider with 1,001-5,000 employees
Real User
2018-06-12T06:24:00Z
Jun 12, 2018
I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply.
Lifecycle management capabilities built on the open, unifying IBM Rational Jazz platform can help agile and traditional teams: see at-a-glance status, access better data for decisions, manage costs, reuse the most efficient processes across the organization, manage cloud, web, SOA and mobile application design and development. Teams can also gain real-time traceability, manage work across vendors, unify across a diverse set of lifecyle tools, and provide collaborative development for...
The user interface requires significant improvement as it is overly complex. For business users with no experience in IT, it can be particularly challenging to understand the UI and create test cases or scenarios. Simplifying the technical terminologies and breaking it down to simpler terms would be beneficial, especially for users involved in user acceptance testing.
We have some special needs. The product does not support our needs perfectly. The GUI is a little bit outdated. There are not many diagrams that help us organize or plan the work for the team. The reporting capabilities are the bare minimum. There might be a more sophisticated setup, but I do not know about it. I believe Jira could provide a lot more. Planning is not that easy. We can’t plan for sprints. The product is missing a lot of features. The compliance and auditing features are not easy for the users. We need to push the users to use ALM. Otherwise, they do not use it. The GUI must be improved. If we create a story from an epic, there’s always a new window opened. It doesn’t help our workflow as a PO to create stories and keep the overview. The way users are guided through the system must be improved.
The product must be more user-friendly.
Maybe there should be more integration—the possibility with the third-party tools. Looking for more integrations specifically with third-party tools that customers can easily access to perform automation without affecting the system. Additionally, some improvements to the user interface (UI) would be helpful, such as exposing more services to make it easier to customize to the needs of each customer. In the next releases, I would like to see the ability to customize reporting without having to rely on a separate tool. So currently, for any customization with respect to reporting from the tool, we still depend on the reporting tool called the publishing engine. So, instead of depending on the publishing engine, we must have a capability that should be available in the next coming version.
IBM Rational ALM should remove the features not used by the customers and keep this product as lightweight as possible.
The interconnectivity between packages is a major support problem and can be improved. I would like to have better trace matrix ability in the solution.
The solution can improve in the development area and the customized applications.
In the next release, we expect a traceability metrics configuration where we can configure the user stories. We also expect them to improve or simplify the query process.
The user experience is something that can be improved. People ask me about getting a more modern and more innovative user interface. One of the complaints from users is that they have to click buttons too many times for just a simple task. Changing this would lead to a better user experience. ALM should use Git for code versioning but it doesn't. Instead, we integrate it with Git instead. IBM should buy a Git company such as GitLab because that would greatly improve their version control capabilities in the CI/CD pipeline. With respect to DevOps, both GitLab and GitHub are better than ALM It would be helpful if it were easier to set up. This would save us money because hiring an expert to do it is a little bit expensive. If we could instead do it ourselves then it would save this cost.
The stability of IBM Rational ALM could be improved.
I think nowadays people are getting into Jira and other tools. What is happening is, this solution is becoming more traditional, whereas Jira and other tools are more attractive for the new users to learn and start using because of the graphical interfaces. All the traditional users are continuing with this solution, while new users they are preferring Jira. The solution could improve by providing an entire engineering life cycle management solution. When we want to use the solution we feel that it could be better because currently, we use SAP for a lot of our engineering life cycle management obligations, and IBM Rational ALM is only for mainly software management applications. It should be extended and provide more coverage from end to end, which would be helpful.
The reporting functionality needs to be improved. They have developed a reporting model but it is not available out-of-the-box. It is especially important when we are talking about Kanban and KPIs. We have some metrics related to lead time and throughput, but we cannot produce them out-of-the-box. There are two features called the Program Board and Quick Learning that need administrator access to use. This is risky and it is not good practice to have more than one administrator on the tool, so the problem is that we can't give this level of access to normal users and it is an obstacle in the way of using these features.
The stability of this solution can be improved.
Support for working with traditional methodologies must be extended if IBM wants to expand horizon in the System engineering domain. You cannot really work in the traditional way of development. In the automotive industry here we tend to follow the Agile methodology. The designer manager is uncivil. The design manager is clearly really unstable. In the next release, I would like to see traditional methodologies working within the tool and a traditional planning book in the toolbar.
Of course, it would be related to customer experience. The solution is not user-friendly at all. It needs an expert to use it, although the reporting feature was okay. I'm fine with the tool. From my point of view, it's all about usability. It should be simplified and it should be more user-friendly.
The cataloguing needs some improvement. It needs to be a bit more in-depth. It's an application that is supposed to do more governance around the application lifecycle. The features should be more intuitive. If I'm looking for something, its location should be easy to locate.
There are a few ways to potentially improve the product although it performs as expected. Reporting can be easier to do and customize, but it is adequate. Product support could be better for new users by providing more beginner-type tutorials. While the product itself is not so complex, step-by-step instructions that help new users understand the basics will make the product easier to adopt. When we started to use the product it was a little bit of mess because we were not used to using it and implemented it poorly in some ways that would have been easy to avoid. Using the product efficiently will be better if there are step-by-step and interactive guides. It would be nice if there were some more possibilities for storing either custom or standard information like stack information, memory cards type and capacity, or other details about products that can be visualized easily in case they may need to be upgraded to solve performance issues. It was a product we decided to use for educational purposes and to provide some guidance to complete projects on time.
I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply.