2019-09-10T09:04:00Z

What advice do you have for others considering Visual Studio Team System?


If you were talking to someone whose organization is considering Visual Studio Team System, what would you say?

How would you rate it and why? Any other tips or advice?

Guest
44 Answers

author avatar
Top 5LeaderboardReseller

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.

2020-03-03T08:47:40Z
author avatar
Top 5LeaderboardReal User

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.

2020-02-12T08:38:13Z
author avatar
Top 5LeaderboardReal User

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.

2019-11-27T05:42:00Z
author avatar
LeaderboardReal User

I like the performance management of this solution and my rating would be eight out of ten. The solution works for us but nowadays I would perhaps adviser others to use a cloud-based version like Microsoft DevOps. The biggest lesson I've learned is you can have all the tools but you still have to manage the communication between developers. Even with the tools you can easily run into some issues with several people who work on the same parts of the projects. So it is very important to organize your sources the best you can. But keep the communication channels open.

2019-09-10T09:04:00Z
Find out what your peers are saying about Microsoft, IBM, Perforce and others in Software Configuration Management. Updated: October 2020.
442,283 professionals have used our research since 2012.