TFS Reviews

The primary use for TFS is for event planning, including things like writing the user story and then assigning tasks to the developers. Another task is writing test cases, then recording test results, and sending bugs to the team members. The third thing is that we use TFS as part of our CICD pipeline.

As part of our pipeline, we use it for checking in code and it acts as a repository. This leads to the fourth thing we use it for, which is to move the code from dev to QA to production. Essentially, we establish a complete lifecycle using TFS.

We also use it in conjunction with Azure DevOps.

This product brings a lot of discipline and consistency in the way that our developers use their tools. 

The most valuable feature from my point of view is project management, which includes user stories as well as task management. I would say that these features are critical.

I would like to see better integration between TFS and third-party tools such as Jira. For example, integration with SharePoint is not very straightforward and we need to do a lot of manual work.

The user interface could be improved to make it simpler and increase usability. Making it more user-friendly would be a good thing. While it is okay in some regards, it does not compare to tools like Jira. There is some complexity because there are a lot of features, but usability can still be much better and it would be more comfortable to use.

We have been using Team Foundation Server for almost five years.

This product is stable and we have not experienced any issues with it.

The developers are completely dependent on TFS and are using it on a daily basis.

TFS is quite scalable and there are different deployment options that are available. I don't see any problems with scalability. We have between 40 and 45 people in my department who are using TFS.

The support that we received during the initial setup was the only time that we needed to contact them. Beyond that, we didn't have to ask for technical support. I wouldn't refer to our initial support as very technical because it was more about knowing how to perform certain tasks within the tool.

Prior to using TFS, we used CVS as our code repository solution. All of our requirements and bug tracking were done using manual effort. We were using Word documents and things like that. However, all of that has now been put into TFS.

What led us to switch was the ability to track all of the developers' activities. Before this, getting visibility and deliverables was a real pain point. For example, we didn't know how many stories the developers had completed, how much effort has been spent, or where we were with respect to the tasks that were completed by the teams.

I would say that the initial setup is of medium difficulty. You definitely need help from an expert, as it is not like I can just pick it up and start running it. TFS requires a little bit of expert support in setting up, and we received solid support from Microsoft.

Our deployment took place over the course of a week. It was not a week's worth of effort but we had to schedule calls for support. I would say that TFS can be set up and tested in a single day, although it may take up to a week to finalize things.

During our implementation, we requested help directly from Microsoft.

Our in-house DevOps team is responsible for maintenance.

I wouldn't say that this tool is cheap or expensive but in the middle. TFS is definitely not as expensive as some other tools like Rational Team Concert. Basically, I would say that it is affordable.

Professional Services is a separate cost from the standard licensing fees.

My advice to anybody who is considering TFS is that the suitability depends on what technology you are trying to use. For example, if you're using Microsoft technology then it is better to use TFS. If on the other hand, you are developing something outside of Microsoft, perhaps using an open-source tool, then I wouldn't be able to recommend TFS. Instead, I would choose one of the other many third-party tools that are available.

I would rate this solution a nine out of ten.

I use TFS as a code repository for version control.

The most valuable features of the code check-in and check-out capabilities.

The code branch capability and build features are helpful.

The interface is easy to navigate.

I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects. As it is now, I can see the details of a single project by selecting it. However, I cannot see all of the scheduled projects at once.

I have been using TFS for between seven and eight years.

TFC is a stable solution.

This is not a scalable product. We have about 35 users in our company.

We have not been in contact with technical support.

Prior to TFS, I did not work with another similar product.

The initial setup is easy and can be completed within a day.

The pricing is reasonable at this time. 

We are currently in the process of upgrading to the 2019 version, which has many more features than does the 2017 version.

My advice to anybody who is considering TFS is that once you get used to it, the interface is very easy to navigate.

I would rate this solution an eight out of ten.

We are using TFS for STLC

It improved SDLC & STLC 

The most valuable features of TFS are bug reporting and its high performance.

The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one.

In a future release of TFS, they should be more integration and DevOps features added.

I have been using TFS for approximately 20 years.

I rate the stability of TFS a six out of ten.

The scalability of TFS is good.

We have approximately 50 people from our IT teams that are using the solution in my company.

I rate the scalability of TFS a six out of ten.

I have not used the support from TFS.

I previously used Jira. I did not switch solutions, the new company I work for selected TFS.

The initial setup of TFS took a couple of days to implement. The full process was simple.

There are different prices depending on the configurations. There is a free version available. There is no extra cost for the solution. However, the hardware could be something that needs to be considered.

The maintenance of the solution can be done by one or two people.

I would recommend this solution to others.

I rate TFS an eight out of ten.

My primary use case for TFS is to track source code changes, including branching, merging, and comparing changes. I also use it to check in and out code, track changes, and maintain a history of modifications. 

The solution has been valuable in managing source control and tracking code changes, improving code management and development efficiency. However, it has not significantly impacted project delivery timelines or cost efficiency.

The product's most valuable feature is the ability to view and track the history of changes. It allows me to see previous modifications and helps develop similar features by referencing past work.

The product access management features and connectivity need improvement. Rights management is also complex and could be simplified. 

Additional automation features would be beneficial. 

I have been using TFS since the early 2000s.

The solution is generally stable, though connectivity issues have occurred, often related to VPN usage.

I have used a similar solution sparingly.

The initial setup was straightforward: creating a new project, importing code, and setting up branches.

The setup was done in-house.

TFS is effective for code management and tracking but could benefit from improved automation and simplified user management.

Overall, I rate it a seven out of ten. 

My company uses the product for some of our developers who develop software on a server, after which they need to import it before collaborating with their teams. In general, the development team in our company uses the product.

The manageability and performance of the product are areas of concern where improvements are required.

I have experience with TFS, which is now called Azure DevOps Server. I have experience with the product for four or five years. My company is a customer of Microsoft.

Microsoft's support team is big, and we get help from the technical team while being able to use Office 365 and Azure Cloud, considering the licenses my company has purchased. Microsoft's technical team is supportive. Microsoft's technical team is supportive. With the licenses that my company has purchased from Microsoft, our organization gets the technical support to fix our problems directly from Microsoft.

The product's initial setup phase was difficult. It was difficult to control the software version we were using in our company. The tool doesn't offer a program or software to manage it.

I rate the overall tool a six out of ten.

We use the solution for creating a by-log and setting up the IPV. Also, we use it for the two-part deployment process. It helps us with application life cycle management and task management.

The solution's most valuable feature is its ability to build and deploy the package simultaneously.

The solution's server, in terms of deployment, needs improvement.

I have been using the solution for one year.

It is a stable solution. I rate its stability ten out of ten.

It is a scalable solution. I rate its scalability eight out of ten.

I have used a solution called In-House Coding, developed by our organization. 

The solution's initial setup was straightforward. I rate the process an eight out of ten.

The solution's cost is relatively high. I rate its pricing six out of ten.

Before choosing TFS, they need to check the development program used earlier by their company. If they have used something linear to Microsoft, then TFS is an apt tool for them.

I rate it eight out of ten.

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.

We are using TFS for source control.

The most valuable feature of TFS is its compatibility with Microsoft Windows systems. We have predominantly Microsoft solutions and TFS work well.

The user interface could improve and test management was not useful in TFS.

I have been using TFS for approximately three years.

The support from the vendor was good.

We switched from TFS and now we use Jira.

The initial setup of TFS was complex.

We did the implementation of the solution in-house using our own knowledge and we did some training courses in TFS.

We evaluated GitLab and Github for source control and Jira for ticketing handling. The newer versions of TFS are better but at the time we found Jira to be more user-friendly and TFS was more technical which is why we switched to Jira.

The effectiveness of TFS depends on the specific use case. It's a suitable solution if the user primarily operates with Microsoft tools, such as Azure DevOps and others.

I rate TFS seven out of ten.

I use TFS for source control. We are investigating the cloud option.

TFS is used to check source code and revision control. It ensures we do not have to do source control on our own. I am a programmer and the product does exactly what I need from it.

I have been using Team Foundation Server for six years. I use the 2010 version, however, our IT department is using the 2019 version.

This is a stable solution.

I have never run into any limitations. We have three individuals in my department using the solution and another six using it in the IT department.

The initial setup is straightforward.

I understand Microsoft is phasing out TFS in favor of Git, so I would steer anyone interested in TFS to look into Git.

I would rate the product an eight out of ten.

The primary use case for TFS is for sharing data.

The most valuable feature of TFS is integration.

The solution should have better dashboards.

I have been at TFS for approximately 10 years.

TFS is a stable solution, but it could be more stable.

The scalability of TFS is good.

We have approximately 200 users using this solution in my organization.

I have not needed to contact the support, my team is very good.

The initial installation is straightforward.

We use one to two people for the implementation and support of the solution.

I rate TFS a nine out of ten.