We performed a comparison between OpenText ALM Octane and Rally Software 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 a very stable tool. The tool has been in the industry for so many years. Stability-wise, I rate the solution a nine out of ten."
"It's more streamlined because we have it all under one umbrella. And once the business requirements and rules have been created, we can do test cases and apply them to the business rules."
"I like the fact that you can use it on top of Jira."
"A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM."
"The most valuable features of the solution are its ability to manage test scenarios, test results, and test automation, which are its primary functionalities."
"The dashboards and metric reporting are valuable features."
"Its end-to-end traceability is one of the big advantages. Most of our agile projects work in a closed team structure. We are seeing what is the flow, where we are, and what is the project milestone. So, it provides end-to-end traceability and good visibility of project milestones."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"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 most valuable features of Rally Software are the executive dashboards, ease of use, and many other features. They have encapsulated everything that a GI can do, such as monitoring, maintaining, and then releasing. It's continuous integration and development."
"Having that view into features and roadmap from product to delivery teams, and where they are going, then execute on."
"It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that."
"It's designed around Agile, so it has all of the pieces that match up with the process."
"Helps me determine how fast I can launch, go to production."
"It helps me evaluate teams' historical performance using velocity charts."
"It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows."
"The reporting needs to be improved and allow for customization. I want to build my own widgets, but I don't want to use the ones already in the system. I want to build mine from scratch."
"What could be improved in Micro Focus ALM Octane is its integration with Jira."
"Technical support can be slow."
"The elements in filtering need to be improved, meaning the number of filters I can use in widgets or in the grid views in parallel. There's a limitation which bothers a lot of our users. Filtering in text, or having a complex filter is limited. In a given field, for example, I can use a filter only once. I cannot say, 'Include the values 1, 2, and 3, and exclude value 17.' This is not possible but we have requested it often."
"Also, while there is a Requirements Module in Octane, it is very plain. It's okay to have some requirements described there, but it's not really following the whole BDD approach. I would like to have more features for requirements in there."
"The product's requirements management feature needs enhancement in terms of functionality."
"It could use just some small improvements. I would like additional features, like planning features, user story mapping, or connection to collaboration tools."
"I would like to see the mobile testing improved so that we can simply select a mobile device, then specify what parameters we want, and the testing will be run based on that."
"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)."
"One problem I see is that if there is a dependent user story - for example, if my team is working on one thing and there is a dependent user story from another team - we can have a dependency created but we don't know if there is a change of status from the other team. That is something which is very important for Agile Central to look into so that if the other team makes any changes we will be notified as well."
"We'd like better dashboards to make visibility better."
"More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc."
"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."
"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."
"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."
"It requires better scalability for the implementation of the whole suite. We do not use it in that fashion, and visibility is sometimes a problem."
OpenText ALM Octane is ranked 5th in Application Lifecycle Management (ALM) Suites with 38 reviews while Rally Software is ranked 8th in Application Lifecycle Management (ALM) Suites with 116 reviews. OpenText ALM Octane is rated 8.2, while Rally Software is rated 8.2. The top reviewer of OpenText ALM Octane writes "Reporting engine, widgets, and dashboards are a huge plus, and powerful REST interface means we can interact with other tools". On the other hand, the top reviewer of Rally Software writes "A solution that enables users to accurately estimate the time required for building large software projects". OpenText ALM Octane is most compared with Jira, OpenText ALM / Quality Center, Microsoft Azure DevOps, GitLab and Codebeamer, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and Polarion ALM. See our OpenText ALM Octane vs. Rally Software report.
See our list of best Application Lifecycle Management (ALM) Suites vendors and best Enterprise Agile Planning Tools 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.
