It is easy to scale the solution by increasing the number of agents. Our clients for Microsoft Azure DevOps are enterprise businesses.

I rate the solution a nine out of ten for scalability.

The scalability is good.

For the cloud, it has been really good. For on-prem too, it is easy enough to scale out. TFS also has always been pretty easy to scale out.

In terms of the number of users, currently, we're in a transition because we were just acquired by another company. So, we're leaving our parent company, and we're going to a new company. The numbers that I have are in flux. Our current numbers are at about 600 for just our existing or old company. I've been asked to stop onboarding my users and projects until we move our current organization into our new operational tenant in the new company, but I'm projecting that we'll have between 2,000 to 4,000 people.

It's capable of handling large volumes of data, project archives, source code, and more without any issues. Around three thousand developers regularly engage with Azure DevOps in various capacities. We have plans to expand its usage in the future. I would rate it eight out of ten.

Microsoft Azure DevOps is scalable if you have everything in place, such as the service map and processes. Before you do anything, you have to understand what the impact will be on the customer.

We had over 10 million people using this solution worldwide. I have worked in many countries, such as the Americas, Canada, and Chile. Many of our product groups were in China, India, France, and Israel.

It is a scalable solution. There are over a hundred end users in my company. Every IT hub uses it. 

The product is scalable. We have more than 40 users in our organization.

I would rate its scalability capabilities seven out of ten. Currently, approximately ten individuals utilize the platform. However, we plan to expand its usage in the future.

When you surpass a terabyte of data from a work item standpoint, certainly there are some limitations in performance as the running is querying that large data set in the backend.

I've done multiple different deployments. Sometimes, the smaller, smaller deployments have been a handful of five people, and it might be three software devs, a test engineer, a hardware engineer, and a PM. 

I've also done larger deployments where it's 8,300 people. That was a mix of hardware, software, PMs, firmware engineers, front-end, full-stack devs, mechanical engineers, electrical engineers, et cetera. 

In the deployment that was 8,300, it's actually still deployed there and growing. Another deployment I was a part of that was a medium deployment - 20 users - has since reduced more due to politics and going back to the front-end, ease of use. There are some folks that it was too high of friction to use it. You can scale it up or down to match your needs.

Azure DevOps is scalable and can be used in distributed environments and for different tenants.

The product is scalable. 

This is an area that has yet to be explored fully. We haven't taken it to this level.

We are a team of 25 to 30 members, which is fine for us. Every time we scale up we need a new license and that takes time, it's not just a click and it's done.

I don't know if it will be scalable for 200 to 300 people.

Microsoft Azure DevOps is a scalable solution. In my current company, around 30 users are using the solution. In my previous organization, more than 100 users were using Microsoft Azure DevOps.

We have around 60 users in our organization.

The scalability of the solution is good and there's no maintenance required. We're a small operation and we could grow by a factor of 10 and it wouldn't be a problem. This is an SaaS and if you need to take care of it, there's something wrong. We use the solution extensively and soon we'll have almost every piece of software, including all our test automation and embedded firmware there so we'll be increasing usage. 

We have more than 35 Microsoft Azure DevOps users in our organization.

It is difficult to customize DevOps. It's similar to a product that has had features added to it rather than being completely redesigned. As a result, it has limitations in terms of scalability and customization.

The most successful users are software developers and technical software managers.

Scalability, at least for the time that we have been using the solution, hasn't been a problem. We are able to adjust and expand any time of VMs. Any organization that needs to grow its usage should be able to do so easily.

Currently, 40 people are using the solution for one of the projects we're running. We have whoever you could think of in an agile team on it. Everybody from the business analyst to the product managers, to the testers, to the developers, and even to business end-users are on it.

I'm not sure if our organization plans on expanding its usage in the future.

Being cloud-based, this product is highly scalable, offering the flexibility to scale horizontally or vertically as needed. With a relatively small team of ten to twenty users, the scalability of the product aligns well with our requirements. It is widely utilized by both developers and the QA team.

It is my understanding that the solution is very stable. As an example, our organization has many teams and many departments and we use it across them all the time with no problem. We started using it originally when we had several teams, and now we have tens of teams, and it scaled up to meet our needs and we haven't had any issue with doing so.

There are no issues with scalability. We have approximately 50 people in our organization who are using it.

When you enter into Microsoft ecosystem, you can scale any part of the product in this ecosystem. For example, you can connect Azure DevOps to Microsoft SharePoint for knowledge or document management. You can connect Azure DevOps to OneDrive for storage. You can connect it with Skype for chatting or Outlook. 

This solution is scalable. Most of my team uses Azure DevOps and other Azure facilities, so there are quite a lot of users. 

The solution appears to be scalable.

Microsoft Azure DevOps is scalable.

We've only been using it for about three years, and so far, it seems to be able to adapt to our growth. We're maturing into it. We're moving in the direction of using it more, and I feel confident that it'll scale appropriately.

We have at least a hundred people using the tool. There are different degrees of people who are using it. Some people are using it in the read mode or view mode to keep themselves informed of where things are. We have some project managers who actually use the tool, and then we have a couple of administrators. I'm one of the administrators for our program. I have a couple of vendor or partner folks who are also administrators. We also have a development team that does some customizations on the dashboard and the Power BI reports that we do. These are pretty much different roles or layers that we have.

We do grant developers access to be able to make their own updates within the tool. Typically, project managers or scrum masters do that, but we also have some team members who are on these projects and have enough understanding of how the tool works and how we're using it. They are able to do their own reporting and their own updates on their statuses.

In terms of plans to increase its usage, we're moving in that direction. Most of our projects are done in Microsoft waterfall project management schedules, but we are being encouraged to move over to more of an Agile approach on our project methodology. Our mandate is that if you're going to do anything Agile, use the DevOps tool.

It is scalable. Currently, we have around ten users. We hope to increase its usage.

We're using perhaps 10% of what it is capable of doing. It is far more capable than what we are using right now. With further experimentation and training, I'll probably go from 10% utilization of its capabilities to about 50% or 60% in the next couple of months. We'll never use 100% of what it is capable of doing, but it should handle 95% of everything we need to do. We can always write our own plugins to handle the side things that we need.

Scalability is not really applicable with the code that we write, but the build times and things like that typically take under 15 seconds before we get our responses back. So, it works extremely well.

In terms of the number of users, there are six of us who are software developers. Some of the managers might also partially use the reporting capabilities.

It is very scalable because it is on the cloud. We have a very large user base and they're all IT-related. The users are engineers, product managers, and management. It is the entire IT organization.

Azure DevOps is highly scalable and works effectively even for large-scale projects. It can handle the demands of extensive engineering work and is generally robust in terms of scalability.

The scalability is very good.

Azure DevOps is scalable. 

The scalability of DevOps is good.

The product can scale. With the projects that I work on I just pick up Azure DevOps. It just makes sense. Everything from the beginning, for example, how the story starts right up to how it gets deployed and everything, is well laid out and you can adjust as needed.

On the project that I'm doing right now, maybe have a team of ten. On other projects, for example, at my previous company, we had a hundred devs or so using it.

It doesn't provide the level of scalability as Jenkins provides. We have approximately forty users in our company. I would rate it six out of ten.

It is a cloud-based system. So, you can add more bandwidth. It is scalable on the cloud.

We have about a hundred users who are using this solution. It is used on a daily basis.

We have about 100 users; developers, engineers and admin. The platform doesn't require any maintenance but we have one DevOps engineer to support the DevOps for the applications that we integrate with the platform. There are two types of scalability, the first is scaling my team, moving from 100 to 200 users, which is easy to do. The second is structure but  I haven't yet tested scalability in terms of increased structure.

The solution is very scalable. 

The product is scalable. That would already work with third-party platforms. In the future, I believe that the solution will be integrated with other platforms.

Around five to six people in my company use the product.

The product is deployed only at a single place in our company.

I would rate the scalability of Azure DevOps as a ten out of ten. At our company, it is used daily.

Microsoft Azure DevOps is scalable.

Scalability is great. We can add as much code as we need, and the deployed code volume can also be scaled. 

The scalability comes in the sense of creating virtual machines using IaaS, which works really well within the suite.

I'm on the DevOps team, and around 25 to 30 of us in the team itself use Azure DevOps. So, overall, there are a lot of end users in my company. 

This solution is used by 20 people in our organization.

It appears to be simple, but based on the work items and project management aspects, I believe there are few options for scaling it up in terms of dashboards and KPIs.

In general, I have seen no real issues with scalability. It is a cloud platform and scalability should usually be available on demand.  

I don't think scale applies to Visual Studio because it's a developer tool. And I haven't had a lot of experience with massive projects where multiple teams are working on the same source code. I've only worked on a team of a few people.

Others in the company may have scaled this solution. I have not explored this area yet.

We don't have any issues with the scalability of the solution. If we need to, we're able to scale.

This solution is extremely scalable.

It helps a lot in Microservices or service technologies. Using the infrastructures of code enables a productivity increase of a thousand percent. I was speaking with a company that was pulling 12 requests at one time but using competitive technology like DevOps they were able to pull over 2000 requests at the same time. It's extremely scalable and you can use it to scale down when it needs it. It's a completely autonomous product, that allows you to scale whatever you need.

I have five or six back end developers that use it every day. They learn every day, so whatever code or scripts they write are in Azure DevOps. They're not using any another tool to do it, they are pulling it with the platform because you can't tell other people about a platform if you aren't using it yourself. The first thing they do is log on to DevOps.

There will be an increase in our usage of the product. We are looking to expand at some point. The more people that come on board, the more use there is for the product.

We have approximately one hundred users, the majority of which are developers. There are some project managers and team leads, as well as different levels of management who present to stakeholders.

Currently, two or three of our development teams use Azure DevOps. In the future, we plan to include five more teams. This will grow the number of active users from one hundred to two or three hundred.

I've used it in organizations with multiple departments using the same installation, and it's scalable. We have about 20 users in multiple departments.

It's good scalability, but we need to improve the process by understanding it a lot more.

It's a scalable product. We have more than 50 users in our organization using this solution.

I plan to continue using it in the future.

The offerings in terms of scalability are good.

It is very scalable. We use it for quite a lot of projects including running the data and all that stuff. We do quite a lot of analysis and analytics on top of that.

We have hundreds of users using this solution.

We've found the scalability to be good. We have about 2,000 users on it right now. We haven't had any issues with scaling as needed. 

The solution is scalable. If we need to expand it we can do so. 

Microsoft Azure DevOps is a scalable solution.

We have more than 800 developers who are using this solution, and this is only a portion of the company. Across the company, there are many groups, and we have more than 2,00,000 employees. We are using DevOps across many customer projects and environments, and more than 50% of our projects are on DevOps.

The solution's level of scalability is good. We're a smaller organization. We've only got 300 people in total, and out of those, probably 40% of our entire staff use the product. About 120 people probably are in there on a daily basis. That's everyone from executives down to programmers. It's extremely cross-functional across our organization.

This product is very scalable. I am currently using it for about 10 users and if I want to add more then I have to pay more money.

I cannot really comment on the scalability of this solution. We are running in a microenvironment with only a few users and a few integrations. It is enough for us at the moment, but if we want to go forward and continue to work with it then that will be a discussion for later.

We have approximately fifty users right now. There are three or four administrators, and the remainder of them are end-users.

We have 5 to 10 people using this solution in my organization. We have three DevOps and the others are the QA cluster.

Microsoft Azure DevOps is very scalable. It uses techniques from Microsoft itself, so if you have the knowledge of how to deal with that, you can scale it up and out as you wish.

DevOps is highly scalable. Before one of our clients decided to move to the cloud version of DevOps, they decided to try it in a small environment to see if they liked it. Previously, they had Team Foundation Server running on-premises, and we encouraged them to switch to DevOps. We set up a minimal environment and used it as a typical development environment. It wasn't for testing or anything. It was just a mini development environment that replicated their internal chassis.

The solution is scalable but you have to pay for it.

We have approximately 40 people using this solution consisting of developers, QAs, and product owners. We are extensively using this solution in our organization.

I wish the dashboards and the release process were integrated better. The use of Kanban dashboards could be a lot better. They don't have a Kanban dashboard. They have a dashboard with one sprint but it's not exactly the same as a Kanban dashboard. You are not able to do much with them. 

The solution is very scalable. It's easy to expand.

The scalability of the solution is good. I would give it a four or five-star rating. We have plans to increase usage. Right now we have about 100 users on the solution.

It's very scalable. We started using this solution 10 years ago, and it has evolved, We also have grown our software production, and so far, we have scope with all these situations.

It is scalable. There are no issues in terms of scalability. Currently, we have around 100 users. Its usage will definitely increase because a lot of new projects are coming.

I would say that it is scalable. On a recent project, we had a lot of users and did not experience any issues in terms of performance.

DevOps is scalable. We have about 65 users working with it, including the product manager, product owner, scrum master developer, tester, line managers, and architects. 

It is easy to scale. In our organization, some teams are using it, and some teams are not using it. We probably have 80 to 100 people.

The solution is easily scalable because it runs on the cloud and everything is managed by Microsoft. We don't do anything in terms of increasing capacity so when more users are added the increased capacity is automatically managed. 

I have found the scalability of the solution to be good.

The product is scalable.

We are a small team, and therefore we don't need to scale. However, I've heard both that it grows 10% a year without issue and that it scales very easily and very well. As far as I know, a company can scale it if they need to.

We have between 50 to 70 people using it, including staff and managers, et cetera.

We have not had to scale it, as we have a very small team with only four members who use this solution on a daily basis.

Scalability is not particularly relevant. It depends on what kind of scaling you want to do. Generally, it has very good support for scaling.

There are hundreds of developers using this solution.

The solution is scalable enough for what we use it for, we have small teams of approximately 25 people. It's more than enough right now.

It is scalable.

We have approximately 20 people using the solution in my organization.

We have about 3 people using the product currently in my company, and about 30 customers.

I've never had to scale it up or down, so I can't comment on that.

Scalability has not been a problem.

As per the documentation that I have read, it's pretty scalable. My brother, who works with this solution practically every day, says it's scalable.

We plan to continue using this solution.

Scalability is fine.

It is easy to scale. We have approximately 250 employees in our organization who use this solution.

The solution is scalable, at least for our purposes. We haven't run into any issues.

We have about 1,000 users on the solution currently.

I have not tried scaling it. In my team, we have approximately 30 people who are using it.

At this time, the majority of our software application development is outsourced so there is not much in terms of DevOps. However, in the future, I am planning to implement DevOps here. Once that happens, I expect that our usage of this solution will increase.

The infrastructure is good so far, and expanding our user base isn't a problem. Microsoft takes care of the infrastructure.

Microsoft Azure DevOps is scalable. It was easy to grow.

The project that we were using the solution for was a small implementation, I cannot fully comment on how scalable it is. I did not have enough data to comment if it was good. However, we did not have any issues.

I have found the solution to be scalable, we have approximately 30 people using it.

Scalability is good. 

I have found the scalability good. We have approximately four specialists and ten testers using the solution in our organization.

DevOps is scalable. About 70 people use the solution on average. 

The solution is scalable.

We have plans to increase usage so that it will be on an org-wide scale. We plan to go up from our present number of 100 users to 300.

It is scalable. Currently, we have 400 users, and they are DevOps engineers and developers.

Scalability-wise, I have not had any problems.

We are a small company and have not had any problems with scalability.

I only tested this solution with a single user. I think that it is scalable, as long as you increase the resources as you move to a larger scale.