We performed a comparison between IBM Rational ALM, Jama Connect, and Rally Software based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."It helped us contain critical things, like source code and several documents, which is very important to us."
"You can customize the board according to your needs."
"One of the key advantages of IBM Rational ALM is its workflow capabilities, which enable seamless collaboration between development and production teams and ensure that all stakeholders are aware of the progress and readiness of the solution. Additionally, the solution is good for integration."
"IBM Rational ALM is a very good tool. I like the management and traceability features and the test management tool. The latter is not linked with the stories and fixed management. It is really useful, and we can create test plans. We can also test some metrics related to QA."
"At the same time, if you're working from the architect or the designing team you, it's quite easy to manage the resources online."
"The solution is customizable."
"We have something called the GC (global configuration), which is a unique feature compared to any other competitor we have in the ALM space."
"Everyone in a team can work on the same platform and share the same information."
"You can get full traceability with any other system. It also includes a test module, and you build the traceability matrix incrementally throughout the development process."
"Technical support answers fairly quickly compared to others like IBM or Atlassian. They also offer quite a good knowledge base for advanced cases and how to plan it, etc. via videos that they provide. They are quite useful."
"The most valuable feature is the user-friendly interface."
"I like Jama Connect because it's easy to use and understand. The widgets are great, and linking is straightforward. The solution is not complex compared to its competitors."
"Jama Connect is a good tool for the entire software development cycle."
"It is good at requirements management and test management."
"Provides suitable tools for managing regulatory requirements."
"The metrics - collecting metrics. It's because we've used several other tools in the past, and they don't give you a full indication of how well your teams are performing, at a portfolio level, at a product level, and at the team level."
"Agile Central allows us to log one hundred percent of the work we do and it allows for no hidden work, so teams can't go under the radar with what they're working on."
"The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"What I like most about Rally Software, in terms of using it for the agile process, is that it's clear, useful, and user-friendly. I also like that it has every field you can use for the Scrum process."
"It has allowed the quality assurance team to keep all information in sync with the application requirements and user stories for our general development."
"The visibility it brings to the plan, the ability to capture tasks, and trace them all the way through the life cycle. Providing that visibility helps both me and the team, or teams, to be able to understand where we are in the development process."
"Ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new."
"The reporting functionality needs to 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."
"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."
"The GUI is a little bit outdated."
"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."
"The stability of IBM Rational ALM could be improved."
"The directory designer manager is uncivil. The design manager is clearly really unstable."
"The product must be more user-friendly."
"I think there's room for improvement, especially with the review process. Reviews should be integrated with requirement evaluation instead of being separate from it. The review should not run parallel to the requirement."
"I have inquired about pricing for this solution but have not yet heard anything, so their response time in this regard is something that should be improved."
"I believe one of the weak points is the reporting side. You must export inter-readable reports from Jama if you do not use the system as a repository for your design history file. Jama is great if you keep it in Jama, but reporting out requires some customization to get it right."
"t is rather slow, so the speed of the process and consuming information should be improved. It doesn't have a nice way of viewing information. We would like to see better interfaces for consuming information."
"The user interface could be modernized and the product lacks project management functionalities."
"Test management can be improved. It's not so scalable. The user interface needs to split things into small projects."
"The initial setup could be better, it's complicated."
"There are some security concerns with Jama Connect, including two-factor enablement."
"In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."
"I would like for workspace admins to be able to hide projects in the Project Picker and not lose any historical data; make them invisible to certain users, visible to certain users, depending on permission sets. That would be lovely."
"I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."
"It is hard to track the changes. For example, we're in sprint 25, and then we have 26, 27, 28, and 29. Throughout that whole time, we're developing pipelines in Azure, moving to GitHub, creating pipelines, and working with teams. But sometimes, we need to revisit specific decisions made in previous sprints, like pipeline details. Maybe it's in our Azure Wiki, GitHub, or Teams, but it's not always consistent. I wish I could search for all tasks or stories related to that particular effort without needing to know everyone's individual stories or features."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."
"It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
"I would like to see more Kanban support. As it stands, it doesn't seem to have the features or the layouts that the teams really need to be able to execute their tasks. It almost tries to force you into more of a Scrum style."
