TFS Reviews

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.

One of the valuable and interesting features is Coded UI automation.

It helps with the structure of the tickets. It can be modified and configured for different flows.

The record and play functionality needs some improvement. The record and play is tricky. In order to make it work for you, you need to do some workarounds. For instance, I use the Run application of the Windows. You need to use it properly.

The MTM is stable.

It can be used for a lot of web tests and Windows testing. I do API tests with Fiddler via MTM.

Microsoft has really nice support.

We used JIRA, but the technology is different. If the developers don't use TFS, then the MTM is really hard to integrate to the process.

The initial setup was easy, but it can be even easier if you get some help at the beginning.

It is a really fair price for the functionality you get.

I was using bug tracking systems. MTM is not only a bug tracking system, but you can also manage your tasks and test runs.

• Application Lifecycle Management
• Team Build Definitions
• Kanban

Developers are able to download code at any point in time. Helped in DevOps responsibilities.

• Team Build definitions
• Bug-tracking tools.

I've used it for around five years.

No issues encountered.

No issues encountered.

No issues encountered.

It's very good.

It's very good.

I used SVN, and wished to have a proprietary tool so choose TFS.

It was straightforward, using the proper documentation.

We used an in-house team.

Its pretty much dealt with using a Microsoft subscription.

Yes, TFS provides complete solution for ALM, We are managing the TFS Service for all the organisation like complete development, Development + Support model, Only Support model using Kan-ban board.

We have streamlined the Scrum process with TFS and the product maturity has increased a lot. The agility features which will help us to understand the project maturity and help us to grow with incremental model for every sprint.

This tool provides a complete solution for ALM. It is useful for every IT individual.

Protfolio Management, Complete Build release management are the new key features which can help the organization to achieve Requirement gather phase till deployment phase.

Every sprint Microsoft has planned for new releases includes fixing both the bugs and attuning the product to the customers' needs. If there is a need of new feature which needs to be updated in the forum and based on the voting the feature will be implemented.

Nope.

Nope.

An eight out of 10.

VSS, which has less features when compared to TFS.

Straightforward.

There is no product costing if you have a Microsoft subscription.

JIRA, Jama, etc.

It's a good tool. Please make use of it and get more benefits.

The ability to do everything outside of an IDE. I can do 99% of everything from a web browser.

1. Cross platform support is great.
2. Developing build definitions from within a web browser is fantastic.
3. Installing build agents from a command line makes maintenance easier to manage.

The security model could be more granular.

I have worked with almost every TFS version since TFS 2005.

Some of our build agents will go offline, but we believe this might be caused by the environment, not the product.

None.

Excellent!

We used Visual SourceSafe and it lacked the ability to branch code.

It was very easy to install and setup. TFS has come a long way and so has its installation wizard.

The pricing model has changed several times, even within the last several years, but, I believe, the model is cheaper than before.

We also use Bitbucket, but my focus is TFS, so I cannot comment on that. We also use StarTeam, but we are looking to sunset this product and focus on migrating all application development teams over to TFS 2015 and Bitbucket.

Before purchasing any hardware, you should review all the hardware requirements. Also, plan to scale if growth is expected. Build servers with more than one CPU, if you can have build agents assigned to each processor. For example, if you have a server with four CPUs, then you technically can have four build agents running on that server.

Code annotations and code review is the "most valuable" feature of this product platform.

RBAC management is too complicated for SCM and IT to manage, Windows Explorer integration of Power Tools is not reliable, Workspace synchronization is not reliable, does not support keyword expansion, does not support offline history and cannot even determine the current workspace version without being connected to TFS server, shelf sets cannot be versioned, shelf sets cannot be merged, and merges do not carry associated work items.  These are just the issues with version control.

Throw a dart, you will hit something that needs improvement in TFS.