Microsoft Team System a way for developers to work at the same time on a project without any hassle.
Rahul Kumar Singh | TrustRadius Reviewer
August 31, 2018

Microsoft Team System a way for developers to work at the same time on a project without any hassle.

Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Microsoft Visual Studio Team System

Microsoft Visual Studio Team System is being used by the dev team in the organization. As every developer is a part of a project, every developer has to access the TFS (team foundation server) in order to contribute to the project. MVSTS is solving some major business problems. For example, it allows version control of a file as the whole team is working on the project. TFS provides each developer a local copy of the file, as well as the server version. Developers can make the changes to their local file and test it and if everything goes well, then they can update it on the server for the customer.
  • Version control of the files: each developer has access to the server and regularly gets the latest server changes in his local box. The local file is maintained and also remains updated with the server version. The program also provides a different copy of a file so that it can be recovered in case of a failure from any individual developer box.
  • Some features like shelveset creation, work item monitoring, and publishing the project database.
  • I can access any developer's local box and see what changes he is doing if he has shared the shelveset with me.
  • Applying any new changes and undoing them using the pending changes feature.
  • Once, I added a PDF file to my shelveset so that I could share my changes with my team, but they were unable to unshelve my changes. This is because PDFs cannot be opened in more than one box, and it was locked on my box. So, I had to undo it from my box, and even then it was only accessible to one person at a time. It was problematic. They should at least be able to open it in read-only mode.
  • Lots of settings are necessary. However, if you accidentally uninstall one, instead of having to install it again, there should be a backup kind of thing for my profile settings in Visual Studio.
  • The default compare and merge tool provided by Visual Studio does not fill our needs, and we need to install other products like Delta Walker or Araxis Merge.
  • Positive impact:- They have good features that are very crucial for the organization's development and reporting team.
  • Positive impact:- Every developer is already familiar with Visual Studio's features, so in this sense return of investment is also good.
  • Negative impact:- This technology is becoming obsolete and more advanced technologies are coming onto the market.
Microsoft Visual Studio was on the market when there were no other providers for this type of service. So if a company was already working on this technology, it will always provide a better output than if they migrated to a new one. However, when comparing GitHub with Microsoft Team System, it's very close, but GitHub is leading in this, in my view.
For large project or a large team, the product is well suited when this technology is already implemented, because nowadays for version control there are products like GitHub. For a company who is concerned about security, this is a way to make their projects accessible from their TFS, and no one can use it for personal use. This is also useful for maintaining a site that a group of developers are working on, where their work items need to change, like peer test, peer review etc.