Please share with the community what you think needs improvement with IBM Rational ALM.
What are its weaknesses? What would you like to see changed in a future version?
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.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.