The scalability is pretty good. We did some load tests in advance, before making the decision, pro or con, on Octane. With Octane we are in a very good position. We expected to have some 5,000 users by the end of 2019/beginning of 2020 working on Octane. I believe it can go up to 2,000 users working in parallel. We hope to be powerful enough, with the architecture and everything else we set up, to meet users' expectations of performance.

We are involved in further step-by-step expansion of our use of Octane. For this year, we are planning to extend the native Octane usage of test automation, the DevOps module. We are introducing it and maybe we will be able to replace some home-grown and other tools and to integrate them into Octane to have the benefit of Octane. It would be helpful to have everything in one place for the monitoring and reporting possibilities. Our processes and needs are changing from time to time, and this is always reflected in the test management tool.

It's extremely scalable. It's an enterprise solution for lifecycle management.

As a rep, I’d always like to increase usage. In general, there's a total direction to increase exposure to ALM Octane.

There's no problem with scalability. 

I don't see any limitations in the product's scalability. Scalability-wise, I rate the solution a ten out of ten.

There are more than 1,000 users of the product in my company.

The usage is going up pretty fast. There will probably come a point where we need to scale. The new architecture for Octane is quite different than HPE ALM. It allows us to scale. We're not quite there yet.

We have over 3,000 users, about 85 concurrent. It's a globally active application. It goes around the clock. We have North America, Europe, Asia-Pacific, and Latin America.

It is scalable. It is just about adding more power and more Elasticsearch servers, and you should be fine.

We have about 500 different users daily.

We have 14 people using the solution in my company. We might increase our usage of the solution depending on the project we have.

I rate the scalability of Micro Focus ALM Octane a nine out of ten.

Micro Focus ALM Octane is a scalable solution.

I have worked with around 400 OpenText ALM Octane customers. It works well for synchronizing data.

I haven't seen any significant requirements in my company regarding the scalability aspect of OpenText ALM Octane.

Scalability-wise, I rate the solution an eight to nine out of ten.

Around 250 people, consisting mostly of QAs and software engineers in my company, work on the solution.

We have 220 users on it. I have spoken to clients who have 3000 users on it. It's relatively scalable. We haven't seen any performance issues at all as we have ramped up the amount of data that we have on it or the amount of users. Our users include scrum masters, developers, testers, product turners, subject-matter experts, and business intelligence analysts.

In terms of usage going forward, we will rollout to our operations department. We'll get Ops using the same platform, so that should be another 60 to 70 users. The benefits of this would be that we would have more work concentrated all in the same place. Therefore, we can have a lot of crossover between other departments which aren't currently on ALM Octane that we can get onto Octane. This would make it work better and make it easier to manage because it would be a single place for work to be referred between teams, as opposed to having to go to a different tool if someone needs something hardware or software related to be created. 

The number of individuals participating in the deployment process varies. Our company provides testing services, employs 34,000 individuals, and many of our clients utilize Micro Focus ALM Octane. This implies that many people use this tool, after considering 34,000 end-users from our company's end who are using Micro Focus ALM Octane.

For deployment, the number of required tech engineers depends on the size of the project. For installation, one or two people may suffice. However, for usage, there will be many others who need to use it.

The tool itself does not require any maintenance. However, it may require customization based on the specific needs of each customer. Workflows may need to be customized to meet the unique requirements of each customer.

It is a scalable solution. Scalability-wise, I rate the solution a nine out of ten.

I'm in SaaS. If it slows down, I just call them. They increase something, whether its memory, CPU, or disk space. Scalability is pretty much a non-issue.

I have found Micro Focus ALM Octane scalable.

We have approximately 250 projects using Micro Focus ALM Octane. We are a  small team of 10 to 20 people that varies at times. Our performance-driven teams and we have been releasing month on month. We are finding it very easy and comfortable with Micro Focus ALM Octane. 

Since the ALM Octane is outsourced for us and another MNC provides support, regarding scalability, we as customers to them have observed it's highly scalable - addition of servers to handle thousands of requests/reposne from end users - agile/scrum teams/project managers/ stakeholders to manage backlog is easily met. There is no lag in response time, never did the pages hang. I never waited for Dashboards to collect data and show up, it's just in a fraction of seconds. 

Also, latest in DevOps technology like Azure DevOps for CI/CD is easily implemented. 

ALM Octane is very scalable. We have a great server team that we use to increase its space or size. We handle it internally, but it works great. 

The scalability isn't good.

It is scalable. We can add additional nodes without a lot of effort, if it is required. There is an option to scale from a license point of view. From a hardware point of view, we can also add multiple nodes to support additional loads.

We have about 1,000 users. 

The performance issues that we have come about when we have load on the system. We're trying to figure out if the source of those issues is the environment, and what the optimized settings would be for the environment: memory size, number of disks, things that we're doing in our performance testing, etc. But we're also looking at the software to see if there are any issues there.

We are working with about 180 to 200 concurrent users, which isn't a terribly high number. We're looking at all sorts of angles but we're currently in the middle of it, so it's hard to tell what the source of the issue is.

Micro Focus has definitely been good about helping us out with all of that, giving us advice, hardware related, on what our settings should be. Maybe we're not sized exactly correctly. According to Micro Focus - they also, of course, do their own performance testing - and they haven't seen the results that we have.

We have projects and teams with several hundreds of users and tens of thousands of records (requirements, tests, etc.). There are risks with not being able to copy a workspace to test changes to the CI/CD or pipelines, so that is a miss. The reporting is limited to a few thousand records so we've had to request an override to the limits - but Micro Focus delivered on this immediately, once we stated the case.

Micro Focus ALM Octane is a scalable product.

We have approximately 500 clients who are using this solution.

They are large enterprises and digital transformation, IT engineers, more business-oriented than DevOps-oriented.

The scalability is excellent. I don't think there is a limit.

We use it quite extensively. We have about 30 teams working on it with approximately 10 projects, and we are definitely expanding.

The extensiveness of integrations into the DevOps ecosystem in the 15.1.20 version to support scalability has been very applicable to our business. We have integrated the solution with Jenkins, which was user-friendly. We also integrated Octane with Qlik Sense and QlikView for people for whom we do not want to give access to the system but want to have them viewing our reports. Therefore, I think the scalability is very wide. 

On my team, there are 18 users who are testers. Overall, there are 20 licenses.

We've only got 20 live projects in there right now. So I don't see any issues with it. Until we can put some massive projects in there. We've taken one 65-gig project from Agile Manager and ported that into Octane. We don't see any degradation, but that was still prototype.

This solution is scalable, but additional servers may be necessary depending on how many users you add.

We haven't tried scaling yet because we just started and we have about 20 projects in there which are not such big projects. But we haven't had any issues so far. We have confidence, after using ALM for so long, in scalability, the way HPE - before Micro Focus - are doing it. We hope that, they will do the same thing.

We haven't put scalability in place yet because of what I explained earlier. Previously, we had two servers for our Quality Center system platform and, with the same number of users, we've got just one application server with Octane. We haven't used the scalability yet.

I think it would scale. We've not needed to scale too much yet, but it seems scalable to me.

I think that the biggest obstacle to scaling with this particular tool is the licensing. You predict what licensing you need for the year, a whole year, and you're stuck with that for that year, unless you pay more to scale up. That's always a challenge. The challenge is not the scalability of the solution but the scalability of licenses.

We've just upped our licenses to 25. We started off with ten. Once we get to steady state, in some six months' time, we'll have about 30 steady-state silences.

Regarding the increase in usage, we'll push more work through it. Right at this moment it's just one program of work. Once we're happy with the way we use it, the stability, we'll then push all our organization's work through Octane, rather than ALM.NET. At the moment, the majority of our work is going through ALM.NET. It's just this transformation program that I mentioned where we're using Octane. It's almost a proof of concept for us. If it works with that program, we'll make it work for all programs.

It is scalable. We do need to explore it more to determine its support for a scalable framework. 

Octane is scalable. We're looking to scale up in the next year.

I imagine it should scale very well. We're using it kind of in a limited basis now, but going forward we're going to use it for a very large project with up to 100 testers. Because we're using the SaaS solution, and because we used the ALM HPE QC product before, and SaaS, I don't see any reason why it can't be scaled the same way. So, not too worried about the scaling.

very scalable for Scaled Agile For Enterprises

This is a scalable product. We have more than 50 users in our company. Some of them are Q&A while others use a different license for development. We will very likely increase our usage in the future.

We did not stress-test it to see what it would be like in a mega environment. Usually we deployed it in a medium-sized environment, with 20 to 30 developers, and the scalability was okay.