So far, so good. We've had one external developer consultant that had to come in and access it as well, and that went well. I don't have any gauge about how it would be for a team of 50 developers. The hardware we're running on it right now probably wouldn't be enough, but I don't feel that it wouldn't be able to scale to a larger number of developers. From a security model perspective and from a functionality perspective, it seems to have all the features to be scalable. I just don't know about the performance. That's all.

Currently, there are five of us who work with this solution. We have one project manager and four developers. We have one firmware developer who does not work in the Visual Studio environment. This firmware developer works in a microchip MPLAB X environment. All other developers work in the Visual Studio development world. So, it's more integrated, but both roles work. The same people also take care of its maintenance.

From a source code management perspective, it is being used very extensively. From a build server perspective, it is used extensively. We don't do release management with it, and we don't have integrated automated testing turned on in it as well. Those are two fairly large areas of functionality that we don't use currently. We may in the future, but we're not using them right now. We're using about 60% of the functionality.

Hundreds of users in our organization use TFS.

I rate TFS a nine or ten out of ten for scalability.

The solution is scalable, and we haven't faced any issues with TFS except for some conflicts we can resolve using the merge tool. We have about 50 to 60 people using TFS. We have about eight people working on our support team.

It is a scalable solution since TFS offers users a very good system, hardware, and efficient people to implement their tool. It is a very scalable software. Also, the scalability of software depends upon its hardware, and they provide very robust hardware.

It's absolutely scalable. If you are planning for a high availability environment, then you can definitely have a backup environment as well. Then if something goes wrong with your primary server, there is always a backup available, which you can always use.

TFS is a scalable solution.

We have approximately 10 people using the solution in my department. We might increase our usage of the solution. However, it is depending on if we add more users and if we receive authorization. We are focusing on accessing Azure Development, such as the task catalog that we have. There are developers who have full access to create and manage them.

I rate the tool's scalability an eight out of ten.

It was able to scale to meet our needs. It also allowed us to do our customization. I'm not sure if that ended up being a good thing, but it did allow us to do what we wanted it to do.

We have about 150 users, and they're developers, FQA, software quality engineers, business analysts, user experience team members, and architects. For its deployment and maintenance, in general, there are four or five people. They are from the DevOps team.

We don't plan to expand its usage. We're transitioning to Jira.

It can be scaled to some extent. The main issue is that, unlike Jira or any other tool, the burndown chart is not displayed.

The solution is scalable, however, we do not need to scale because we do not have many people on each team. The administration part requires three or four people, and for development teams, we have about 15 team members who actively use VS Code.

It's scalable. We have around 45 users.

TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools.

We have more than 200 users using this solution.

The solution is scalable. 

TFS is scalable because it is managed by Microsoft internally. 

No.

My company has more than 50 users. 

It's a scalable solution. We have 100 users in our organization.

For large organizations with more than 200+ concurrent users, there can be some scalability issues.

It is a scalable solution. Presently, twenty to thirty users are using the solution. 

TFS' scalability is quite good. My company has 25 users. 

We have encountered no issues with the solution's scalability. 

The scalability of TFS is good.

We have approximately 50 people from our IT teams that are using the solution in my company.

I rate the scalability of TFS a six out of ten.

It's completely scalable.

I would rate the scalability a six out of ten. Sometimes, a lot of branches get mixed together, making it difficult to use. I remember struggling with these branch management issues some time ago and even wrote about them. It is so hard to review problems in TFS.

There are around 200 end users using this solution in our organization. 

It's scalable.

This is not a scalable product. We have about 35 users in our company.

No. However, my user base has always been relatively small:100–200 users.

TFS is quite scalable and there are different deployment options that are available. I don't see any problems with scalability. We have between 40 and 45 people in my department who are using TFS.

No issues have been noticed in scalability.

The solution's scalability is a six or seven.

TFS is a very scalable product.

The scalability of the solution is very good. If a company needs to expand outwards and grow they should be able to fairly easily. We've had not trouble with that aspect of the solution.

This solution has some scalability.

TFS is not that scalable compared to Jira. It's scalable at the story level and at the project level but in the grand scheme of things, it's hard to manage it from an entire product perspective. 

This solution is scalable and it is simple. 

From my experience, we have loaded a lot of work and we have several branches.

We have perhaps one hundred users, but in my team specifically, we have eight users who are engineers, testers, and a few managers.

No issues encountered.

It is a scalable solution. I rate its scalability eight out of ten.

I have no issues with the scalability. It is fine. 

I have never run into any limitations. We have three individuals in my department using the solution and another six using it in the IT department.

It is possible to scale, albeit tricky. There are between 2,000 and 3,000 users.

No, but I have never worked in a big company with many developers or projects.

No.

No issues encountered.

The scalability of TFS is good.

We have approximately 200 users using this solution in my organization.

Nope.

Nope.

I didn't encounter issues with scalability.

This is a scalable solution. Our company has 1,300 employees, although there are only between 50 and 100 who use TFS.

I am not involved in this aspect of TFS’ evaluation.

TFS is a scalable model. If I have to look into large projects, we have multiple agile teams having different backlogs. Having a view on this is rather scalable.

We have approximately 28 users for this current project, and we are using it on a daily basis.

We plan to keep using TFS.

No.

No issues encountered.

No issues encountered.

No issues encountered.

We are using a single server deployment with more than 150 projects and never had any issues. Of course, some pre- and post-installation optimization has to be done like SQL Server, etc.

No, it is very easy to scale it up.

No.

No.

There were no scalability issues.

No issues encountered.

No issues encountered.

No issues encountered.

No issues encountered.

This is a scalable solution. I have plans to increase usage.

Nope. The product is absolutely scalable for use in large enterprise companies.

This is a scalable product. We have more than 50 users.

The scalability of the solution is good. There are 20 developers in my specific project who use TFS for storing the code repository. We work on multiple projects so there can be anywhere up to 25 people in the company using the product at any one time. It's a development tool so we use it on a daily basis as a centralized code repository.

No.

No issues encountered.

No issues encountered.

No issues encountered.

No issues encountered.

No issues encountered.

I have found the solution to be scalable. There are approximately ten people using the solution in my organization.

I would rate scalability as a six out of 10.

No issues with scalability.

It can be used for a lot of web tests and Windows testing. I do API tests with Fiddler via MTM.

No issues encountered.

Nope.

None.