TFS Reviews

For customers, we work in banking, finance, and healthcare domains, where there is a huge amount of data from customers and other types of applications and databases. We access this data for automation purposes. Many times, we utilize TFS for this type of thing.

Currently, we are focusing on the security features of TFS, such as the Credential Vault. We use it to store all credentials securely and provide access to specific stakeholders.

TFS should have capabilities similar to Git, like storing all types of artifacts in the repository. It should offer features that allow DevOps teams to track the changes made to the source code or by developers and generate automated reports and dashboards. This would make it easier to monitor and get information without searching through logs manually.

I've worked with TFS for more than three to four years.

Once TFS is installed, there are no major issues. I would rate the stability at seven out of ten.

The scalability is good because TFS is backed by Microsoft, allowing easy integration with other Microsoft applications. It supports a range of capabilities which can be utilized effectively. I would rate the scalability at seven out of ten.

There are some issues with the support team as we need to wait for a long time to get a response. The SLA needs to be improved. Direct communication, such as chat, to showcase screens would help resolve issues faster. I would rate the customer support at five out of ten.

Neutral

The initial setup was somewhat challenging, taking two to three days the first time due to our inexperience. We faced issues such as getting appropriate access and connecting TFS with our current environment. Once we prepared documentation, subsequent setups were easier and quicker, taking only two to three hours.

There are many version control options available in the market. From a costing and licensing perspective, I would rate it around six out of ten. It is not the cheapest product, but it offers good value for money.

I would recommend TFS to anyone planning to use it. It offers valuable features, though they need to be improved over time.

I'd rate the solution six 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. 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.

TFS is useful for managing the code, such as code versioning, and managing where we store our soft-coding repository, which is where we can manage the versioning with the owner. The main purpose of using TFS is for managing our soft-coding, branching, and tracking of our different branches.

The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch.

I have been using TFS for approximately seven years.

The solution is stable but could improve.

I rate the stability of TFS an eight out of ten.

We have approximately 10 people using the solution in my department. We might increase our usage of the solution. However, it is depending on if we add more users and if we receive authorization. We are focusing on accessing Azure Development, such as the task catalog that we have. There are developers who have full access to create and manage them.

I have not contacted the support from TFS. We have our own internal support.

The initial setup of TFS is straightforward. However, one should understand the concept of all the types of version control.

We used one person for the deployment of the solution.

I did not evaluate other options before choosing TFS.

I recommend TFS to others.

I rate TFS a nine out of ten.

TFS is used for version control. So, other software can integrate with TFS. The tool is also used for documentation and STLC.

Since it is a robust solution, I face no performance issues. Also, considering how well the implementation process of the solution was carried out, we never faced any issues while using the solution.

As an end-user, I expect the solution's performance to be faster while staying as stable as possible.

To be frank, we never considered the need for additional features in the solution. I don't have any specific suggestions for what could be added since the tool is already very streamlined. It is a stable tool without any issues; everybody in my company is happy with the solution. We follow a streamlined process at work with a specific set of steps from point A to point Z in a thorough manner. If there was something tedious, time-consuming, or repetitive in the solution, I could have spoken about what additional features I wanted to see.

I have been using TFS for a year. Also, I don't remember the version of the solution. I am just an end-user of the solution.

Since it is a very stable product, there is no chance of our company planning to replace it with some other product. The most that my company would do is they might consider shifting from TFS Version Control to Git TFS.

As I work in a bank, TFS ensures the solution is always available, making it a stable tool. I have never faced any stability issues while using the solution.

It is a scalable solution since TFS offers users a very good system, hardware, and efficient people to implement their tool. It is a very scalable software. Also, the scalability of software depends upon its hardware, and they provide very robust hardware.

The initial setup and implementation process of the solution was something that was done years ago in my company. Since I joined the company recently, I won't be in a position to comment on the implementation process.

We have an entire floor of people who provide technical support for deploying and maintaining the solution in our company.

I believe that my company has opted for volume licensing provided by TFS. So, it is not just one or two licenses my company has since my company trusts products from Microsoft. Though I am unsure, I think that if you purchase one of Microsoft's products, they offer you some of their other products for free. As per my knowledge, Microsoft products are cheaper than other products in the market. On a scale where ten is the highest and one is the cheapest, I rate the solution's licensing cost at one on a scale of one to ten.

Since in our company, we are already trained to use the solution, and so we never face any issues or problems while using the solution. The pre-existing features in the solution are more than enough to meet our needs.

The solution has a user-friendly interface. The solution already allows for more integrations with other solutions. Also, there is a separate team that works on the solution. The solution protects the systems in my organization. When it comes to the products offered to customers by TFS, they are constantly evolving since it has been in the market for twenty years. Also, we keep getting updates for the solution every second or third day.

I have a laptop, and if I start the solution on that laptop after two weeks or three weeks, I won't be able to connect. I need to take it to my technical support team. They will install some updates, and then I will be able to use my laptop. So, from this, one can figure out how much the solution has invested in their system. So, it is very rare that the solution faces any issues, and if any issues crop up in the solution, they have a very robust system of dealing with such problems. They have a good IT team that quickly resolves any issues. So, people are working to improve the system day by day. Every day, there is an evolution in their products. Some teams are working on production issues because of the new features implemented in the tool. Also, they are monitoring it continuously.

I rate the overall solution a ten 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.

We do a user story for a use case, which is like a snapshot of one pass through a use case. We tend to align them with the branches in Git. We have story branches created in Git and edited in TFS, which correspond to user stories based on a use case.

The solution's iteration board is good because you can track all your work with it. In TFS, you can do pull requests, trigger builds automatically, and gate them so that they're reviewed thoroughly before you release them. It is a good practice that makes things a lot easier.

If you've got 100 iterations and you create a new story and try to select which iterations, it doesn't default to the current iteration. You have to scroll right down to iteration 100 in the drop-down list. It would be good if it defaulted to the current iteration rather than having to go down a long drop-down list to select it when it's right at the end.

IBM ClearCase has something called a Version Tree, where you can see all the commits and updates to the configuration as a series of nodes in a tree diagram. You can also do mergers from the different branches using that. I'd like to see some kind of visualization tool for TFS that would make life much easier.

I have been using TFS for six to seven years.

I rate TFS ten out of ten for stability.

Hundreds of users in our organization use TFS.

I rate TFS a nine or ten out of ten for scalability.

The solution's initial setup is not too difficult. The people who set it up were experts who could quickly get it up and running. So, it looked like the setup was straightforward for them.

TFS is deployed on the cloud in our organization.

Overall, I rate TFS an eight out of ten.

We use TFS for forecast management.

The tool is sufficient for our business.

We encounter issues with backups.

I have been using the solution for three to four years.

TFS' stability is fine.

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

The solution's technical support is very good.

TFS is easy to install. We had a team of two to three persons to handle the deployment.

TFS is a scalable and useful solution. I rate it a seven out of ten.

We use it for code archiving, complete CI/CD functionality, code propagation, code repository, etc.

Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part.

The price could be cheaper.

We're going for a cloud solution that will give us similar functionality and integration with our other products that we are customizing, like SFD. At present, those codes aren't many. 

I've been using it for more than eight years.

It is stable.

It's scalable. We have around 45 users.

We deployed it using an in-house team. You will need two to three people who are in the DevOps teams, who do all the testing, and programmers, who use it and check the code.

You will need to obtain server and account licenses.

TFS is a good product, and I would rate it at eight on a scale from one to ten.