We performed a comparison between OpenText ALM Octane, OpenText ALM / Quality Center, 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.
"An improvement on previous versions because it comes as preconfigured as possible."
"The most useful feature of Micro Focus ALM Octane is the dashboards, they are easy to use."
"Current version of the solution is fairly stable."
"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."
"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 important feature is the integration among all the different features in just one tool: Agile management system, requirements management system, test management, defects management, automatic test execution. Really, if you're looking at other tools, you will never find all that integrated into just one tool with all the traceability, with all the elements in just one place."
"It is a very stable solution. Stability-wise, I rate the solution a ten out of ten."
"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."
"As a stand-alone test management tool, it's a good tool."
"I like that it integrates with the Jira solutions."
"So the first impression that hits me about HP UFT 14.0 (formerly QTP) is that it seems to be a whole lot faster! But that could be subjective, as I'm running it on a high end gaming system."
"Defect management is very good."
"The best thing is that you can see your current status in real time... To see real-time updates, you just log in to ALM and you can see exactly what the progress is. You can also see if the plan for the day is being executed properly, and it's all tracked. From the management side, I find those features very valuable."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"I love linking/associating the requirements to a test case. That's where I get to know my requirement coverage, which helps a lot at a practical level. So, we use the traceability and visibility features a lot. This helps us to understand if there are any requirements not linked to any test case, thus not getting tested at all. That missing link is always very visible, which helps us to create our requirement traceability matrix and maintain it in a dynamic way. Even with changing requirements, we can keep on changing or updating the tool."
"We can get an entire project into a single repository where we can view all the data in detail. This is where we keep all our test cases where everyone can reference them. This provides everyone access to the test cases and artifacts via the cloud. There is no need to contact anyone."
"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."
"I was able to create epics for our budgeting concerns and it helped me link everything together."
"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."
"The most valuable feature of this solution is the Kanban board."
"Tech support is very responsive, helpful, and available."
"It's very user-friendly."
"When it comes to the valuable features of Rally Software, it excels at burn-down charts, burn-up charts, and road mapping once it's set up. I particularly appreciated the new feature for releases and road mapping, which worked exceptionally well."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"They don't support all IDEs yet. We have Visual Studio code, which is not supported, and loved by our developers. This integration is missing. We also had to do our own in-house integration with the Confluence. That is also something that they could add."
"Globally, I don't see many major points of improvement. It's mostly plenty of little things, and it's weird to me that they are not in the product yet. They are really details, but they're annoying details... Today, in the tool, we've got plenty of assets we can handle, like requirements, user storage, defects, tasks and so on. And to all of those elements, we can add comments. We can add comments to any asset in Octane but not to tasks. It's just impossible to understand why it's not available for the tasks because it's available everywhere else. Similarly, for attachments, you can attach files absolutely everywhere except on automated runs, which is, again, awkward. I don't understand why on this element, in particular, you cannot do it. It's little touches like that."
"It could use just some small improvements. I would like additional features, like planning features, user story mapping, or connection to collaboration tools."
"There's a trend in our requests to have the ability to export data, en masse, out of Octane. There are capabilities within Octane to export data, but there are specifics around test suites and requirements and relations, as well as certain attributes, that we would like to be able to export easily out of Octane and into a database or Excel."
"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."
"I have yet to experience the CI/CD part of Micro Focus ALM Octane but as demonstrated by the team who is providing the services, I see that the CI/CD could improve. When we check in the code, for the code snippet that has been checked in by a particular user, you need to open a separate file. When comparing Micro Focus ALM Octane to Jira, they have a separate window in which you can click on the ID and the code is visible in the snippet. It's a two-step process in Micro Focus ALM Octane and it's a single-step process in Jira. It's essential for the developers to think about this difference."
"We've only had a few stability issues. Generally, we have issues following any deployment they do, so if they do a deployment on a Sunday, then we may have a couple of issues on a Monday or Tuesday."
"There are some challenges when we want to integrate the tool with other products, and it takes time for a team to figure out how to do it."
"The performance could be faster."
"The solution needs to offer support for Agile. Currently, ALM only supports Waterfall."
"Defect ageing reports need to be included as built-in."
"The integration could be improved because with Agile technology you are working more quickly than with a top-down methodology."
"We operate in Sweden, and there are not so many Swedish people that know the product."
"ALM Quality Center could be improved with more techniques to manage Agile processes."
"Lacks sufficient plug-ins."
"If the solution could create a lighter, more flexible tool with more adaptability to new methodologies such as agile, it would be great."
"CA Agile Central does not have a workflow tool included."
"There's a lot of support for Scrum and Agile, but it needs something for the Kanban side."
"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."
"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 would like more meaningful, customizable dashboards."
"I think there needs to be some simplification. The team-level side can be challenging and complicated."
"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."
"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."
More OpenText ALM / Quality Center Pricing and Cost Advice →
