TFS Reviews

At my previous company, I was using TFS for managing projects and code.

The most valuable feature is the backlog.

The reporting has improved over time, with the addition of Power BI reports.

There are a lot of places that Microsoft can improve this product, as well as their support.

The program and portfolio planning facility can be improved. As it is now, you can't do portfolio program planning functionality across multiple project Areas (vs. Team areas within a project area) because you cannot link items across projects. Reporting can be done using Power BI, but real time connections are difficult.  You can use connectors and external integrations but you cannot do it with the tool. It needs to be better. 

It is difficult to customize.

I had been using Team Foundation Server for between four and five years.

This is absolutely a stable platform. It is highly available and follows on the environment.

It is possible to scale, albeit tricky. There are between 2,000 and 3,000 users.

Technical support is a challenge. It is a pain to get anything from Microsoft done. For example, working on patches and queries is slow. There was a lot of functionality that we wanted to embed that we had trouble with.

They changed the entire application lifecycle management suite, so it was a challenge to understand and navigate through how things would be done.

It is not a buggy product, but for new functionality, it is really a challenge. Especially in cloud-based deployments, it is even more challenging.

I was using TFS at my previous company and my current organization uses JIRA. I would say that TFS is the more scalable of the two. With JIRA, you really need connectors and things like that. You have to have external addons to make it more scalable.

In terms of usability, JIRA might provide a better user experience but from an organizational and stability point of view, TFS wins hands-down.

Price-wise, TFS is better than JIRA.

Out of the box, the initial setup is easy. However, it is difficult to customize, especially if it is on a cloud. 

TFS is more competitively priced than some other solutions.

My advice to anybody who is implementing this solution is to use as much as possible, out of the box. Customizing it is difficult. It may not necessarily fit everything perfectly and it can be tricky to scale, but not impossible. There are definitely challenges scaling it. That said, the tool from Microsoft does allow you to do things very differently but try to do it in a standard way first.

I would rate this solution an eight 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 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.