Azure DevOps Server (formerly TMS)

Azure DevOps Server (formerly TMS)

About TrustRadius Scoring
Score 8.1 out of 100
Azure DevOps Server (formerly Team Foundation Server)

Overview

Recent Reviews

Still TFS to Me

9 out of 10
April 14, 2021
Our dev team uses [Azure DevOps Server] to receive requests for our site from all departments in the company. I have used it as a …
Continue reading

Fostering Innovation

10 out of 10
October 03, 2019
The Azure DevOps server is used within our IT department. We use it to have simplified server management and improved connectivity with …
Continue reading

Reviewer Sentiment

N/A
Positive ()
N/A
Negative ()
Learn how we calculate reviewer sentiment

Awards

TrustRadius Award Top Rated 2020

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Azure DevOps Server (formerly TMS), and make your voice heard!

Pricing

View all pricing
N/A
Unavailable

What is Azure DevOps Server (formerly TMS)?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

7 people want pricing too

Alternatives Pricing

What is Jira Software?

JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.

What is Bitbucket?

Bitbucket from Australian-headquartered Atlassian offers source code management and version control.

Features Scorecard

No scorecards have been submitted for this product yet..

Product Details

What is Azure DevOps Server (formerly TMS)?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Azure DevOps Server (formerly TMS) Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Comparisons

View all alternatives

Frequently Asked Questions

What is Azure DevOps Server (formerly TMS)?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

What is Azure DevOps Server (formerly TMS)'s best feature?

Reviewers rate Usability highest, with a score of 8.7.

Who uses Azure DevOps Server (formerly TMS)?

The most common users of Azure DevOps Server (formerly TMS) are from Enterprises (1,001+ employees) and the Information Technology & Services industry.

Reviews and Ratings

 (224)

Ratings

Reviews

(1-25 of 39)
Companies can't remove reviews or game the system. Here's why
Christopher Sawyer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using Azure DevOps [(formerly Team Foundation Server)] in our IT department to help us with Agile software development. It helps us to track code changes with various work items like Tasks and Bugs. It also helps to test, build and deploy those changes to multiple environments. It easily integrates with Visual Studio to create a seamless experience.
  • All-in-one product (don't need a bunch of separate connected products)
  • Integrates easily with other Microsoft products
  • Can use git or its own version control with less steep learning curve
  • More stable than Atlassian products
  • No clear-cut way to track items in a release, especially if they are not code change related
  • Agile boards still lag behind Jira in terms of functionality
  • Bamboo and Confluence have nice features over DevOps Build and Sharepoint
More stable than Atlassian products but not quite as feature rich. I've supported both TFS (now Azure DevOps) and Atlassian products in the past. Nice to have an all-in-one stable suite but you may not have quite as many bells and whistles. I would choose less features over having to restart servers.
Mark Orlando | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps to manage and store all our corporate source code and deploy our applications to a string of various environments from development to production. In addition, we use Azure DevOps on a daily basis to manage our agile-based projects. Azure DevOps is used to track and follow the progress of customer support tickets as well. Our business analysts use the Agile Project Management feature to log user stories.
  • Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
  • Our business analysts use its features to document and assign user stories for Agile-based projects.
  • Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
  • For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
  • Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
  • The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
Azure DevOps works great if you spend most of your day in Visual Studio. If you plan on using VS Code, then skip it because Azure DevOps doesn't really work with VS Code. VS Code works with Git. For project management, Azure Dev Ops is okay, but project managers need to provide their team with links to where things are. Additionally, you might be better off using OneNote to document requirements and simply add links to your user stories where developers and testers can read the stories. The Word-like editor in Azure DevOps is extremely primitive.
Microsoft supports its products well. Considering the complexity of managing all the software built by a corporation, DevOps is perfect. It never messes up code merges - an incredible feat by itself. There is certainly room for improvement in the product, but considering it brings agile project management features, software deployment and source code management in one package it really can't be beaten.
Ross Borissov | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps in our business unit as an end to end solution for our ALM / SDLC. We have several organizations with various projects, repos and pipelines. We are following Scaled Agile Framework (SAFe) which is well served by Azure DevOps backlog module. We are happy that we could back trace a cloud release through the pipelines back to the work items in the backlog.
  • End to end tracing of released artifacts
  • Scaled Agile Framework implementation with Azure DevOps backlog
  • Versatile and powerful pipelines as code
  • Ability to automatically link automated tests executions to Test Cases
  • A better file editor (like VS code) in the git repo UI
Well suited:
  • Large teams developing heterogeneous applications
  • Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
  • Company undergoes regular external audits of their SDLC practices
  • Comprehensive reporting is required
  • Pipeline templating is required
  • Many git repositories are needed having to link to a unified backlog
  • Access to backlog work items and reporting is required for business stakeholders
Jeffrey Staw | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
The biggest and best use of Azure DevOps Server (formerly Team Foundation Server) is the gathering and management of user stories for development, coupled with the other elements of information sharing and the metrics it can provide. The ability to track bugs, and the fixes to those bugs, and generally track the evolution of your agile development group is a major plus. While primarily focused on the development organization, Azure DevOps Server (formerly Team Foundation Server) is used by the lines of business by product owners and their associates.
  • User story management
  • Integrations with other products
  • Reporting
  • It does not necessarily play very well with non-Microsoft stacks
  • Upgrades have been cumbersome; however, with the cloud offering, that is mostly off the table as a major issue
  • Some of the search functionality is unclear and difficult to use
  • Could have more pre-built templates; it offers so much it can be challenging at times
If you are a large organization that needs structure, Azure DevOps Server (formerly Team Foundation Server) is a great place to go. It does really benefit from others that have experience with the tool--that is a major plus. Azure DevOps Server (formerly Team Foundation Server) is particularly well suited for organizations that are looking to become more agile in the way they do business, especially in the way they code.
April 14, 2021

Still TFS to Me

Jordan Comstock | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Our dev team uses [Azure DevOps Server] to receive requests for our site from all departments in the company. I have used it as a marketing user. It is being used across the entire organization. It helps to address the business problem of prioritizing the work that we need to be done on our website.
  • Orginazation
  • Notifications
  • Complex nesting of projects
  • So many options, getting the team on the same page
  • Formatting
  • Tricky for new users
We still call it TFS. It is very useful for our marketing team and working with our developers. Every time we have a page, a bug, a user story, or an epic project, we can put the details into [Azure DevOps Server] and work back and forth with our dev team in there to complete the work.
Score 10 out of 10
Vetted Review
Verified User
Review Source
TFS is used for ALM of all in house supportive software, development of our flagship product and clinical studies for our latest version. TFS acts as a central hub for requirements, code, tests and reports. It links these facets of the product life cycle together.
  • Linking together all aspects of the application life cycle, from requirements to code to builds and test.
  • Trace-ability of all application life cycle via reports and queries.
  • Automated testing.
  • Flexibility of source code management. Centralized or distributed.
  • Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
  • Capacity planning could be improved.
  • Dot Net framework 260 character path limit is ridiculous.
Team Foundation Server (TFS) is best for large scale enterprise deployments. Not needed for a small company. With the infrastructure investment, TFS can aid large scale software development immensely. TFS is highly customizable, but if you go the route of heavy customization, don't upgrade to the latest version aggressively. Plan to invest in at least one full time TFS administrator. Make sure the users are properly trained.
Score 10 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps Server is being used across the organization as a defect/bug tracking system for IT projects similar to Jira. The business problems it addresses are mainly related to issue tracking and traceability. There is a multitude of IT deployments at our company, and hence, lots of QA/UAT testing. When defects are captured during these phases, they are logged in Azure DevOps Server and tracked.
  • Organization
  • Defect tracking
  • Severity
  • Escalation
  • Issue/user traceability
  • Easier interface.
  • Less drop downs and tabs.
  • Email notifications.
The best use for Azure DevOps Server is for issue tracking and reconciliation for defects during the QA process.
The support for Azure usually responds in a timely manner and the technicians seem well-versed.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Our IT department uses Azure DevOps Server to manage all our projects and for software development.
  • Ease to manage code.
  • Compatible with several services.
  • Version control.
  • Need more templates.
  • Can be confusing to use at first.
  • Reporting could be better.
It is well suited for any IT team, provides a great way to manage and track projects. Great for code reviews and bug management.
The support so far has been really good, no complaints.
Score 10 out of 10
Vetted Review
Verified User
Review Source
I am currently using Azure DevOps Server with a client on a scrum project to build a business application. In the company, Azure DevOps Server is mostly used by our specific project but does have other users and different projects. It helps manage the scrum process and provides organization and clarity to a project with many moving parts and members.
  • Organization of tasks per team member
  • Statistics provider for data related to capacity and output
  • Good UX/UI experience for clarity
  • Copy/Paste functionality could be improved
  • Ability to see all team members more clear visually
  • Sort feature on columns could be better
Azure DevOps Server is a great tool for keeping large projects organized. It is well suited for building large, business applications that require a lot of organization and history of the project that is accessible.
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus.
Score 7 out of 10
Vetted Review
Verified User
Review Source
Source control for application code, for the most part. For database code, it integrates well with Red Gate software. Besides scripting out database schema, Red Gate will even script out static data so it can be source controlled as well within TFS/ADS. My previous employer used TFS/ADS to automate builds and as a ticketing system.
  • It allows you to view the history of any piece of code. Shows the differences. If you are a good 'code archaeologist' you can figure out why things were changed and when.
  • It provides a repository of your code so you can reconstruct it in case of a catastrophe. With code history, you can restore the code as it was before some change that didn't work, was made.
  • The tickets it creates can be linked to the changes in the code. This adds an important element showing causation. This code change resolves or is associated with this ticket which includes the purpose of the change.
  • The way it uses workspaces is non-intuitive. I required help from our resident expert to get TFS set up initially.
  • Don't forget to refresh again and again. Yes, of course, you want the latest changes - you shouldn't have to remember to keep hitting that button.
  • Even though it uses a Microsoft SQL Server database to store its data, it uses the database in a non-standard way. Don't try to do the usual MS SQL backups - let TFS handle the backups.
Git is very popular right now and can be used instead of TFS for source control, but TFS can integrate with Git. Git has more of a learning curve than TFS, IMO.
There is quite a bit of info about it on the web.
F A | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
It was used as an Application Lifecycle Management (ALM) system that takes care of all aspects of software development from planning, requirements gathering to coding, testing, deployment, and maintenance. Also as a Source Code Control(SCC), Bug Tracking, Project Management, and Team Collaboration platform.
SDLC Management (SDLC – Software Development Life Cycle):
  • Software Team Collaboration
  • Source Code Management
  • Supports Agile, Scrum, CMMI
  • Bug Tracking
  • Integrated Test Tools
  • Automated Builds
  • SDLC Management (SDLC – Software Development Life Cycle).
  • Software Team Collaboration.
  • Supports Agile, Scrum, CMMI.
  • Bug Tracking.
  • Reporting
  • Code integration
  • Project Management integrations
Team Foundation Server (TFS), provided by Microsoft, provides you a wide array of collaborative software development tools that integrate with your IDE providing secure version control, extensible integrations, agile tooling among many others. You can set up an on-premise version of TFS or you can sign up for Visual Studio Team Services which is backed by Microsoft Azure if you don’t want the hassle of managing the infrastructure.
The best support that i have everr used
Score 10 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps is being used by the entire company. We use that to build our build and release pipeline to continually release our deployment.
For our department, we build infrastructure with Terraform and deploy it to the Google Cloud Platform. It solves our problem of not having a CI/CD pipeline. It makes our development cycle much faster.
  • It is compatible with so many services. You can deploy to GCP, AWS, and with any kind of developing language.
  • It has a clear developing logic. You build first and then deploy things to the destination you want.
  • When you develop with Microsoft products, you can do a lot more.
  • There is a little window tells you small jokes and information. It just annoys me.
  • The UI might use more careful design. it can be confusing when you want to find the thing you want.
  • There are small things can be added to improve productivity, such as cloning the whole agent job.
For companies, especially big companies, when they adopt the way of CI/CD, they need a build pipeline to realize all these. Either they develop websites with languages like Python, Ruby, or C#, or they set up infrastructure with Terraform, Ansible, or Puppet. Azure DevOps integrates everything together and provides a solution that works with all the technologies you use.
I give it this rating mainly because there are a lot of documents you can read and find the solution for your problem. Whether you are developing pipelines or designing the workflow, you will always find someone who has done it and can give you the right insights. I have not used their customer support yet.
Brendan McKenna | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use the Azure Dev Ops server throughout the IT department of our organization. It is utilized by Business Analysts, Scrum Masters, Developers, and QA. We have Git integration enabled and it has been an awesome experience with its integration to our source code. I especially love the built-in ability in the latest version to perform source code wide string searches. This makes it exceptionally easy to find code references and delve into new areas quickly. Aside from source control, it is our UI interface for all of our SCRUM project management needs. We create all of our tasks on the work items board and it makes it easy to see the progress of the overall team. Overall it's just been a great experience and I can't think of any complaints.
  • Git integration has been fantastic.
  • Provides a convenient UI for managing the SCRUM process.
  • Built-in Code Review feature and completion policies.
  • I wish I could default to a specific dashboard on load.
Great for source control, project management, and code reviews. It is really critical to put in place code review policies with required reviewers before a pull request can ever be merged into a target branch. As a senior developer sometimes I feel this can be cumbersome but there have been a few instances where I have caught a major error in a pull request and was able to prevent the code from being merged.
There is a large community of users and a lot of questions/answers on StackOverflow.
Score 8 out of 10
Vetted Review
Verified User
Review Source
We have been using Azure as one of our cloud providers for a few months. Not all departments in my company are using it but a few of the critical applications that need multi-cloud for managing resilience are using it. How these departments use it is for an end to end infrastructure on the cloud and set up and launch an app in Azure.
  • Not only does it provide a way to manage your code, but you can also do most of the other activities such as planning for a release, planning test cycles and, in a sense, true product management
  • The reporting is great out of the gate. They will enable you to draw insights into how the teams are managing and pushing the changes to production.
  • It integrates pipeline and DevOps, making it true life cycle management.
  • Most of the companies use AWS, GitHub, etc. and generally the support on the internet is relatively less.
  • Being a Microsoft service, it works very well with Microsoft apps.
If you are using Azure as a cloud provider and want to build solid code management and overall software life cycle management, then azure DevOpsSserver is a great fit and should generally work. Also, the reporting features out of the box are really helpful and the higher management can get great visibility on how the code and product are being managed.
This is a less popular option in the market and the overall support you get on the internet is less.
October 03, 2019

Fostering Innovation

Score 10 out of 10
Vetted Review
Verified User
Review Source
The Azure DevOps server is used within our IT department. We use it to have simplified server management and improved connectivity with remote sites. It also allows us to save money, as we may have options to pay per use or month-to-month. It is also hosted on-prem, which is beneficial.
  • The Azure DevOps server integrates well with the IDE we currently use -- Visual Studio
  • Azure DevOps server is hosted on-premises.
  • The Azure DevOps server fosters innovation in our company.
  • Since we are new to using Azure DevOps since this year, we are trying to find areas that could be improved.
  • Azure DevOps server would be beneficial if it could be used with all technologies/programming languages.
  • Having a way to use Azure DevOps server with Oracle or Stored Procedure packages would be beneficial.
Our dev team is able to use Azure DevOps to do cross development or paired programming. The ease of deployment is wonderful. The integration with the current IDE and ways to track or monitor changes is also great. I would love to see it expand outside of only IT within our company.
The Azure DevOps server is helping our team to transform and stay relevant. It is helping us to deliver on time while saving the company money. It is efficient and meets our needs for being innovative. It is one of our best decisions made. It is truly an upgraded version of what the previous TFS once was.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps server is being utilized as a centralized tool for our organization's code & release management. All departments in the organization have their own repositories where they check-in their codes. Azure DevOps server along with GIT integration is serving as a central code repository for our organization. Also its widget integration and inbuilt templates to automate code build and release from almost any tech stack is worthy to have it as a DevOps tool.
  • Vast range of Template for Automated Build and Release Pipeline with option to have conditional triggers
  • Code repository mechanism is aligned with GIT which is a well known public repository system
  • Bug Management is also an integral feature of this tool
  • Dashboard creation option of Build and Release pipeline is also available
  • Can add more build templates for specific technology requirements
  • Can have more features in dashboards which can help dev teams stream line their tasks and priorities
  • Can have raise alarm feature in case of any sort of failure in devops pipeline execution
Azure DevOps is well suited if you have a big team that is collaborating their codes and need to have devops pipeline for all build and release work. Also since this tool provides bug management facility, you don't need to purchase any other tool for that purpose. Moreover if you have your infrastructure built over Azure cloud then this is a best match for your requirements as it integrates well with it.
Vaibhav Choksi | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Dell Technologies uses Team Foundation Server for managing multiple projects across the North America region and rolling out in all other regions. If you use Visual Studio for development, TFS, or its online equivalent VSTS, you can have a fairly seamless end-to-end integration. Out of the box, it provides code management, testing, work hierarchy in agile formats, automated build, and deployment.

Dell manages source code, project reporting, engineering progress tracking and release management for agile software development. Microsoft TFS is also leveraged by the Product Management group to define and manage product requirements and managing the technical backlog. TFS really makes it easier to perform an end-to-end integration, reporting, tracking, code management, automated build, and deployment, etc.
  • TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
  • It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
  • It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
  • TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
  • Development in branches is hard to achieve and TFS has a room for improvement.
  • Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
Team Foundation Server is well suited in product management
  • Easier to build a technical backlog.
  • Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
  • Make a Product Manger's and engineering teams' life easier in meeting and tracking.
  • Project managers can easily track the work and create reporting.
Vinicius Lima | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source
We use Team Foundation Server in the Information Systems Department in our company. All developers have access to Team Foundation Server to do code versioning. We use it integrated with Visual Studio to check-in and check-out our projects' code. We also use the web interface to navigate between code versions and to manually download code when necessary.
  • Integration with Microsoft products, like SharePoint, IIS, Visual Studio
  • Users are able to access via desktop client, web browser and through Visual Studio
  • Code version control
  • Bad UX and UI in the web interface
  • Merging code is a very hard task
  • Development in branches is also hard to achieve
  • Not so easy to upgrade server version
TFS is well suited to developers and teams that work with Microsoft technologies and products. For other scenarios, alternatives like Git can deliver more powerful and reliable features. Also, developing software in branches is very difficult, as well as merging code. These tasks needs to be carefully planned to avoid broken code and headaches in your company.
Score 9 out of 10
Vetted Review
Verified User
Review Source
We are currently managing a large project and we use TFS to manage bugs, code and releases. It is only being used by the technical team but others are coordinating with us to make sure their bugs make it into the system. As well, we are using data from the system to routinely give updates to management on the status of the project as well as any concerns or risks.
  • The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
  • Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
  • Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.
  • Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
  • Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
  • Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.
TFS is very good when working on a large project with a lot of moving pieces. When you have many BAs involved and a lot of user stories, it can be extremely useful to consolidate information. If you are not working on a large project with many users and developers, it may be excessive. However, in general, the tool is extremely helpful when implemented correctly.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Team Foundation Server to manage manage almost all the projects and application packages. Team Foundation Server makes it easy for us to have good control of all the progress and it really helps in managing the whole release process even if a lot of developers and many teams are involved.
  • The environment is easy to use.
  • It is very easy to track progress of various work items.
  • Project management is made really easy.
  • There is no ability to work offline.
  • There is a learning curve involved which is little hard to get when you are using the tool for the first time
  • The UI can be little more organized.
Team Foundation Server is specifically very useful for bigger teams which have a lot of developers and organizations with a lot of parallel team working on similar projects. It helps to keep track and manage the overall project well. I don't think of an alternative which is as powerful as TFS
Lavanya Elluri | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Team Foundation Server is used for version control of Microsoft .net applications, SSIS, SSRS. Also, TFS is used for tracking tasks, bugs and change requests.
  • Version Control
  • Track Bugs, Change Requests, Tasks
  • Compare versions of SSIS can be improved
  • Merging of the SSIS Code can also be improved
Team Foundation Server is a very a very good tool when you are using with Visual Studio. It's very easy to check in/check out the code to the Team Foundation Server. One can easily check the Task, Bugs and any change request items very easily from the Visual Studio. One can also check this items directly on the web browser as well.
Markus Hopfenspirger | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Team Foundation Server as Source Control Managment System and for automated Builds and Tests. We don't use the WorkItem System of Team Foundation Server. We Used it a couple of years ago, but it was to complicated. Right now we just use Trello with a Scrum AddOn for Task and Backlog Planning. Right now only our Developers are using Team Foundation Server.
  • I like the Team Foundation Source Control Management much more compared to other Systems like GIT, because:
  • - Perfect Integration into Visual Studio
  • - Easy and direct checkout/check-in
  • - Perfect branching and merging
  • - Workflow Support with autmated Reminders
  • The Build System is just great. Since Version 2017 its very easy to integrate self made tools into the build process.
  • Easy Managament of Users and User Rights.
  • Team Foundation Server could be improved in the Task and Backlog Managment for smaller Teams. E.G.: It's hard to quickly write down Tasks during a meeting because you have to fill in lots of Fields per WorkItem. It is hard to push the Items around.
Well, as said before. I like TFS for Source Control and automated Builds and Testing, but it could be improved in the area of Task Management.
Score 8 out of 10
Vetted Review
Verified User
Review Source
TFS is used across the organization as an Application Lifecycle Management tool. This addresses the problem of needing a central way to demonstrate the status of projects/applications.
  • Security
  • Reliability
  • Scalability
  • TFS templates are not as flexible as the business requires
Well suited for any IT team. Great way to track and manage the software lifecycle for projects, whether for one team or many teams.
Luca Campanelli | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
In my organization Team Foundation Server is used to better manage all projects and application packages. Having several developers in place and having to work on multiple projects Team Foundation Server allows you to have complete control of all developments and to manage independently and with order every release and every package developed without loss of data or misalignments.
  • No data loss
  • Multiple deployments
  • Deployment without problems of versions
  • You must avoid getting stuck with check-in
  • Developers must avoid overwriting
  • The developers must be at minimum coordinated among themselves during the developments
if you are a development company or you work in a company with continuous developments it is certainly advisable to create a server dedicated to Team Foundation Server, surely you will have fewer problems in the deployment phase and you can always keep all the versioning of your software or your objects under control. Also, rollback in emergencies can be easily managed without losing too much time.
Brian Willis | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use it for our software development team. Team size is 8. It is being used as source control for .NET applications and as a continuous integration server. It is being used on site and also by our offshore partner developer team in Mexico. It helps us track versioning and collaborate with the peace of mind that we control the code.
  • Continuous integration when the team is using azure is really easy.
  • It's fairly intuitive to use.
  • Azure or IIS deployment is very easy.
  • The project management/scrum piece is hard to learn.
  • The Wikipedia functionality it provides isn't very useful for lack of features.
  • It takes a REALLY long time to check in a large number of newly added files.
  • If your file paths get too long, TFS gives you errors.
Team Foundation Server (TFS) is suited for anyone working in .NET. It's not appropriate otherwise. It's really as simple as that I think.

You could use some other source control with .NET but it integrates so well with the rest of the Microsoft family and is so reasonably priced, there'd be no need to.