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."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."
"Everyone in a team can work on the same platform and share the same information."
"The most valuable feature is the reporting of the CPU usage on the dashboard."
"The word emulation and importing is good."
"It's easy to use."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The tools for requirement capture we have found very useful."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"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."
"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."
"Jama Connect is a good tool for the entire software development cycle."
"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."
"Provides suitable tools for managing regulatory requirements."
"It is good at requirements management and test management."
"The most valuable feature is the user-friendly interface."
"The main ways that I used it when I was in it day to day was keeping up with the burn rate within the teams. Also, to track at the feature level too, as far as how we were doing with actually being able to deliver that feature."
"If teams are tracking correctly and entering their information correctly, it's really easy to see where you're at, within your release, and whether you're on track or not."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker."
"The Defect feature. In one view you can see all your defects and you can push them into the different releases."
"The most valuable feature of this solution is the Kanban board."
"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
"The stability of this solution can be improved."
"The features should be more intuitive. If I'm looking for something, its location should be easy to locate."
"The solution can improve in the development area and the customized applications."
"The interconnectivity between packages is a major support problem and can be improved."
"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 directory designer manager is uncivil. The design manager is clearly really unstable."
"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."
"IBM Rational ALM should remove the features not used by the customers and keep this product as lightweight as possible."
"The user interface could be modernized and the product lacks project management functionalities."
"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."
"The initial setup could be better, it's complicated."
"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."
"There are some security concerns with Jama Connect, including two-factor enablement."
"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."
"Test management can be improved. It's not so scalable. The user interface needs to split things into small projects."
"We want Rally to generate OKRs, to allow teams to record the OKRs, and then the OKRs can be mapped to the epics and there is organizational alignment."
"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."
"We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them."
"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."
"I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
"More customization capabilities would be helpful. Providing a little bit more structure around how the system should be set up in terms of the hierarchy structure might be helpful as well."
"A lot of the features that we would be looking to add, I am learning may not be within Agile Central, but part of another CA tool set."
