Most Helpful Review
Gives us work distribution among team members, but teams need clearer pictures of resource availability in charts and...
Find out what your peers are saying about IBM Engineering Workflow Management vs. Micro Focus ALM Octane and other solutions. Updated: January 2020.
390,232 professionals have used our research since 2012.
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
Work distribution among team members and accountability for completion with a clearer picture.
All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security.
Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness.
Octane creates a gentle approach to Agile-based projects.
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.
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.
The openness and the possibilities of the REST API, from an operations and maintenance perspective, are a big plus.
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 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.
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...
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.
Teams need clearer pictures of resource availability in charts and dashboards along with plans.
Some administrative tasks are difficult to perform. These could be simplified.
Improvements could be made by way of additional integrations across the lifecycle.
An example of one of the features we have requested is inheriting information from a test suite into a suite run and into a menu run, so the user does not have to add that information, update it manually.
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'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.
We have some requests to beef up the manual testing abilities and the ability to report on testing progress. All the basics are there, but there's an issue of maintainability. For example... once you plan a test and it creates a run, more particularly a suite run, you can't edit the suite run afterward... That that is not realistic with how people work. Mistakes are made and people are humans and we change our minds about things. So the tool needs to allow for a bit more flexibility in that testing area, as well as some better widgets to report on progress.
When I manage projects that are being created in ALM, I have a standard template, but I don't have a template for them in Octane. I literally have to create the project from the ground up every time, which for an administrator, is a nightmare solution
The Requirements Module could be better, to build up a better requirements process. There's a huge improvement from ALM.NET to Octane, but it's still not really facilitating all the needs of the product owners, to set up their requirements in Octane.
Because JIRA is a leading tool for both development and requirements management - everybody is using JIRA - I'm pretty there will be a use case where people are trying to connect between ALM Octane and JIRA. The back-end configuration of the synchronization with JIRA could be simplified. The architecture is really complicated. We required a lot of machines to build the cluster and the configuration was not really clearly described within the documentation. This may have something to do with the fact that the software is pretty new.
Pricing and Cost Advice
Licensing: The solution cost is high and should be brought down to increase competition.
It's an expensive investment to make, so the decision should be driven on individual requirements.
For what it does, it's very reasonably priced. I like the licensing model as well, because it's very flexible. You can scale licenses up and down for short periods of time.
In terms of pricing, it's comparable to what we had previously. It's not priced at the higher end of the scale by any means. It's priced nicely, in the middle of the market. For what you're getting, it's a very good tool.
It's expensive. HPE products, and now Micro Focus, have always been expensive. The license is not cheap, and it will always be a challenge, particularly for small organizations like ours.
It's pretty pricey, one of the most expensive ones on the market... The value depends on if you use all the features that it has. It comes with a lot of features. The difference between the license structure of ALM and Octane versus JIRA, is that you get everything with ALM and Octane... For JIRA, you buy the pieces one piece at a time.
It will be as expensive as ALM.NET, if not more expensive. But here's a good tip: If you have ALM.NET, you are able to share your licenses from ALM.NET to Octane. You just have to define a dedicated number of licenses on ALM.NET and then you can share them with ALM Octane, with some configuration effort. This is something that you have to take into account, that there is a possibility of such license sharing that could decrease your costs. Compared to open-source tools, the price the ALM Octane is definitely higher, in terms of the licensing cost.
Pricing is the weakest point. It is expensive, but the tool has plenty of features. The main problem we have is that the pricing is very high compared to some other solutions.
out of 18 in Enterprise Agile Planning Tools
Average Words per Review
out of 18 in Enterprise Agile Planning Tools
Average Words per Review
Compared 53% of the time.
Compared 11% of the time.
Compared 6% of the time.
Compared 50% of the time.
Compared 33% of the time.
Compared 7% of the time.
Also Known As
|IBM Rational Team Concert (IBM ALM), IBM RTC||Micro Focus Octane|
IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of seamlessly integrated tools: IBM Engineering Workflow Management, IBM Engineering Test Management, and IBM Engineering Requirements Management DOORS Next.
|In support of the bimodal nature of many customers today, Micro Focus has expanded the ALM experience by introducing ALM Octane, as a separate platform that is tuned and designed for high-velocity, Lean and Agile teams. ALM Octane is an included part of the ALM product, and integrates with both Micro Focus Agile Manager and the traditional Micro Focus ALM.NET platform to allow teams to easily share assets and report across projects.|
Learn more about IBM Engineering Workflow Management
Learn more about Micro Focus ALM Octane
|Telstra Corporation, Visteon, Atos SE, Panasonic Automotive Systems, IBM Global Technology Services, CareCore National, JTEKT Corp., ItaÒ BBA, Avea, CACEIS, Danske Bank Group, APIS IT|
Information Not Available
Comms Service Provider11%
Software R&D Company11%
Financial Services Firm30%
Comms Service Provider10%
Software R&D Company46%
Comms Service Provider7%