TFS Reviews

We use the source code repository technology of TFS, we have Git repository in TFS, and also, have TFVC.

Git was introduced starting from TFS 2013. This allowed our team the flexibility on the source control preference.

This product has allowed us to continually maintain our code repository.

The product is mature. We use it as our primary on-premise source control for both Git and TFVC allowing the flexibility for different delivery team to use different source control that best suits them.

We have just recently upgraded to this version of TFS, but have been using Microsoft Team Foundation Server for the last six years.

If your plan on using on-premise, we would recommend you would resource your hardware/VM requirements appropriately to host Team Foundation Server.

There were no scalability issues.

The product is mature, as we’ve upgraded our on-premise Team Foundation we’ve never had to engage technical support, as the upgrade process was seamless barring some minor issues here and there.

There was no issue with the setup or upgrade path as both are well documented.

There is now cloud offering of the Team Foundation Server known as Team Foundation Services for smaller companies/individuals to use, starting out with the free version for five users. I would recommend people review their requirements based on the size and resources; review them with the different offering that is now available from Microsoft.

As the variant of this product was already in use, we followed the upgrade path as we are Microsoft Gold Partners.

Now, there is the cloud offering of Team Foundation Server which is known as Visual Studio Team Services which would suit those who do not want to maintain the on-premise version and is free for up to five users.

We have a DevOps team and we primarily use TFS for bug tracking.

The current dashboard has limited report charts, We need more in reporting as charts are not enough to represent project full stat.

Addition to that, configuring reporting service require a SQL report server, which is anextra cost and need allot of effort to build

The most valuable features are test case writing and bug tracking.

The reporting functionality is something that they should work on.

The dashboards can be improved.

Migrating from version to version should be easier.

I have been working with TFS for four years.

The stability is good and I would recommend it based on that.

This is a scalable product. We have more than 50 users.

I have worked with similar solutions, albeit a long time back. Visual SourceSafe was one of them and it is now discontinued. We switched to TFS as part of an upgrade.

The initial setup is straightforward.

We have one or two people who are responsible for maintenance.

We pay subscription fees on a yearly basis and the price is reasonable.

In summary, this is a good product and I strongly recommend it. If the reporting were enhanced then it would be even better.

I would rate this solution an eight out of ten.

• Product backlog
• Work items (Features, User Stories, Bugs, Tasks)

We transitioned into an agile software development shop around 2010. Using TFS allowed us to document our requirements as Features and User Stories on a Product Backlog, which allows all team members to access them at the same time. They can see updates and changes to them in real-time. It also supports our iteration-based development approach effectively, by allowing us to group features, and user stories into iterations, as well as forecast upcoming user stories into future iterations.

I've been using it for five years.

No issues encountered.

Previously we primarily used a waterfall software development methodology, so our move to TFS coincided with a reorganization we went through into an agile shop.

From a project/requirements perspective, transitioning into TFS was fairly straightforward. Instead of creating requirements documents for upcoming projects, functionality was documented as Features and User Stories in TFS. There was a learning curve for the organization as a whole who didn’t have much agile experience to be able to document and read requirements as user stories.

We use the solution mainly for store version control, backlog and product management.

Some of the valuable features are version control and the ability to create different collections in terms of segregating the authorization for teams who connect to small projects. The hierarchy they have is nice. The backlog management tool is good, you can manage your product backlog very easily and then assign your comments against it. 

This solution is quite old and it is already being bundled as Azure DevOps Server. 

In an upcoming release, more integration is needed.

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

The solution is stable.

I have found the solution to be scalable. There are approximately ten people using the solution in my organization.

I have used Jira In the past and if you compare Jira with Microsoft, Jira integrates from portfolio to project, to product, to version control management. Everything is linked in Jira. If you have a company portfolio of several programs that someone can see. If your responsibility is at a program level, you can see all the projects under it. You can even go to product backlogs for each program and got the code version control to see the programs being developed.

In terms of Microsoft, they have an organization structure. You can create multiple organizations, but Azure DevOps is only for product management. If you have your project risks and plan, that is outside Azure DevOps. You have to go to a separate tool in Microsoft, which is Microsoft Project. If you want to go to content management, if you stay in Jira you have another tool, which is also integrated into the overall platform, and that is called Confluence Content Management. If you use Microsoft, then either you need to do it on SharePoint or you will be using Teams.

The installation was easy.

We had a team doing the implementation, it was their first time and they did not have any problems. It took less than a week to do the full implementation. The amount of implementation personnel depends on the scope of the operation, but if you just want to get it up and running, then one person is enough.

The price of the solution is cheaper than other competitors and it is a per-user license.

I was using TFS in my previous company, which I recently left. Where I am currently employed, I looking to get Azure DevOps, and there will be approximately 20 to 40 users. It is a bigger project, it has more developers involved. This is where we are right now comparing what to go with DevOps or with Jira, or you can say Microsoft or Jira.

We did evaluate other solutions before this one. Since our use case for TFS was mainly version control. We looked at GitHub and Bitbucket, but I think the licensing model for TFS was cheaper than both of them.

If someone is looking for version control software and product management software today, then I would recommend them to go for Azure DevOps. If they do not have any restrictions in terms of keeping their data on-cloud, then they should go with Azure DevOps Cloud Service, because then you will not have to worry about installing anything on the server. If you want to have an on-premise solution, then you can use the Azure DevOps Server version.

I rate TFS an eight out of ten.

I am an end-user, using this solution to assign tasks for my development team.

The most valuable feature is simplicity. It's very easy.

It's simple to design and it's straightforward. This is an advantage for TFS.

They should have design patterns in TFS for the development team, and design patterns for the QA. QA around the world basically does the same thing, and also development. Similar to Scrum, they should have something already built-in.

I would like to see templates for design added, and the option to make it more complicated.

I have been using this solution for five years.

This is a scalable solution. I have plans to increase usage.

I worked with Jira two years ago. As a product, Jira is better but it's much more complex. It is hard to design but after that, it's easy to use.

It was already in place when I arrived. I was not a part of the initial setup or the deployment.

It's a good product and it's fulfilled all that I want it to do.

I recommend this product. If you are looking for something simple, TFS is what you should use. If you are looking for a more complex solution then I would suggest going with Jira.

I would rate this solution an eight out of ten.

• Version control
• Project management
• Test management
• Release management

• Agile project management
• Enterprise level development
• Testing of large enterprise applications

Test case management could be improved.

For over 12 years now.

Nope. The product is very stable.

Nope. The product is absolutely scalable for use in large enterprise companies.

10 out of 10 is the technical support that I have received from Microsoft.

We used VSS earlier, then switched to the TFS product.

Setup has very specific documentation that needs to be followed 'exactly', and it's straight forward.

Microsoft changes licensing and pricing every year. Best thing to do is reach out to their licensing/sales folks for the latest info.

Yes, Perforce and Git were evaluated, but we wanted a single solution for the entire SDLC. This product fit the bill.

It's an outstanding product, but needs technically qualified people to administer this product.

The version control itself (version history, branching and merging), shelving change and build server.

With TFS online, now everything is in the cloud, it is tidy and easy to compare and restore, especially my unfinished work, where I use the shelving changes feature. It's very useful.

I can't see any major improvements for now. Maybe the comparing tool is too simple, but I'm using an alternative, so I have no problem at all.

We've used it for five years, basically for source control. I used work items once for a very short time, so I can't consider it as "used".

No issues encountered.

No issues encountered.

No issues encountered.

I've not had to use it.

I had to use TFS because it was there in the companies where I worked, but I also used CVS and Git. I think that TFS is easier because it is already integrated with Visual Studio, if you are using Visual Studio.

I've never setup a TFS server.

if TFS was completely free (not limited to five members for online), I would suggest using it, but the price for extra members is too expensive in my opinion and is worth it only if you are using Visual Studio, otherwise other solutions can do basically the same (talking only about source control).

• Source control
• Work items
• Team build

• It's easy to implement agile methodology, updated and uniform code on work spaces.
• Work items allows easier tracking for risks, bug and issues, and tasks.

As of now, TFS delivers what we need on the project/business.

I've used it for seven years.

No issues encountered.

No issues encountered.

No issues encountered.

I haven't needed their help yet.

I haven't needed their help yet.

For source control, I've used SVN Tortoise before. TFS is more useful, organized and user-friendly.

Straightforward. Usually no issues being encountered when setting up.

We used a vendor team from Microsoft.