TFS Reviews

Record and playback is a good feature.

• Tech support needs a lot of improvement
• License is expensive

I've used it for six months.

No issues encountered.

No issues encountered.

No issues encountered.

Their support needs much improvement.

The company chose to switch from HP to Microsoft because of the expense of the licenses.

It was complex.

I don't know the ROI yet.

HP products were also evaluated.

• 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.

• 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.

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.

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.