We performed a comparison between IBM Rational ALM and Jira based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is relatively easy to use and user-friendly once the setup is complete."
"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."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"The tools for requirement capture we have found very useful."
"Everyone in a team can work on the same platform and share the same information."
"It's easy to use."
"The solution is customizable."
"A most valuable feature involves the ability to customize the entries and to update them quickly."
"The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress."
"Its integration with Bitbucket, Confluence, and other things is most valuable."
"The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution."
"The solution works well and does what it needs to do."
"The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view."
"We've found the scalability to be good."
"It gave us control over all test artifacts in one place, along with easy traceability, mapping between stories, bugs, test cases, and test cycles."
"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."
"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The GUI is a little bit outdated."
"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 product must be more user-friendly."
"The directory designer manager is uncivil. The design manager is clearly really unstable."
"The stability of this solution can be improved."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details."
"The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."
"It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story."
"I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira."
"The solution should be more user-friendly and include integration with different tools."
"Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist."
"Slow when integrating with other components."
IBM Rational ALM is ranked 10th in Application Lifecycle Management (ALM) Suites with 17 reviews while Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews. IBM Rational ALM is rated 7.2, while Jira is rated 8.2. The top reviewer of IBM Rational ALM writes "A complex deployment that is not stable, but is cloud-based". On the other hand, the top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". IBM Rational ALM is most compared with Codebeamer, Microsoft Azure DevOps, Polarion ALM, PTC Integrity and Atlassian ALM, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM. See our IBM Rational ALM vs. Jira report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
