We performed a comparison between IBM Rational ALM, Jira, 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."The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"It is relatively easy to use and user-friendly once the setup is complete."
"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."
"I would rate the stability of this product a nine out of ten."
"You can customize the board according to your needs."
"The integration with Git works well."
"The word emulation and importing is good."
"The cataloging is a very valuable feature. For a lot of enterprises, they end up not knowing which applications do specific features. The cataloging helps with this. It's not that verbose, but it still gives you allowances to put in more detail."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"It also works well with all the integrated tools that you buy."
"The most valuable feature is that it is somewhat flexible."
"The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"Jira is designed for issue tracking, making the process much easier than traditional methods like paper-based tracking. It is number one for agile management."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users."
"The flexibility to create different flows is most valuable."
"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 transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing."
"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."
"The effect of these kind of tools drives the way you organize things. It helps you shape the way you flow."
"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."
"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."
"The most valuable feature of this solution is the Kanban board."
"We can work better and at a higher quality, than we were able to before."
"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 stability of this solution can be improved."
"The interconnectivity between packages is a major support problem and can 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."
"The stability of IBM Rational ALM could be improved."
"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The reporting functionality needs to 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 way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified."
"Of course, the price could always be cheaper."
"In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members."
"We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it."
"Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"The stability could be improved."
"Customization features may not be exposed or unavailable, so people may be looking for them. So, customization is an area people have told me is more desirable."
"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 could improve by being self-organizing: user stories, different hierarchies, and different perspectives. Not just as a single hierarchical structure, but something that can be multidimensional."
"The product needs to have more integration capabilities."
"There are few customisation options. For instance, the workflow for story cards cannot be changed out of the box from the standard (Defined, In-Progress, Completed and Accepted)."
"I wish there was a view, like the Kanban view, where you could see the parent, and see all the children visually, so you could drag and drop where you want it to go. Something like that might help."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
"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."
