TFS Reviews

Work item management integration with source control. I value it as the most valuable feature since it provides seamless integration with your TFS source control which makes it easy to drill down the requirements from the source control, and vice versa.

It has improved a lot over the years with newer versions, Build is one such area which has been significantly simplified, making it very easy for the users to use than the previous XAML and pre TFS 2010 build infrastructure.

Also, the introduction of Release Management has made TFS a complete ALM tool.

I think the integration with SharePoint. Microsoft should discontinue the use of SharePoint as I don’t really see any value add to TFS, document management features can be included in TFS web portal itself, if required!

11+ years, using TFS right from the first version (TFS 2005).

I have rarely faced any stability issues, except for some minor notification/alerts issues, etc., which can be easily ignored, as Microsoft is quick to provide fixes for them as well as there are quarterly updates for TFS.

The technical support has always been up to the mark in my case. Also, there are multiple posts online which help you in difficult times.

Yes, I previously used VSS, but since it was just a source control solution, I moved to TFS, which offered much more features in one package.

The previous version of TFS (TFS 2005) were a bit messy during setup due to the different installers required for different components, but with newer versions the installation and setup has been simplified to a great extent.

Yes, the pricing and licensing for TFS is on the higher side, but if you intend to use the tool as a complete ALM tool, it will reduce your costs in the long run.

As of now, there are no products in market which you can compare with TFS which provides you complete integration with different components required in ALM hemisphere, I have tried various Open Source tools, but none of them can match the functionality TFS provides. They are GIT, JIRA, Octopus Deploy, etc.

If you need a complete ALM tool for Microsoft applications and have the budget, please go ahead with TFS.

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.

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 are using the core repository for the complete development life cycle. 

The solution helps with pretty much all aspects of the development cycle. This includes using it for QA, testing, development, and the release. It's useful for every aspect of the development cycle.

The initial setup is fairly easy.

The continuous integration and continuous delivery should begin with DSS. It doesn't right now. That needs to be changed.

The phased release process could be better. Instead of shelving the call and unshelving the call, it should be done in phases. In an updated version, this should be something they adjust. It needs a more effective release process. 

There should be management of the project built-in.

I've been using the solution for more than five years.

The stability of the solution is good. There aren't bugs or glitches. It doesn't crash or freeze on us. It works. It's good. We haven't had any issues when it comes to stability.

The scalability of the solution is very good. If a company needs to expand outwards and grow they should be able to fairly easily. We've had not trouble with that aspect of the solution.

We don't have technical support for this solution, therefore I can't speak to how knowledgeable or responsive they are.

We are still using TFS, however, we're considering switching to Microsoft Azure DevOps.

The initial setup is not complex. It is very much straightforward. It shouldn't give an organization too many problems.

I didn't deploy this solution, so I can't speak to how long it actually took to do so.

We had the help of consultants from Microsoft. The implementation was five years ago, so I can't recall too many details, however, I believe we were pleased with their work.

Overall the solution is good. It's scalable and stable and has been working well for us. Of course, the phased release could be smoother, and it's something they need to improve upon.

I'd recommend this solution, even though we do plan to move to Microsoft Azure DevOps.

I'd rate the solution eight out of ten.

We use this solution for corporate internal SW development of small business applications manly in .NET.

I am the administrator and configurator of TFS Servers and other DevOps related tools (Jenkins, Ansible, Nexus, SonarQube). I create the projects and configure the full life-cycle, with a deployment model mainly on-premises for now.

Better team collaboration and Issue tracking.

I like the build management features, the integration with Jenkins and many other tools.

The team rooms for team collaboration, and issuing the backtracking are very valuable features.

One of the areas that could be improved is to have an effective full life-cycle management.

For example, when the developing team has an issue with a bug, they can relate and tag sources and builds to that bug, but after that, it's not easy to track if those builds where in fact deployed.

In the next release, I would l like to see a modern solution with a full integration of the real life-cycle.

This solution is stable.

This solution has some scalability.

We have contacted technical support (local Microsoft) a couple of times I would rate them a four out of five or a nine out of ten. They are good and I am satisfied with the help that I have received from them.

Previously we used manily another solution (Serena Dimensions CM). But specially Java developers hated it, so we start to migrate to GIT and Jenkins for them, while .NET developers prefer to use TFS.

The initial setup was straightforward. We did have some issues, speacilly in the use of the databases but due to our customer internal policies, who were old fashioned and gave us some problems, but we can't blame the software for that.

TFS licencing can be confusing, we have to read it well and have a good user management strategy and control.

We evaluated modern versions of Microfocus and SVN, we still have Dimensions CM but will be discontinuing it.

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.

We mainly use it for source control.

In the past, I've used it throughout the whole CI/CD. I've worked with Scrum and Agile methodologies. From the user story, from the product backlog to the CI/CD and deployment. I've used it for everything — the whole nine yards.

At my previous company, there were a lot of employees using this solution; it was the only system that was being used. 

Currently, there are a lot of products for managing the product backlog. The usability of TFS is not that great.

Integration from an agile perspective could be improved. Jira is far better in this regard.

I have been using TFS for over a decade.

It's is a very stable solution but when compared with Jira, Jira has taken over. The question should be: how agile is TFS? From this perspective, TFS is lacking — the ease of usability is less.

TFS is not that scalable compared to Jira. It's scalable at the story level and at the project level but in the grand scheme of things, it's hard to manage it from an entire product perspective. 

It depends on what kind of program your company has. Personally, we didn't have to deal with Microsoft tech support very often relating to TFS. 

It depends on which point you start. From my experience, problems occur when you already have a development and then you adopt the agile method and try to work it into your source code.

Our IT team handles deployment and all maintenance-related issues.

It depends on what methodology. You can use it for the entire software development process, from the user story to the code and the integration and deployment — the whole nine yards. That's something to be taken care of and set up diligently.

On a scale from one to ten, I would give TFS a rating of seven.