TFS Reviews

• Source Controlling
• Application Development
• Project Life Cycle

When we applied the CMMI standards in our SDLC we used TFS to force some policies to control the project documentation and source controlling, and to manage the relationship between concerned parties.

TFS administration tools need to be more controlled and easier to use.

I've used it for a total of seven years, and for the last three years, I have used it more as a TFS administrator not only as an end user.

No issues encountered.

No issues encountered.

No issues encountered.

Yes in 2007 we used a different source controlling tool and we faced a lot of issues and with no GUI we had to deal with it using commands which made our life even harder.

TFS, like most Microsoft products, is easy to install use. The initial setup is very easy, all you need to know is the basic configurations that need to be applied.

• Version control
• Code backup

I have spent less time merging code from developers.

They can improve the stability and merging features, especially with SSIS.

I've used this version for four months, and previously I was using TFS2010 for two years.

No issues encountered.

There were some minor issues.

No issues encountered.

I have not needed to contact them.

I have not needed to contact them.

I previously used MS Source Safe and TFS was just the logical progression.

We did it in-house.

You could use a less expensive product, but if you need integration with MS Visual Studio this is the best product.

The system admins evaluated a few products.

As a QA geek, MS Test is the most valuable component.

Being able to easily create new bugs during the execution of a testcase in MS Test, then resume testing is a time-saving feature.

It is very difficult to delete work items from the database. It would be helpful if MS provided a way to simplify that.

I've used it for over three years at three different companies.

No issues encountered.

No issues encountered.

No issues encountered.

I have never needed to contact Microsoft about this product.

I have never needed to contact Microsoft about this product.

I was not responsible for the initial install of TFS, but the setup/config of both requirements, test cases and test plans was straightforward.

We did it in-house.

I was not involved in the buying process.

We use this solution for test management, bug management, and product backlog items grooming.

This solution enables us to link all items usefully, in the way we use Agile.

The most valuable feature is having everything in a single interface, allowing quick and efficient browsing.

The test management interface is not very handy.

I would like to see improved metrics in MTM.

• Change control
• Collaboration
• Change history

TFS has allowed our development team to function better as a group, by keeping code organized, and making it easier to prevent people from stepping on each other's code.

The interface needs work. As it is, it takes a few weeks to get new team members used to using it.

I've used it for two years.

No issues encountered.

No issues encountered.

No issues encountered.

We used GIT, and we switched because TFS was easier to use and maintain.

It was straightforward.

We did it in-house.

We are currently using the free version.

We also lookeed at GIT.

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.

Most of our development is .NET based, integrating with GitHub and the code. It has been performing well. This is why we have been using TFS.

It brings in collaboration between our teams.

The biggest value-add is the solution integrates well with most Microsoft products.

Since it is Microsoft, it is technology agnostic, thus it does not really fit into various different technologies in the organization.

We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS.

There is no downtime. It is a very stable product.

I would rate scalability as a six out of 10.

I have been with the company only for the last one and half years, and the TFS was already in place. In my previous job, I used a different solution.

I was not involved in the initial setup.

It is pretty expensive compared to other project management tools.

This product choice was influenced by the development team more than any other team due to the development around .NET and its accompanying technologies. The product works best for development teams.

Overall, I would rate this solution a seven out of 10. We have many different teams, and it does not work well for all them, e.g., applications for management tools.

Most important criteria when selecting a vendor: I look at reviews of the product because these are real companies who have been using this particular product.

I especially like the Build and Release features since I mainly work in that area with customers.

It has sped up the build and deployment process. We can now deploy the same application version to each environment in a repeatable and automated fashion.

I think the testing tools need some work.

I have used TFS since 2015. I have used the latest version since it first came out.

No issues with stability.

No issues with scalability.

10 out of 10.

No, I have used this solution for 12 years now.

It was very easy to deploy the on-premise version of TFS. The wizard really helps facilitate the ease of the deployment. The web version is super easy to setup and it takes a little more than 10 minutes to be up and running.

I cannot advise as the costs and licensing vary by organization and the type of agreement that they have with Microsoft. I direct all those types of questions to Microsoft.

No other products were evaluated, but I have setup other solutions for customers.

Don’t wait too long. If you can use the cloud version, it has so much less overhead and you also stay up-to-date on features.