Back to TFS reviews

TFS Review

Supports Multiple Code Repositories But Needs Improvement On Its Agile Functionality

What is most valuable?

TFS can support multiple code repositories (example: Git, TFS, CVS, etc.) via plugins, which is really a nice feature.

How has it helped my organization?

As I mentioned, it supports multiple code repositories. You can also build CI/CDs out of it. You can instruct TFS to build your .jar, .war, and .ear files and deploy them to to certain environments based on your configuration. So you don’t have explicitly maintain another code repository and CI/CD tools for your continuous integration/build purpose. This also automatically reduces DevOp burden and the number of people maintaining that DevOp work.

What needs improvement?

It needs huge improvement on its Agile functionality.

For how long have I used the solution?

For more than a year, until I left the company.

What do I think about the stability of the solution?

No.

What do I think about the scalability of the solution?

No.

How are customer service and technical support?

We had our own support member (so I can't rate their support).

Which solution did I use previously and why did I switch?

Yes, I used to use VersionOne, HP AGM, and JIRA to track and monitor Agile practice in my previous companies. At Lennox they had only one option, TFS.

How was the initial setup?

I wasn’t involved in this process.

What's my experience with pricing, setup cost, and licensing?

I wasn’t involved in discussions of pricing or licensing for TFS at Lennox.

Which other solutions did I evaluate?

As far as I‘m aware, the company decided to use TFS without evaluating other options.

What other advice do I have?

There are better tools for Agile and CI/CD in the market. TFS may be good for code repository purposes; however, it's not the best for Agile practice.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.

Last updated: Aug 15 2017

More TFS reviews from users