TFS Reviews

• Source code management
• Branch/merge tools
• Build capabilities
• Work item tracking
• Scrum board management

We've reduced production deployment rollbacks 100%.

Build definition management - there needs to be change control for build definitions

I've used it for 10 years.

It's a long upgrade process, but works fine.

No issues encountered.

No issues encountered.

8/10

8/10

No previous solution was used.

It was straightforward. It's mostly wizard-driven, with plenty of built-in validation for most steps.

Virtually immeasurable. The low cost of the product is nothing compared to the productivity improvements it brings.

Size accordingly. Not every shop needs every feature.

Size accordingly. Not every shop needs every feature.

Recognize the fact that TFS isn't just a source code management tool. It's an application lifecycle management tool that covers all facets of software project management as well as development, deployment, and production support.

TFS is mainly used for day-to-day project management i.e. all the tasks, user stories, and test case management are done on TFS.

The most valuable feature is integration, particularly if you have a .NET application because it nicely integrates the CI/CD pipeline where you can automate your build whenever developers check the code. It also has great integration support with Visual Studio.

TFS isn't a great tool if you're on the cloud, so the cloud version could be improved.

I've been working with TFS for over ten years.

TFS is a Microsoft tool, so it's very straightforward to set up.

TFS is nicely suited for enterprises running Microsoft, but if you're using a different technology, I'd advise exploring other tools as well. I would rate TFS eight out of ten.

1. SCM functionalities
2. ALM Features
3. Build capabilities
4. Deploy options
5. Web portal
6. Release management
7. Support for multiple languages
8. Plugins for open source tools, like Sonar and Jenkins
9. Very good user-friendly UI
10. Test management - capturing/creating defects
11. Reports
12. TFS community, APIs, and support

• We have set up a centralized TFS server.
• All the delivery projects are clients for this TFS.
• They are using it for code repository, ALMs, and for DevOps implementation.

1. Customization of build templates - better tools
2. Tracking
3. More friendly on test lab setup (TFS 2013, I did not verify on TFS 2017).
4. More user-friendly on SharePoint integration (TFS 2013, I did not verify on TFS 2017).

We having been using this product for more than three years.

All for my entire development project, the major SCM tool has only been TFS.

Nope. Installation was very easy. We set up a 'multi-node' installation:

• Application tier
• Build server
• Database server
• Reports server

No, stability is fine.

We encountered some issues with the report server part when the service user password changes, otherwise until today have not faced issues on the production environment.

Nope.

Very good.

Very good.

We used VSS and most of our projects are in Microsoft stack. I opted to choose TFS for incorporating DevOps with easy integration VS IDE as there are many advantages.

Setup is straightforward. As I mentioned earlier, we did a multi-node installation.

In-house.

Yes.

No idea on this one as it was done by different team.

Yes, VSS and Git.

1. SCM functionalities

2. ALM features

3. Build capabilities

4. Deploy options

5. Web portal

6. Release management

7. Support for multiple languages

8. Plug-ins for open source tools, like Sonar and Jenkins

9. Very good, user-friendly UI

10. Test management: capturing/creating defects

11. Reports

12. TFS community, APIs, and support

We have set up a centralized TFS server.

All delivery projects are clients for this TFS.

They are using it for code-repository, ALM, and for DevOps implementation.

1. Customization of build templates - better tools.

2. Tracking

3. More friendly Test Lab setup (in TFS 2013; I didn't verify in TFS 2017).

4. More user-friendly on SharePoint integration (in TFS 2013; I didn't verify in TFS 2017).

We have been using this for more than three years during all development projects. Major SCM and TFS only.

Nope. Installation is very easy. We have set up "Multi-node" installation:

• Application tier
• Build server
• Database server
• Reports server.

No, stability is fine.

We encountered some issues with the report server when the service user password changed. Otherwise, until today, we haven't faced issues in the production environment.

Nope.

Very good.

Very good.

We used VSS and most of our projects are in Microsoft Stack. Opted to choose TFS for incorporating DevOps and easy integration of VS IDE. There are many advantages.

Setup is straightforward. As I mentioned earlier, we did a multi-node installation.

In-house.

Yes.

Not idea on this one as it was done by a different team.

Yes. VSS and Git.

Project Management: Agile and Code development can now work side-by-side in the same solution.

This speeds up development, as developers do not need to be swapping applications to update and develop at the same time.

TFS increased productivity and reduced our times to market by 60%.

The product needs to stay competitive with its peers like Github, and the adoption of other markup language renderings in the code section of TFS.

10 years.

I didn't encounter any issues with stability.

I didn't encounter issues with scalability.

If you have premier support, then the support is excellent. We get a response within four hours of placing a ticket.

I did not use a different solution prior to using TFS.

Simple, out-of-the-box.

The only area that takes time is creating builds and release pipelines.

It's free with MSDN (Microsoft Developer Network).

We have looked at Github, JIRA, and Rally.

Team Foundation Server is an enterprise ALM tool, not just for developers.

It’s come a long way in 10 years, it's worth a look.

We use the solution to store all the code and designs for software version control.

The solution helps us store multiple software versions as it evolves and develops.

All the essential functions of the solution perform well.

The solution's pricing and setup process needs improvement.

I have been using the solution for a couple of years.

The solution is stable. I rate its stability as an eight.

The solution's scalability is a six or seven.

The solution's setup process is quite complex. It keeps updating for new versions, and thus, it becomes complicated to maintain them.

The solution generates an average ROI.

The solution is expensive.

I rate the solution as a seven. I advise others to prefer Azure DevOps as it has better features than TFS.

I use TFS to assign and manage projects.

TFS's best features include user-friendly test management, bug reporting, and ID assignment.

TFS's CI/CD, project pipelines, and management development could be improved. TFS is also an older product, so it's not making the advances that other products in the market are.

I've been using TFS for seven years.

TFS is very stable.

TFS is a very scalable product.

I would rate TFS eight out of ten.

We use Microsoft Team Foundation Server as part of our development framework. Most of our development technology is from Microsoft and our primary language is C#, although we do have a number of Java programmers as well.

We primarily use TFS for managing our resources and scheduling. We can also use it to check to see whether tasks have been completed by the team, or not.

The most valuable features are the dashboard and task-selection capability.

The option to save favorites is helpful for managing pages.

I would like to see TFS integrated with a project management solution, such as Microsoft EPM. Right now, it is isolated from EPM but if we could somehow connect it, then that would help a lot. As it is now, the results are not easy to report to project managers, which makes it difficult to estimate both cost and the time to completion.

The interface can be improved and made more user-friendly.

We have been using TFS for about five years.

This solution is stable and we have not had any crashes to this point. We use it on a daily basis. All of our new projects start on TFS.

This is a scalable solution. Our company has 1,300 employees, although there are only between 50 and 100 who use TFS.

Because we are in Iran and there are sanctions, we do not have a Microsoft agent and we have never been in contact with them. We instead rely on various forums and searching for solutions using Google. Using Google is the fastest way to get results.

We did not use a similar solution prior to implementing TFS. However, we did use Microsoft Project for scheduling. It was not specifically for the purpose of software development, but we used it for putting together the steps of a project. For example, first, the UI would be developed, and then the backend. These steps were listed in the project management software.

I did not personally perform the installation, although my colleagues had no problem and I got the impression that it was easy.

Our in-house technical people installed and deployed this solution. There were two of them involved in the process where one took care of the servers, VMs, and infrastructure, whereas the second person installed the solution and gave us the link to use it.

We have lots of servers and virtual machines, with two people in charge of maintaining our infrastructure. One person is generally in charge of installing and maintaining software as was with TFS, and this person is also responsible for the maintenance.

There is a gap between project management, agile methodology, and TFS resource management. If they can fill this gap then it would be a great improvement for us and many other companies.

My advice for anybody who is implementing this solution is to keep in mind that using the tool, alone, will not change the way they develop their software. First, they should become familiar with agile methodology, and then they will be able to properly use TFS.

I would rate this solution an eight out of ten.