I give the scalability a seven out of ten. We had hundreds of employees using the solution.

The tool is scalable. We have 15 users on our team. There are more than 100 users in our organization.

IBM Rational ALM is a scalable solution. More than 1,000 of our customers use the solution.

I would rate the scalability of this product a nine out of ten. It is very scalable and can handle large numbers of users and transactions.

I have clients of all sizes, from small businesses to large enterprises.

IBM Rational ALM is scalable. 

We have a large team of 30 people using the solution.

IBM Rational ALM is a scalable solution. We have almost 3,000 people using this solution.

I don't know how scalable this product is. We have approximately 6,000 users but whether it might support 10,000 or 12,000 is something that I don't know because I haven't tried it.

It runs inside a mainframe computer that has a lot of power. However, even with 6,000 users, it is not very stable.

IBM Rational ALM is a scalable solution. It is used by everyone in our organization. We have thousands of users.

We did not have any problems with scalability.

I manage 500 people who use the product.

The solution is pretty scalable.

The tool is quite scalable, from the deployment side or be it be from the tool functionality side. If you are a part of the development teams it helps you. But I'll say there is room for improvement that could help us. For example, in regards to DOORS and Rational Team Concert, the development with respect to the Java script is limited, while for Java, the capacity is quite huge.

It's scalable but you need a lot of background knowledge if you want to scale the solution.

In my company, we have four or five locations in total, so all together we have somewhere around 500, 600 users. 

The deployment and maintenance only require two to three people but they don't work on it full time. 

We did have plans to increase usage in the past. Recently, we have had some struggles with our events. We had some problems with Rhapsody Design Manager. It took me six months to get it stable and I still struggle with it. I don't think that we'd increase the userbase anytime in the future. 

The scalability of this solution is good. 

Currently, the IT and software development departments are using this solution. I believe that is about 50 people.

We are using the Community Edition rather than the Enterprise version, just to create PoCs, pipelines, and showcase them to the business. We have not tried to scale beyond this.

We have between 30 and 40 architects who are using it, and we are all involved in creating new solutions and new architectures.

We are happy with the scalability, although it is related to licensing. We have different types of licensing including concurrent floating and stakeholder. I think that we have 12 concurrent licenses and a total of 50 users who are assigned to these different concurrent pools.

To this point, we have not needed to scale. If we extend the functionality and integrate it with the DevOps tool, with respect to continuous integration and continuous deployment, then we may increase our usage.

We never really needed to scale the usage a lot, but we never had an issue adding users or projects, so scalability is good.

Scalability is not really an issue for us because we don't have a lot of users. The license is expensive. We have a limited number of concurrent users. We haven't tested the scalability. With our limited number of users, the performance is okay, the availability is okay.