TFS Reviews

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.

We use this solution for corporate internal SW development of small business applications manly in .NET.

I am the administrator and configurator of TFS Servers and other DevOps related tools (Jenkins, Ansible, Nexus, SonarQube). I create the projects and configure the full life-cycle, with a deployment model mainly on-premises for now.

Better team collaboration and Issue tracking.

I like the build management features, the integration with Jenkins and many other tools.

The team rooms for team collaboration, and issuing the backtracking are very valuable features.

One of the areas that could be improved is to have an effective full life-cycle management.

For example, when the developing team has an issue with a bug, they can relate and tag sources and builds to that bug, but after that, it's not easy to track if those builds where in fact deployed.

In the next release, I would l like to see a modern solution with a full integration of the real life-cycle.

This solution is stable.

This solution has some scalability.

We have contacted technical support (local Microsoft) a couple of times I would rate them a four out of five or a nine out of ten. They are good and I am satisfied with the help that I have received from them.

Previously we used manily another solution (Serena Dimensions CM). But specially Java developers hated it, so we start to migrate to GIT and Jenkins for them, while .NET developers prefer to use TFS.

The initial setup was straightforward. We did have some issues, speacilly in the use of the databases but due to our customer internal policies, who were old fashioned and gave us some problems, but we can't blame the software for that.

TFS licencing can be confusing, we have to read it well and have a good user management strategy and control.

We evaluated modern versions of Microfocus and SVN, we still have Dimensions CM but will be discontinuing it.

The primary use case of this solution is version control.

We use it for ticketing protecting particular items, we use the dashboard, and we use the Kanban board where you can put work items.

The deployment model that we are using is on-premises.

I really like the dashboards in this solution. They are good for the team, where you can provide announcements and you can organize it the way you want.

I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is.

I know that they want to discontinue the version control feature, but I like it because for simple applications, it works.

In the next release, I would like them to include integration for various projects, similar to what JIRA has, and they could create this feature on the dashboard. 

If they could create a feature to allow us to see the dashboards with all of the products, it would be useful.

This solution is pretty stable. I have not experienced any issues.

This solution is scalable and it is simple. 

From my experience, we have loaded a lot of work and we have several branches.

We have perhaps one hundred users, but in my team specifically, we have eight users who are engineers, testers, and a few managers.

We have not contacted technical support because issues are handled by the team internally.

We have not used any other solutions previously. This has been the first one with version control.

We have an internal team that handled the implementation of this solution.

I am currently evaluating JIRA. The management is considering moving everything to JIRA.

This solution is simple to learn. It's straightforward and you don't need a lot of time to learn the functionalities.

I would recommend this solution.

I would rate this solution an eight out of ten.

It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code.

It's one continuous integrated solution that includes the code. We can put all of our work from tasks with cases and user tool requirements.

The dashboard needs more enhancements.

We have used TFS as part of our SAFe Agile Implementation.  Major uses of it were:

• Project management
• Backlog management
• Issue tracking
• Source code management.

TFS was the first system of its type to be implemented in the organization, which helped in managing requirements and multiple teams effectively under a SAFe Agile environment.

• Requirements
• Backlog management
• Project management

Each tool has the option to prioritize requirements in a backlog pool, assigning them to particular teams and particular iterations. The system has also helped in managing requirements with options to attach supporting documents. 

From the project management perspective, the tool is efficiently managing teams by giving management information, such as reports, graphs, velocity, capacity, etc.

More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively.

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.

The use case is as our repository for UPS Enterprise and the performance is pretty good.

It is a big improvement because before we were using PBCS.

Build definitions and releases within the product. They allow us to put our latest applications in the field.

Right now they are up to standard. All the features that we needed are included currently in TFS, including Git repository which allows our developers to perform their code-testing without impacting by uploading the latest code in TFS. It fits all of our needs.

100 percent stable.

It's completely scalable.

I give technical support a rating of A-plus.

The previous solution was PBCS which was obsolete for our team and that is why the company decided to invest in TFS.

When selecting a vendor what's most important, speaking from a money point of view, is that it be cost effective. It should have good support like Microsoft doing provides with TFS, and be easy to use as well.

Initial setup was straightforward.

The other vendor was HPE but we decided to go with Microsoft.

It has great functionality: work items, backlogs, source code, build releases, and it's easy to use.

TFS is very easy to integrate into your system. It's very easy to follow for any new developers. Also, I would say some 80 percent of developers out there use Visual Studio which is integrated with TFS.

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.

1. SCM functionalities
2. ALM Features
3. Build capabilities
4. Deploy options
5. Web portal
6. Release management
7. Support for multiple languages
8. Plugins for open source tools, like Sonar and Jenkins
9. Very good user-friendly UI
10. Test management - capturing/creating defects
11. Reports
12. TFS community, APIs, and support

• We have set up a centralized TFS server.
• All the delivery projects are clients for this TFS.
• They are using it for code repository, ALMs, and for DevOps implementation.

1. Customization of build templates - better tools
2. Tracking
3. More friendly on test lab setup (TFS 2013, I did not verify on TFS 2017).
4. More user-friendly on SharePoint integration (TFS 2013, I did not verify on TFS 2017).

We having been using this product for more than three years.

All for my entire development project, the major SCM tool has only been TFS.

Nope. Installation was very easy. We set up a 'multi-node' installation:

• Application tier
• Build server
• Database server
• Reports server

No, stability is fine.

We encountered some issues with the report server part when the service user password changes, otherwise until today have not faced issues on the production environment.

Nope.

Very good.

Very good.

We used VSS and most of our projects are in Microsoft stack. I opted to choose TFS for incorporating DevOps with easy integration VS IDE as there are many advantages.

Setup is straightforward. As I mentioned earlier, we did a multi-node installation.

In-house.

Yes.

No idea on this one as it was done by different team.

Yes, VSS and Git.

Integration with Visual Studio (VS): I have used other software management solutions with VS, but TFS is the best at the moment. It offers easy integration with servers and full functionality.

Another very good feature of TFS is the build server. With it, I can quickly and easily generate binaries for testing and production environments.

• Local branching
• Move folders using drag & drop
• Better resolve for merging the conflicts tool.

Around eight years.

No. Nothing which I have noticed.

No, but I have never worked in a big company with many developers or projects.

I can't rate. I have never used technical support.

We were using Microsoft SourceSafe, but is unreliable and slow. These issues are enough for anyone decide to change to another software management tool. As we are a Microsoft partner, we naturally switched to TFS and are happy with this solution so far.

Very simple and straightforward, which makes for a very good, first impression.

This is the negative side of TFS; the price is expensive. Microsoft offers VSTS for free if you have a very small company and don't mind to keep your code in the cloud. But if this isn't the case, you have to pay too much for licenses (in the cloud or out of it), especially if your company just needs to track the changes in your code.

No, because we are a Microsoft Partner.

Use the free version of VSTS first, to just to have an idea of what it is. It's even possible to build binaries online.