TFS Review

Provides traceability, test management, and source control. I would like to see better test automation.


What is most valuable?

Valuable features include total traceability, test management, source control, and extensibility.

How has it helped my organization?

The solution gives us support for Agile processes, including usage of board and burndown charts. It provides us with an estimation process to move to formal and test coverage for more visibility and accountability.

What needs improvement?

  • Test automation: There is only integration with the MS framework which requires us to use only a certain configured infrastructure. Even MS is changing this approach as integration should be done on your own (publishing test execution results into TFS).
  • Process customization: This is evolving but it is still far behind the competitors such as JIRA WI management, HPE ALM with events model and ability to manage all aspects of integration including VersionOne integration with multiple APIs.
  • Scaling for large organizations: There is no predefined approach for handling different types of projects. You need to build out your own way using community suggestions and your implementation resources. There are limited scaling strategies for large organizations with more than 300 users.

For how long have I used the solution?

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

What do I think about the stability of the solution?

There were some minor stability issues under a large load or during migration between versions.

What do I think about the scalability of the solution?

For large organizations with more than 200+ concurrent users, there can be some scalability issues.

How is customer service and technical support?

The technical support has been getting better since 2015, when MS started making more frequent releases, including a user voice application.

Which solutions did we use previously?

Previously, we were using HPE ALM, QA Manager, Atlassian Stack, and small, customized ALM products. The change was made at the corporate level.

How was the initial setup?

It depends on the project/organization size. For a small organization/team, it is very easy. For a large one, the process definition takes more time and then the setup can happen.

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

If you have an MSDN license for using TFS, it is a good tool to start from. Later on, you may prefer to select another suite. However, you need to be sure about change. TFS, as from 2015, is evolving very quickly including the CI server, GIT server, and code review process with pull requests support inside.

Which other solutions did I evaluate?

We evaluated HPE ALM, JIRA, and VersionOne.

What other advice do I have?

Look for the cloud version. It will give you an understanding of further development of the product.

Disclosure: My company has a business relationship with this vendor other than being a customer: We are an MS Gold Partner.
Add a Comment
Guest
Sign Up with Email