Micro Focus ALM Octane Primary Use Case

Process Owner E/E Test Management at a transportation company with 10,001+ employees

We are using ALM Octane for electronic component testing and validation. We have a few departments where they are developing their software and using JIRA projects and exchanging results with Octane. 

About 80 percent of the users are not in software development itself, but are in software testing. The software is developed by external companies and we are just doing the integration testing. We are putting the components together from five different suppliers, and then doing the integration testing. Is the software working in real life, together, from the different control units of different vendors? It is a staged process. We check if things are working in the different parts of the system, like the engine components, drive train, navigation, and infotainment systems. If things are working in those different areas, we put everything together and test it in a complete car.

As a result, we have lots of test cases. We have automated tests and a test automation tool that is controlling complete car-wrecks and the like. So it's not only a mouse pointer on a screen. It's controlling robots opening and closing doors, for example. 

Our main focus is efficient planning of tests. We cannot run all the tests we have every single week, because lots of the stuff has different variants for Europe and the U.S. and China. So we have to have very sophisticated test planning. A lot of attributes are needed for this and for all the runs, whether manual or automated. We have what we call a very large problem management process to work on the defects with the 100-plus suppliers that are delivering different control units and, therefore, software packages.

View full review »
Agne Gecevice
Release Manager at a comms service provider with 1,001-5,000 employees

ALM Octane is used to manage our software delivery. Currently, we are running the hybrid mode. We use traditional waterfall delivery as well as agile. 

  • For waterfall delivery, it is managed completely. Then, we have our requirements and our test cases to cover those requirements as well as the defects. 
  • For agile, we currently have only one team. So, all team activity happens in ALM Octane. Their backlog is broken down into user stories tasks, then covered by the test coverage.

We have installed it on a Windows Server on our systems.

View full review »
Stefan Berchtold
Release Management and Testing Manager at a comms service provider with 1,001-5,000 employees

Our use cases are test management, defect management, and release management. We also do quality management and we have started to put our Agile journey on it. That is something we started at the end of last year. We're putting more and more on it. We're doing Agile delivery and Waterfall delivery with it.

View full review »
Learn what your peers think about Micro Focus ALM Octane. Get advice and tips from experienced pros sharing their opinions. Updated: May 2021.
509,641 professionals have used our research since 2012.
AGM, Delivery Excellence at a comms service provider with 1,001-5,000 employees

We are using it for agile projects. Our company projects run using Agile models, so we use all the important modules of Octane, like Backlog, Epics, Feature, and user story in Tasks. We are also using the Product Backlog and Team Backlog modules as well as the Quality modules under quality, test and defects. This is primarily for agile and are all the modules and dashboards that we use. 

Another use is for waterfall projects. To some extent, we are using the requirement documents and Quality modules for our waterfall projects.

We just started analyzing and using a module called Pipelines Analysis. We are trying to integrate our Jenkins with Octane to start using it. This is in the initial stages.

After taking input from the Micro Focus sales team, deployment team, installation team, and professional services team, we are using Octane to its full capabilities, except for with the Pipeline Analysis and dashboards. We still need to focus more on dashboards, because Octane does support plenty of dashboards. We want to start using those in a big way along with the Pipeline Analysis. We are already using all the other modules in a big way. We started configuring dashboards for agile, waterfall, and various built-in widgets, but this is also in the initial stages. We need to explore more the dashboards and Pipeline Analysis, which is where we are seeking support from Micro Focus.

It is purely for project milestone progress, project environment, project development, project execution, software development, and software execution. Then, we are using it mainly for holding and maintaining the repository of Product Backlog, Epics, Features, testing test cases, system integration testing, and user acceptance testing. That is the scope that we have defined.

View full review »
Founder, Managing Director at a tech services company with 51-200 employees

One use case was for development life cycle management for a pool of developers using it in an Oracle and .NET development environment.

View full review »
Wilheminah Ngqola
QA Specialist at Vodacom

We are only using the Quality testing module of Octane to test newly developed mobile solutions or changes. For example, if someone wants to deploy a new promotion of a cheap bundle for 1 GB of 50 ram. Once that goes through the project management and comes to us, we use mostly these three Octane modules: Backlog, Quality, and Pipelines. 

View full review »
Test Automation Eng Senior Analyst at a tech services company with 10,001+ employees

We use ALM Octane for lifecycle management and for testing.

View full review »
Learn what your peers think about Micro Focus ALM Octane. Get advice and tips from experienced pros sharing their opinions. Updated: May 2021.
509,641 professionals have used our research since 2012.