We just raised a $30M Series A: Read our story

Visual Studio Team System OverviewUNIXBusinessApplication

What is Visual Studio Team System?

Microsoft Visual Studio Team System is a platform for productive, integrated, and extensible software development life-cycle tools that helps software teams by improving communication and collaboration throughout the software development process.

Buyer's Guide

Download the Software Configuration Management Buyer's Guide including reviews and more. Updated: November 2021

Visual Studio Team System Customers

Bluegarden A/S, Tracasa, Rabobank Group, Borusan Otomotiv, Arelik, Alfa Bank

Visual Studio Team System Video

Pricing Advice

What users are saying about Visual Studio Team System pricing:
  • "The price could be better."

Visual Studio Team System Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Fad Mohi
Head of Software Development Department at ACT
Reseller
Top 5Leaderboard
Good code management and sharing capability, but needs better integration with the documentation

Pros and Cons

  • "The most valuable feature is the code management, where there is sharing of code for developers and it is distributed within the organization."
  • "The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved."

What is our primary use case?

We use Visual Studio Team System as part of our development environment. This is the core system to manage our code and our development life cycle.

How has it helped my organization?

Prior to implementing this solution, we had a lot of fear of losing our code due to some kind of situation that was outside of our control. At the same time, our team was distributed between different regional locations both inside and outside of Lebanon. When we started using this tool, it was a great way to have full access to all that was being developed between different areas.

What is most valuable?

The most valuable feature is the code management, where there is sharing of code for developers and it is distributed within the organization.

We have lately been trying to use the built-in functionality for task management and software lifecycle development. This is a new feature and it is pretty good. We are just in the evaluation phase, comparing it to other task management tools.

What needs improvement?

The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved. This includes assigning tasks, as well as reviewing those that are pending or ongoing. For example, Jira has an excellent user experience, and it should be more like that.

We would like to see better integration of documentation.

For how long have I used the solution?

I have been working with this solution for about seven years.

What do I think about the scalability of the solution?

We have ten people who use this solution in our company.

How are customer service and technical support?

We have not been in contact with technical support.

Which solution did I use previously and why did I switch?

Prior to this solution, we used to use Visual SourceSafe.

How was the initial setup?

When we first implemented this solution, we had some hiccups because earlier versions needed SharePoint and a special Active Directory to be set up. It was not easy or straightforward. We had to separate our Active Directory and the company corporate directory into three directories. One for activities, one for the company, and one for the development team alone. In general, the older version was a little bit complicated. It took about one week to prepare and set it up.

The latest, cloud-based version is much better in terms of setup.

What about the implementation team?

Our in-house team handled the implementation. The first time we deployed it, three people were involved in the process. Maintenance is not required for this solution and we have one system administrator.

Which other solutions did I evaluate?

We did not evaluate other options when we switched from SourceSafe to TFS.

What other advice do I have?

My advice to anybody who is considering this solution is to first decide what they need out of it. The benefit of each solution is becoming multidimensional. For example, TFS can be used for managing code, managing software, and lifecycle development. People have to decide which dimension they need to use and then focus on it. Later, they can go to explore and use other dimensions. Otherwise, they will lose a lot of time trying to learn and to adapt to the solution. This is the biggest lesson that we learned from our implementation. Once we mastered its use in one area, we moved on to the next.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Distributor
TelgePeiris
Technical Lead / Project Manager at a financial services firm with 51-200 employees
Real User
Scalable, flexible, and easy to set up

Pros and Cons

  • "Microsoft makes great products. They are quite robust."
  • "When you go into the front-end, the web portal, if, for example, you pick up an issue, it would be ideal if the branch was automatically created in the repository. Right now, this isn't the case."

What is our primary use case?

We primarily use the solution for remote repository and management and source control.

What is most valuable?

The analyst feature is very useful to us.

We like that it's quite flexible and you can make a variety of changes using it. There are all kinds of different tasks you can leverage.

The initial setup was straightforward. 

Microsoft makes great products. They are quite robust.

The solution can scale.

The stability is good.

What needs improvement?

Sometimes it gets tough when you're dealing with a larger process if you're accessing it through the VPN. If you're not on the local network, you're accessing through the VPN, which already makes it slower in general, and then on top of that, if you're accessing a really large process, you're going to feel it slow down even more. The product sort of gets stuck when you're trying to connect and operate for the first time. 

When you go into the front-end, the web portal, if, for example, you pick up an issue, it would be ideal if the branch was automatically created in the repository. Right now, this isn't the case.

For how long have I used the solution?

I've been using the solution over the last 12 months. I've used it for a while.

What do I think about the stability of the solution?

The solution is pretty stable. I used it on an earlier job and it was fine. There were no bugs or glitches. It doesn't seem to crash or freeze. It's good overall. 

What do I think about the scalability of the solution?

The solution scales quite well. I've used it in larger companies and it was great. At my previous employer, I had 100 or more programmers and the product handled everything like a charm, no problem.

How are customer service and technical support?

I've never had to contact technical support. I guess that says something about the quality of their service that I've never had to call them up. However, since I have never spoken with them, I can't directly speak to how helpful or responsive they are.

How was the initial setup?

We found the initial setup to be pretty simple and straightforward. It was not very complex or difficult. An organization shouldn't have too much trouble with the initial setup.

What's my experience with pricing, setup cost, and licensing?

We have an enterprise license. That's an aspect that the company handles. I don't directly deal with sales or licensing.

What other advice do I have?

We're just customers and end-users. We don't have a business relationship with Microsoft.

I've been using the latest version of the solution.

For those considering the solution, I would advise that they decide between a centralized or distributed repository - and then choose VSTS. For a more centralized repository, VSTS is the nicest I've used so far.

I'd rate the solution at an eight out of ten. We've largely been happy with the solution overall.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Find out what your peers are saying about Microsoft, IBM, Perforce and others in Software Configuration Management. Updated: November 2021.
552,305 professionals have used our research since 2012.
DG
Dynamics 365/Ax Technical Consultant at a tech services company with 10,001+ employees
Consultant
Top 20Leaderboard
Easy to use, straightforward to set up, stable, and scalable

Pros and Cons

  • "I am not familiar with any issues with respect to stability, and I have never seen Team System crash."
  • "I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see."

What is our primary use case?

Visual Studio Team System is kind of ubiquitous in programming because it's also what a lot of systems use for their source control. It is generally used for source control and deployment, and I have a couple of clients that use it as their ticketing system. In this capacity, it is used for setting up features to be developed in running through their development processes.

What is most valuable?

This product is easy to use compared to Git, which is the alternative source control system that Microsoft is trying to push these days. Git is very difficult to use properly and it is not as feature-friendly as Team System used to be.

What needs improvement?

I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see.

For how long have I used the solution?

I have been using Visual Studio Team System for approximately 10 years.

What do I think about the stability of the solution?

I am not familiar with any issues with respect to stability, and I have never seen Team System crash.

What do I think about the scalability of the solution?

I have never had any problems with scaling. My clients generally work on projects that have anywhere between one person and 80 people working on them.

How are customer service and technical support?

I have never spoken with technical support.

Which solution did I use previously and why did I switch?

I did use alternatives, but it was going back to 2005 or 2006 and I don't remember what it was that we used back then. These days, it is so ubiquitous for Visual Studio development that I would not even think about it.

How was the initial setup?

The initial setup is pretty straightforward. If it's in-house then you just deploy it to a server. I think that it comes with its own SQL database, as well. Then, you just link Visual Studio to the implementation and start adding files.

The installation is seamless as to what I usually do.

What about the implementation team?

We have an in-house team for deployment and maintenance.

What other advice do I have?

The features are fine for what it is. It works very well. It's designed for a specific niche, which is a very big niche. In summary, this is a good product that is straightforward, easy to use, and manages well.

It's a fine product.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
JS
Software Engineer at a financial services firm with 10,001+ employees
Real User
Top 20Leaderboard
Fast and responsive with a comprehensive functionality that is good for writing and debugging code

Pros and Cons

  • "IntelliSense and CodeLens are helpful because they can show you details about your function, such as how many times it is called from other places within the code."
  • "I would like to see the inclusion of more programming languages, especially better support for Java."

What is our primary use case?

I used this solution for software development, writing and debugging code.

What is most valuable?

What I like most is that it is a very comprehensive product.

IntelliSense and CodeLens are helpful because they help you (auto)complete your code, can show you details about methods, such as how many times it is called from other places within the code and where.

Debugging functionalities are useful too.

I also like the structure of how it creates solutions and programs. 

Visual Studio is quite fast and responsive compared to some other programs that I have used.

What needs improvement?

I would like to see the inclusion of more programming languages, especially better support for Java.

For how long have I used the solution?

I have been using the 2015 edition for some four years. I started using the 2017 version more recently, perhaps four or five months ago.

What do I think about the stability of the solution?

I did have some issues with the 2015 version where on very few occasions it froze or just crashed. With the 2017 version, I have never had this problem. I have to say that with the 2017 version, the stability has improved.

What do I think about the scalability of the solution?

We have perhaps 50 to 200 users in our company. We are spread over different locations and we have about 50 users here, whereas we have up to 200 globally.

How are customer service and technical support?

I have never had the opportunity to speak with Microsoft directly because our company is supported by our internal group.

What other advice do I have?

The 2017 version is similar to 2015, they have added a few things. One difference is the setup experience, although it is not a groundbreaking change. I know that they have released a new version, 2019, that allows for sharing of what you see also remotely. You can work on code with your colleague who is developing somewhere else, remotely.

When it comes to this solution, I am not really missing anything I needed from an IDE.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jan Meeremans
Owner at Myriade
Real User
Leaderboard
It is stable and scalable and the setup is really straightforward

Pros and Cons

  • "The solution is pretty stable."
  • "The technical support could be better."

What is our primary use case?

Our primary use case of this solution is to search for smugglers and for people who have open files. So we integrate everything with GDPR and then we distribute this in most parts of Europe. We have some interests in the United States too.

What is most valuable?

What I like about this solution is that it is one big framework, which everybody knows, so one can quite easily start-up new developers using it. 

What needs improvement?

We are looking forward to the new Blazer system that is coming out soon. It is currently in beta on the service side, so we are looking forward to the new version that will be on the client side too. I also would like to see an improvement in the technical support.

For how long have I used the solution?

I have been using Visual Studio Team System for more than ten years now.

What do I think about the stability of the solution?

The solution is pretty stable.

What do I think about the scalability of the solution?

The solution is very scalable. We integrate this in SQL and we can do this vertically as well as horizontally; in both directions. We have 15 users that are using the regional pseudo team system within our company, and they are all developers.

How are customer service and technical support?

We pay additional fees for support, and it is doable. It is not the best support, but it is definitely acceptable. That is perhaps something that needs to be improved. 

How was the initial setup?

We did the installation and setup ourselves and it was really straightforward.

What other advice do I have?

My advice to others would be to go all the way with this solution. Don't try to find a cheaper solution. On a scale from one to ten, I rate Visual Studio Team System an eight and I'm looking forward to the new Blazers system.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
TA
Process Manager at a marketing services firm with 501-1,000 employees
Real User
Top 5Leaderboard
An easy to install solution which is scalable and stable

Pros and Cons

  • "The solution is scalable, stable and has allowed us to upgrade our frameworks."
  • "Support response time could stand improvement."

What is our primary use case?

The solution helps the project teams to take care of all aspects of the processes for software development.

What is most valuable?

All is fine with the solution. It is scalable, stable and has allowed us to upgrade our frameworks.

What needs improvement?

It would be nice to see some of the authentications compacted to the solution which are done with Nudi.

Support response time could stand improvement.

The price could be better. 

For how long have I used the solution?

We have been using Visual Studio Team System for the last five years.

What do I think about the stability of the solution?

The solution is stable. 

What do I think about the scalability of the solution?

The solution is scalable. 

How are customer service and technical support?

Response time could be faster. 

Which solution did I use previously and why did I switch?

We did not use other solutions prior to the current one. 

How was the initial setup?

Installation is easy. 

While I do not recall its exact duration, this should be around four hours. 

What about the implementation team?

Installation can be done with the help of the technical team.

The size of the team should be the same as that which we used, three to four people, consisting of managers. We have one IT manager. 

What's my experience with pricing, setup cost, and licensing?

The solution could be more cost-effective. 

There is an annual licensing fee. 

What other advice do I have?

If price is not a consideration, then my recommendation to others is that they go with the solution. 

The solution is cloud-based.

I rate Visual Studio Team System as a seven or eight out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
Download our free Software Configuration Management Report and find out what your peers are saying about Microsoft, IBM, Perforce, and more!