TFS Reviews

TFS can support multiple code repositories (example: Git, TFS, CVS, etc.) via plugins, which is really a nice feature.

As I mentioned, it supports multiple code repositories. You can also build CI/CDs out of it. You can instruct TFS to build your .jar, .war, and .ear files and deploy them to to certain environments based on your configuration. So you don’t have explicitly maintain another code repository and CI/CD tools for your continuous integration/build purpose. This also automatically reduces DevOp burden and the number of people maintaining that DevOp work.

It needs huge improvement on its Agile functionality.

For more than a year, until I left the company.

No.

No.

We had our own support member (so I can't rate their support).

Yes, I used to use VersionOne, HP AGM, and JIRA to track and monitor Agile practice in my previous companies. At Lennox they had only one option, TFS.

I wasn’t involved in this process.

I wasn’t involved in discussions of pricing or licensing for TFS at Lennox.

As far as I‘m aware, the company decided to use TFS without evaluating other options.

There are better tools for Agile and CI/CD in the market. TFS may be good for code repository purposes; however, it's not the best for Agile practice.

TFS needs to be stable.

I have been using the solution for six months. 

I rate the tool's stability an eight out of ten. 

My company has more than 50 users. 

The tool's installation is straightforward. 

I have seen ROI with the tool's use. 

TFS is expensive, and the licensing costs are yearly. I rate the tool's pricing an eight out of ten. 

I rate the solution an eight out of ten. 

We are developers using the TFS for controlling, and for continuously developing our code.

I am not familiar with all of the features, as I only use it a bit for some of my projects. 

I am using the new kit because it is open source and has many good features.

What I like the most is that you can set permissions on just one folder.

For me, it was easy to use.

There are many things that I cannot do, and I have a lot of bugs. For example, if I want to merge two branches together, sometimes TFS will merge them automatically and I couldn't find the changes and had to check them myself.

That wasn't very good for me and I couldn't understand all of them and wasn't able to interact with them.

The merging could be simplified and improved.

I would like to see more features included for branching so that it copies your source code to the other branch, and have it in a separate folder.

We have been using this solution for five years.

We have not had any issues with stability. It's a stable product.

It's a scalable solution. We have 100 users in our organization.

I found the initial setup straightforward and easy.

We have a team of four or five to maintain this solution.

We are using the open-source version.

I would recommend this solution to others. It's definitely a good product. If you are looking to set up custom privileges then it's a good option for you. It has several features. If you want to secure your code, TFS is a good choice, as it can do it easily.

I would rate TFS a five out of ten.

Valuable features include total traceability, test management, source control, and extensibility.

The solution gives us support for Agile processes, including usage of board and burndown charts. It provides us with an estimation process to move to formal and test coverage for more visibility and accountability.

• Test automation: There is only integration with the MS framework which requires us to use only a certain configured infrastructure. Even MS is changing this approach as integration should be done on your own (publishing test execution results into TFS).
• Process customization: This is evolving but it is still far behind the competitors such as JIRA WI management, HPE ALM with events model and ability to manage all aspects of integration including VersionOne integration with multiple APIs.
• Scaling for large organizations: There is no predefined approach for handling different types of projects. You need to build out your own way using community suggestions and your implementation resources. There are limited scaling strategies for large organizations with more than 300 users.

We have been using the solution for more than five years.

There were some minor stability issues under a large load or during migration between versions.

For large organizations with more than 200+ concurrent users, there can be some scalability issues.

The technical support has been getting better since 2015, when MS started making more frequent releases, including a user voice application.

Previously, we were using HPE ALM, QA Manager, Atlassian Stack, and small, customized ALM products. The change was made at the corporate level.

It depends on the project/organization size. For a small organization/team, it is very easy. For a large one, the process definition takes more time and then the setup can happen.

If you have an MSDN license for using TFS, it is a good tool to start from. Later on, you may prefer to select another suite. However, you need to be sure about change. TFS, as from 2015, is evolving very quickly including the CI server, GIT server, and code review process with pull requests support inside.

We evaluated HPE ALM, JIRA, and VersionOne.

Look for the cloud version. It will give you an understanding of further development of the product.

The solution was used for software development.

It is very user-friendly.

Since the TFS was an on-prem solution, the private network accessibility was restricted. 

I have been using TFS for a year. 

It is a stable solution. I rate the stability an eight out of ten. 

It is a scalable solution. Presently, twenty to thirty users are using the solution. 

The technical support team is good and supportive. 

Positive

The IT team deployed the solution. 

There is a yearly licensing fee that needs to be paid. 

I rate the overall solution a nine out of ten.

We use TFS for bug detection and incident management. 

TFS' most valuable feature is the triage process. It is a robust solution that is easy to use. 

The tool needs improvement in stability. 

I have been using the solution for three years. 

I rate the tool's stability a seven out of ten. 

TFS' scalability is quite good. My company has 25 users. 

TFS' deployment is simple. You need about five to seven resources to handle the deployment and maintenance. 

We have seen ROI with the tool's use. 

The tool's licensing costs are yearly. 

I rate TFS an eight out of ten. 

While I don't recall the exact version we are using, I do know that we upgraded to the latest one.

We use the solution for project planning, code repository and for releases, everything really. 

Primarily, we have used it as a code repository, something we have been doing for many years. We have not made much use of the other features. 

The project management side should be addressed and the project and release planning should be somewhat extended. The solution cannot be used as a project management tool on its own. 

Although clear, the installation is of medium difficulty. It could be better and easier. 

I have been using TFS for more than five years.

The solution is very much stable. 

We have encountered no issues with the solution's scalability. 

I am not aware of ever having contacted technical support. 

TFS is the first solution of which we made use. 

While clear, the installation is of medium difficulty. It could be better and easier.

I do not know how long it took. 

Not too many people are needed for the deployment, perhaps four or five. They consist primarily of engineers and there is one manager. 

I am not in a position to comment on the licensing terms, as we are talking about an enterprise arrangement. I am not part of that.

Subsequent to TFS, we evaluated and tried making use of Jira and Azure DevOps. 

There are around 250 people making use of the solution in our organization.

At this point, I would not recommend the solution to others. 

I rate the solution as at least an eight out of ten.

The use case is as our repository for UPS Enterprise and the performance is pretty good.

It is a big improvement because before we were using PBCS.

Build definitions and releases within the product. They allow us to put our latest applications in the field.

Right now they are up to standard. All the features that we needed are included currently in TFS, including Git repository which allows our developers to perform their code-testing without impacting by uploading the latest code in TFS. It fits all of our needs.

100 percent stable.

It's completely scalable.

I give technical support a rating of A-plus.

The previous solution was PBCS which was obsolete for our team and that is why the company decided to invest in TFS.

When selecting a vendor what's most important, speaking from a money point of view, is that it be cost effective. It should have good support like Microsoft doing provides with TFS, and be easy to use as well.

Initial setup was straightforward.

The other vendor was HPE but we decided to go with Microsoft.

It has great functionality: work items, backlogs, source code, build releases, and it's easy to use.

TFS is very easy to integrate into your system. It's very easy to follow for any new developers. Also, I would say some 80 percent of developers out there use Visual Studio which is integrated with TFS.