Visual Studio Team Services Quick Outlook
Fred Sookiasian | TrustRadius Reviewer
March 01, 2018

Visual Studio Team Services Quick Outlook

Score 9 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 in our organization for development and testing activities across multiple domains and multiple architectures of multiple products. The biggest business problem it addresses is disparity in branches and trunks of the applications that are being developed. Since the company is merging two vast platforms into one coming from TFS, the independent units working on shared libraries of the framework will eventually migrate everything to one unified WPF framework. Couple this with segregated API automation libraries, the global availability of shared resources with very good version controlling solves endless issues that can result in haphazard application delivery.
  • Global availability as opposed to having everything done in silos when teams are dispersed all over the world.
  • Configuration and administration that reaches out to more people and has overall less impact than having to do spotted administration.
  • Agile project management is easier to deal with in conjunction with some third-party SCRUM/Agile tools.
  • Test Automation endeavors can be quickly ramped up as opposed to using other third party solutions that require greater technical resource overhead.
  • Possibly some test management and ALM desires that are left out.
  • Some performance issues not related directly to internal network performance bottlenecks.
  • It may be pricey from an initial outlook (for larger distributed teams) and that may throw off some companies with challenged budgets.
  • Streamlined development workflows
  • Helped the integration of Agile/Scrum in all pockets of the company
  • Allow for more robust code from a holistic view, not just developer to developer
  • Allow for better test approach
In larger distributed teams or even smaller local teams, MVST is a big contender in application/architecture delivery. In areas where there might be a finite amount of resources or the development can be done more out of a "shrink wrapped" solution, without the need for large configuration of an IDE, it may be suited to stay simpler and do something else besides MVST.