ALM Octane Benefits

ProcessO7962
Process Owner E/E Test Management at a transportation company with 10,001+ employees
The most important thing is that we have, 8,000 users, more or less, and if you could save each user who's working with our current ALM tool, just in opening drop-down menus and searching for information, just ten minutes a day, it's a huge improvement. The concept of Octane is to have the most information and the most important functions available with one or two clicks. This is a big point of savings, in time and money. The powerful widgets, the Dashboard module, the ability to drill down to the information you need and the ability to configure it to your needs, are big advantages as well, and one of the biggest pain points in ALM. In the latter, you would need to install different tools. In our company, everybody just exported everything to Excel and reported everything in Excel. That was a pain. The possibilities of the Dashboard module will save another couple of thousand Euros, because of all of the time and the small developments that were required around ALM will not be necessary anymore because everything is supported by one tool. The general capabilities of Octane, setting up rules instead of programming VBA scripts for controlling the workflow, and making life easier for the users with the template functionalities, are very big benefits. In the old-world ALM, it was hard to adapt the tool as a central point, into a complete toolchain. The requirements of our industry, the automotive industry, of a tool like ALM or Octane are a bit more complex rather than just software development. We are using a complete toolchain. We are using a toolchain of about 70 interfaces around the old ALM. With Octane, we can kick out a lot of those tools, although there will still be some 25 to 30 tools which are connecting different databases, loading information into Octane or from Octane, etc. The openness and the possibilities of the REST API, from an operations and maintenance perspective, are also a big plus. View full review »
Jennifer Plourde
Enabling Manager at a financial services firm with 10,001+ employees
For our use case, it's brought our entire team into a single tool. We're all looking at the same real-time data. Our project management office has been able to set up dashboards for individual teams, and do comparisons by teams, of integration, and cross-team integration, burn-up, burn-down, and cumulative flow types of things. So from a PMO perspective, there is a really good overview, from how we've set up our dashboards, to know where each team is and how they're progressing and how much work they have that integrates with other teams. That's really helpful. The feedback that we've gotten is that the way testing is closely tied into the product Backlog has made it more intuitive, or easier to manage the relationship between building out an application and testing it. In other tools, that is more segregated. The way it's designed in Octane, people have said it makes more sense to them, and that it's easier for them to understand their data and to maintain and test their solutions. View full review »
Steven Tompsett
CDA Engineer at Hastings
Octane has definitely improved the capability that we have for visibility within our tool set. The ability to report and see the current status on change, defect, and test runs on a spring by spring basis within our programs. Previous to this, change management was done in one system and testing was done in another system. Defects were in one of those systems, but they were like forgotten children and weren't really linked to anything. Octane has made everything a lot more visible. It's ability to relate everything together and create spider diagrams of change, the lifecycle of that change, defects, and the test status. These have made a massive difference to the visibility and our ability to trace back to the origin of a change, where it started, and see how it finished. It's beginning to improve our processes as well. We are seeing some real improvements in the way we do things. We are becoming more agile in the way we do it because of that and in a way that stories are managed. Stories are given lifecycles as opposed to just being entities within a tool. The visibility that we received from the ALM tool is that we can see a change through from its early requirements all the way through to development check-ins to the pipeline release then to the point that it's deployed. We can see the full lifecycle of the change within the ALM tool including integrations that we never before had in a change management tool. It's almost revolutionary for some people here to see check-in information appear against a user story in an ALM tool. View full review »
Timothy Leach
Senior Software Engineer with 10,001+ employees
One of the things we're working towards is DevOps. 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. I would estimate it saves us 20 percent in terms of effort and time. We haven't gotten to Nirvana yet, which would be full automation, but we're trying to achieve that. View full review »
Reviewer3273
Programme Test Manager at a energy/utilities company with 1,001-5,000 employees
The integration points are very good. Octane gives us a window not only into our manual testing, but also our automation testing and our performance testing. We can see all results from all three streams of testing in one place. We've never done that before, until this past year. Whether that was possible with Quality Center or ALM.NET, I really don't know, but it's the first time we've ever done this. So the fact that it gives us that window into all phases of testing is where it's a bonus for us. View full review »
Reviewer312098
Senior Expert IT Test Service Management at a financial services firm with 1,001-5,000 employees
Throughout the evaluation, we've sensed that we have better collaboration among these three roles, the business, the testers, and the testing automation engineers or the developers. From a functionality point of view, we have been able to execute more testing automation on this particular pilot team because of the integration between the tools. These are things we can see from the daily work between the teams. It's a feeling that everything is moving a little bit faster, it's a little bit easier. Right now, we have a lot of tools facilitating the BDD syntax but they are scattered. For example, the product owners are working with JIRA or other application products, like Confluence. The developers are working inside their IDE. And the testers are working somewhere else, for example, on ALM.NET. We thought the possibility of having a single platform which can connect all three roles, centralize them into one platform, would be helpful. It's quite difficult because if you write the feature files first in JIRA, for example, you have to copy the content of the feature files to the testing tool. With ALM Octane, it is possible to have synchronization between JIRA and ALM Octane, if we are using both tools. But there's also the possibility that we use only ALM Octane for both the requirements management and the testing. By clicking a button after we have the feature files in ALM Octane, we can send a message directly through the IDE plugin of ALM Octane - for example, for ItelliJ or Eclipse - to inform the testing automation engineer that this test is ready to automate. In other words, it would allow us to keep each of the roles flexible. So the product owner could work in JIRA, the testers in ALM Octane, and the testing automation engineers in their IDE. But we wouldn't leave the consultation aspect behind. View full review »
Gerd Fladrich
Test Manager at a financial services firm with 1,001-5,000 employees
We started from scratch because we didn't have any BDD approach. We used a more old-fashioned method of development, more Waterfall and so on. We were looking for a solution which would be a good tool for our new methodology. For us, this was a key benefit from Octane, to get rid of the old style. We are implementing Agile methodologies in DevOps, that's the main thing. We try to use shift left to test much earlier and therefore it's really helpful to have Octane and to implement the new approach with it. View full review »
Venu Cherukuri
Lead Solution Architect at a Consumer Goods with 10,001+ employees
Coming from an HPE Quality Center/HPE ALM background, in the company, I think Micro Focus has done a great job in redesigning the overall user experience. We've seen a big increase in the adoption of the tool itself. The amount of time we spend on training, in general, has definitely come down. People find it very intuitive. The real value is that we're able to standardize, and project teams are more vested in, or interested in, actually doing their standard activities in the tool itself. The value is in the adoption, that people are willing to use it for the purpose for which it was put in. We have gained some efficiencies. We had a challenge in standardizing our tools. Sometimes activities were tracked within the central depository, sometimes they were outside, on multiple tools. Standardizing on a single tool, and standardizing our process brings us value. It is definitely saving us some time because it's very simple from a user perspective and it's more efficient. View full review »
it_user458409
Test Community Manager at Orange
We had projects in which we had the Agile part in a specific tool and the testing parts in another tool and it was very difficult to synchronize all that together for a reasonable price. Of course, you can buy tools to synchronize the different tools together, but to buy synchronization tools is very expensive. You have to handle that and if something is badly synchronized, you have to redo it by hand. So to have all that included in just one tool really makes our life easier. Another benefit is the integration with Continuous Integration tools. Before, we had to upload all the test results either manually or automatically, but we had to write the scripts for that. With Octane that's just native, included in the package. Finally, it consumes fewer resources than the previous tools in Quality Center. We have the same number of users but with half the servers. It's really economical from that perspective. View full review »
Sukarna Chirumamilla
Senior manager IT at a transportation company
For one, it's the whole Agile framework itself. You're cutting the time, the wait stage, and all that. We wanted a tool. You could do Agile methodology on a whiteboard, by using Post-Its. But practically that is not going to work out because the teams are in different locations. For example, our development team is in India. So we have to have an enterprise level tool which can support everybody. So now we can create the same "whiteboard" and the "Post-Its" in Octane, and everybody can see it around the world. That means the people who support our service, the development teams in India. And the functional team sitting here in the U.S. It's the "collaborator thing." That happens using the enterprise tool. View full review »
Mike Smithson
ALM platform architect at a transportation company with 10,001+ employees
Octane provides the platform needed for teams to run Agile projects. Previous tools like ALM QC were modeled for Waterfall methodologies. Metrics are not relevant for us in this case as we are still moving from Waterfall to Agile and hybrid delivery. Our Waterfall practices have been standardized and templated to provide cross-project metrics and reusable assets, such as tests and other libraries. Our Mobile and Solution Delivery teams are finding Octane provides the CI/CD and DevOps connections with development and infrastructure teams, connections that they had previously managed with brute force tools like SharePoint, Excel, and email. View full review »
Walter Whitaker
Qa manager at a tech services company with 1,001-5,000 employees
It helps us go to the true DevOps model, which means we can do shorter cycle times. Go from releasing every month, to every day. It's got a nice clean interface that people don't mind using. It integrates into the developers IDEs, like IntelliJ, which means that everybody gets to work in the tool they want to work in. Then it easily integrates across, so everybody can see the information in any place they want to see it. View full review »
Mike Smithson
ALM platform architect at a transportation company with 10,001+ employees
Two things. One is Agile. The other is the CI integration. We've always struggled bringing the development teams directly into ALM. ALI is a bridge, but it's cumbersome. The CI integration of the pipelines is what we're looking for right now. To bring us into the DevOps potential. That's the biggest draw right now. Octane fits that niche that we never had. We need an Agile solution. We had other teams using other products that are semi-Agile, but we didn't have an approved standard. Octane gives us that. It's awesome. View full review »

Sign Up with Email