What do you like best?

Integration with Microsoft Products: SharePoint, IIS, and integration with GitHub and git-flow.

Easy upgrade process from version 2015 to version 2017.

Version Control system.

Access via Desktop client and web browser.

What do you dislike?

Code review process, comments without dates and commentator name.

The TFS Addon for integration with windows explorer(Microsoft Visual Studio Team Foundation Server Power Tools) has bugs with folders. I spent a lot of time before I found a solution. After a new version installation, you need to change it to the previous version of power tools and proceed with the newest one.

I'd say TFS has bad UX and UI. It's hard to find projects and you need to write full ways to add a project.

Wiki-pages support appeared only in the version 2017. But wiki-pages has a poor functionality and UI.

It is necessary to improve the process of source code check out and check-in.

Recommendations to others considering the product

If you use a mac it's used to be a problem. Because eclipse plugin looks ugly and unstable. From time to time, the TFS plugin for eclipse is suddenly closed.

I'd recommend accurately think about this solution.

It has strong benefits but for Atlassian products users, it seems to be contradictory and too strange.

But for .NET development and Microsoft Partners, there is ni=o another way. They need to wait for improvements.

At the moment it looks like Microsoft TFS is a weak solution.

What business problems are you solving with the product? What benefits have you realized?

We use Microsoft TFS as a common entrance pion for our Software development, business analysis, and Change management processes.

Sign in to G2 Crowd to see what your connections have to say about Microsoft Team Foundation Server

What do you like best?

Technically it can be configured in a lot of detailed way depending on the team. It is more useful for the backend engineers who use it for version control and code review.

What do you dislike?

We primarily use it as a task management system and there is no easy way to attache multiple people to be assigned a task which might be cross-discipline. I prefer more visual systems like a Kanban style board. While it is very customizable, it takes a lot of effort to configure the way I would like it, and then is not flexible or easy to change afterwards.

What business problems are you solving with the product? What benefits have you realized?

We use it primarily for task management. I would prefer to use a system like Jira or Pivotal which are easier to work with in smaller teams like mine. It is more useful for the backend engineers who use it for version control and code review.

What do you like best?

TFS is one of our main tool we use to save all of our source code so that we all have access to one code version.

What do you dislike?

Sort of time consuming since you have to check out any source code. After using it, you have to check it in. Sometimes multiple users will check out the same code but at least you will get the latest version.

Recommendations to others considering the product

Sort of difficult to use at first but over time you will get the hang of it.

There are many youtube videos that you can use and learn how to use TFS.

What business problems are you solving with the product? What benefits have you realized?

The problem we are solving to store all our source coding into one location and to have one version of it.

Before TFS, we would use our own storage methods which led to multiple versions. TFS solved this issue.

What do you like best?

It has some interesting features regarding project management / teamwork. Integrationcwoth AD is also nice. If you can, I'd recommend using the Git support as TFVC can be a pain to coworkers with especially if you do any work outside of the Microsoft Stack. It has a number of ALM tools built in, such as a ticket board, Kanban board, chat rooms, etc.,which may be helpful if you follow any sort of agile practices. It also supports code reviews, which is great.

What do you dislike?

Very poor IDE integration outside of Visual Studio. Poor and confusing documentation with some broken tools as well. The biggest example I've encountered of this is with Jetbrains IDE's. The Microsoft supplied plugin for VSTS required a command line tool that ended up breaking after working fine for several months. I reached out to support, and they were helpful, unfortunately I ended up getting nowhere.

Recommendations to others considering the product

If you're not stuck in Microsoft vendor lock in, or not using a MS stack, it might be better use the Git support as opposed to TFVC

What business problems are you solving with the product? What benefits have you realized?

Version Control primarily. It allows you to version and back up your code with decent integration with other parts of the Microsoft stack. It also provides a near complete set of ALM tools.

What do you like best?

It works great and is full of functions and team collaboration tools. I further love that it is seamless within Visual Studio. I also love the fact that Microsoft lately has been integrating with Open Source platforms and technologies like Git and others.

What do you dislike?

Learning curve... (at least in administering it.) I'm sure that once you have it down, it would be fairly simple... but not everything is intuitive enough to automatically know how to use it.

Recommendations to others considering the product

If you want a tool that you know works and is feature full then TFS is for your team. It does carry a bit of a learning curve especially with administration... but for those already used to administering Microsoft Products it should feel pretty familiar.

What business problems are you solving with the product? What benefits have you realized?

What do you like best?

The way how we can have folders across versions, test plans, code is the best thing. While writing up defects, the ease to mention the fields for the developers to understand how to and where to find the defect is the best

What do you dislike?

It just keeps losing connection to the server at times. We need to connect again to the server if updates to the laptop is made.

Recommendations to others considering the product

Any novice user with a little help can try using TFS because it will lay out all the groundwork for you and help collaborating with the developers easy and beneficial.

What business problems are you solving with the product? What benefits have you realized?

The team collaboration has become better. Every team member can figure out any details regarding test cases or defects logged. I would recommend this to everyone who are new to defect tracking.

Learning about Microsoft Team Foundation Server?

* We monitor all Microsoft Team Foundation Server reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.