Micro Focus ALM Octane Other Solutions Considered

ProcessO7962
Process Owner E/E Test Management at a transportation company with 10,001+ employees
We started analyzing which tool we should use for the future two years ago or so, and we started digging into Octane very early. I work on Octane from a test perspective: What the tool is capable of doing, and how we can adapt our processes to the new options we have with Octane. Options we considered include JIRA, which is used by a lot of small teams. There is a standard toolchain around JIRA, but JIRA, with the amount of data and information we need to run, was very easy to strike from the list. We dug into IBM and PTC Tool Chain. We looked into ALM Octane vs codeBeamer from Intland. We did some comparisons but ended up with Octane. With JIRA and the toolchain, you cannot run a business like we are doing with car development, using a lot of plugins to get the needed functionality into one tool. You have so many small companies providing those plugins. What if the company providing one of the tools or plugins you're using collapses or doesn't support a new JIRA version? So this was not an option. PTC is also using different tools to support the full functionality of requirements, test cases, team management, the backlogs, tests and defects, and so on. The biggest competitor to Octane was codeBeamer, but from our perspective, Octane did much better in performance. Octane is not able to do as many relations between the data objects as codeBeamer, but performance was the key factor for us. We are now setting the foundation for the next eight to ten years. We had to have that in mind, as well as the increase in data, the increase in users, the increase in data objects and rules, and the complexity of development which is dividing into different pieces. To cover all this in one single tool led us to Octane. Cost and license fees were also a big issue. The two solutions, codeBeamer and Octane, weren't that far apart but, here as well, Octane was first. Finally, with the benefit of this design partnership, which is unique - and we are very proud of this relationship with Micro Focus - it's a plus for us to be able to influence the tool and get features, especially within the timeline that we need them. That's one of the biggest advantages. View full review »
Jennifer Plourde
Enabling Manager at a financial services firm with 10,001+ employees
We did not evaluate other options before choosing Octane. At that point, we were in pretty deep with HPE. But before we chose HPE as our vendor for the bulk of our enterprise tools, we did an evaluation of different vendors, different suites of enterprise tools that we could possibly host, before we made that decision to go with ALM and AGM and UFT. View full review »
Steven Tompsett
CDA Engineer at Hastings
It went through official procurement process where we went out to tender with seven different suppliers. We had responses from five of those suppliers. We had demos from five of those suppliers. We followed three more through, then we eventually selected Micro Focus ALM Octane. At which point, we started demoing Octane and ran it through 2018 whilst we were doing contract negotiations and signing contracts, which was probably the single hardest part of the entire thing. Four of the seven vendors that we looked at were Micro Focus, CA Agile (incumbent), VersionOne, and Jama. We went with ALM Octane because of its functionality and it is presented very cleanly and simply. You are never more than three clicks away from where you need to be in Octane. Another reason that we went for ALM Octane as a tool is because of our relationship with Micro Focus as a company. ALM Octane has a cleaner version than VersionOne, which is a little busier. View full review »
Find out what your peers are saying about Micro Focus, Atlassian, Microsoft and others in Application Lifecycle Management (ALM) Suites. Updated: November 2019.
384,324 professionals have used our research since 2012.
Timothy Leach
Senior Software Engineer with 10,001+ employees
When you compare ALM Octane vs JIRA, it's different than JIRA where you have the core product and then you have to buy all of the add-ons to do what you need to do. Octane tends to have everything you need. View full review »
Reviewer312098
Senior Expert IT Test Service Management at a financial services firm with 1,001-5,000 employees
We are doing a lot of other evaluations; for example, the possibility of using direct JIRA backends for testing. In addition, but not in the same magnitude as our evaluation of ALM Octane, we're still looking at the possibility of holding on to ALM.NET longer. View full review »
Gerd Fladrich
Test Manager at a financial services firm with 1,001-5,000 employees
We looked at a few. One we're still having look at is Xray but doesn't fit with our BDD approach. We also looked at ServiceNow. That's mainly for ticketing systems but they also showed us something about test management. It was very close to ALM, to the old way, so it was also not very useful for our process. Our support is working with ServiceNow but it doesn't fit with our project. View full review »
Venu Cherukuri
Lead Solution Architect at a Consumer Goods with 10,001+ employees
We looked at six tools as part of our evaluation, when we were looking for an Agile ALM tool. We looked at CA Agile Central, VersionOne, JIRA, TFS, Agile Manager, and Octane. We did have very extensive requirements and they scored very closely. JIRA was our number two, Agile Central was number three, and VersionOne was our number four. Agile Central scored more, the highest, but Micro Focus allowed us to share licensing between HPE Quality Center and Octane. That was the primary reason it was a no-brainer for us to get started with Octane. Apart from our hardware and implementation costs, there were zero costs to begin with. Most of the other tools that we evaluated were very comparable. You could pick any of those tools on any day. But for our use cases, for our specific needs, and the costs and scoring, we zeroed in on Octane. View full review »
it_user458409
Test Community Manager at Orange
We evaluated several solutions. One is called the Tuleap, which is open-source. Globally, it's a software development forge. The problem with that solution is that it's lacking test management, primarily. Then we tested another open-source solution made by a company named Henix, called Squash, which is a good solution, especially for open-source. It's just missing an integrated Agile management system. We also looked at JIRA but it does not have a test solution system and I don't like Atlassian politics very much. View full review »
Mike Smithson
ALM platform architect at a transportation company with 10,001+ employees
We evaluated solutions from ServiceNow, VersionOne, Jira, and multiple in-house solutions. View full review »
Find out what your peers are saying about Micro Focus, Atlassian, Microsoft and others in Application Lifecycle Management (ALM) Suites. Updated: November 2019.
384,324 professionals have used our research since 2012.
Sign Up with Email