Most Helpful Review
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
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.
People really how easy it is to customize. In some previous tools, that has been very limited, or you had to know how to write code to do some of the customizations, or it was very confusing. Going back to the user interface, they've made the customization of the tool, the workspace settings, very easy for people to figure out and use.
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.
A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM.
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.
It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code.
From the project management perspective, the tool is efficiently managing teams by giving management information, such as reports, graphs, velocity, capacity, etc.
The biggest value-add is the solution integrates well with most Microsoft products.
Build definitions and releases within the product. allow us to put our latest applications in the field.
It has great functionality: work items, backlogs, source code, build releases, and it's easy to use.
Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error.
Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology.
I like its MTM (Microsoft Test Manager) section which gives us options to create various test plans and add test cases into it.
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.
Also, while there is a Requirements Module in Octane, it is very plain. It's okay to have some requirements described there, but it's not really following the whole BDD approach. I would like to have more features for requirements in there.
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.
The dashboard needs more enhancements.
More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively.
Since it is Microsoft, it is technology agnostic, thus it does not really fit into various different technologies in the organization.
We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS.
TFS on-premise does not support integration with SharePoint Online.
Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI.
TFS and MTM have their own style of working and they are different from other tools like Jira or TestRail, which are simpler and easy to use.
Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements.
Pricing and Cost Advice
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.
It is pretty expensive compared to other project management tools.
If running TFS on-premise is expensive, maybe you could consider moving to the Cloud and use the Visual Studio Team Services.
Use the Microsoft recommended “seat-based” licensing model. This allows a single developer with multiple machines to consume only one client license.
TFS is on the higher side, but if you intend to use the tool as a complete ALM tool, it will reduce your costs in the long run.
It's just as expensive as HPE ALM, without many of the features, best used for development tool only to avoid higher costs.
out of 38 in Application Lifecycle Management (ALM) Suites
out of 38 in Application Lifecycle Management (ALM) Suites
Compared 59% of the time.
Compared 19% of the time.
Compared 6% of the time.
Compared 64% of the time.
Compared 6% of the time.
Compared 4% of the time.
Also Known As
|Micro Focus ALM Octane||Team Foundation Server|
|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.||Visual Studio Team Foundation Server (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution. TFS supports agile development practices, multiple IDEs and platforms locally or in the cloud and gives you the tools you need to effectively manage software development projects throughout the IT lifecycle.|
Learn more about ALM Octane
Learn more about TFS
Information Not Available
|Vendex KBB IT Services, Info Support, Fujitsu Consulting, TCSC, Airways New Zealand, HP|
Financial Services Firm30%
Software R&D Company30%
Financial Services Firm15%
Financial Services Firm43%
Software R&D Company10%
Financial Services Firm18%
See also ALM Octane Reviews, TFS Reviews, and our list of Best Application Lifecycle Management (ALM) Suites Companies.