We performed a comparison between OpenText ALM Octane, Rally Software, and TFS 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 most valuable features of the solution are its ability to manage test scenarios, test results, and test automation, which are its primary functionalities."
"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."
"An improvement on previous versions because it comes as preconfigured as possible."
"The defect management gives us full-fledged capabilities for handling defects, including capturing the details of the defects and even screenshotting the defect cases. The defect management is comprehensive."
"With an Octane project, we have our automation, our requirements, our tests, our pipeline into build-and-deploy, and the ability to identify problem areas. It makes things quicker because it's more along the lines of an automated process."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"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."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"I was able to create epics for our budgeting concerns and it helped me link everything together."
"The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop."
"We have teams come and go all the time. We have teams in India, America, Ireland, Poland, Italy, England... we are spread out everywhere! Rally is our key tool for scrum planning and our single source of truth, and it handles it all flawlessly."
"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."
"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
"My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."
"The most valuable features are in-line editing, easy custom view setup, intuitive and helpful visuals (e.g., contextual formatting) and the collaboration features."
"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."
"This solution enables us to link all items usefully, in the way we use Agile."
"The interface is easy to navigate."
"The most valuable features are the dashboard and task-selection capability."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"It is a stable solution."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"It is easy to push our changes from quality to pre-prod and prod."
"The most valuable features of TFS are bug reporting and its high performance."
"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 is an opportunity for them to do a little more with the dashboarding. We still feel that HPE Quality Center/HPE ALM reporting is very powerful. We talked with R&D, and there are some things on their roadmap, but at the same time, their strategy is to connect Octane with visualization tools such as Power BI."
"It would help us if ALM Octane got FedRAMP-certified, so our government departments could use the cloud solution. That way our external consultants could access it. We've created a URL to get to it, but if it were FedRAMP-certified and service and had support in the continental United States, that would be better."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"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."
"Security and security management, meaning the integration of the security, could be enhanced. We know about Fortify, but it would be better to have security features in the original Octane platform without the need for another solution or another application."
"We’d like to see Platform One/Iron Bank compliant containers."
"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."
"The stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"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)."
"We would like more meaningful, customizable dashboards."
"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."
"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."
"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."
"The product needs to have more integration capabilities."
"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 has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"The execution of test cases could stand improvement."
"The tool needs improvement in stability."
"The reporting functionality is something that they should work on."
"More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively."
"The dashboard needs more enhancements."
"Access and permissions are confusing when attempting to include basic manual testing functionalities."
