TFS Reviews

We do a user story for a use case, which is like a snapshot of one pass through a use case. We tend to align them with the branches in Git. We have story branches created in Git and edited in TFS, which correspond to user stories based on a use case.

The solution's iteration board is good because you can track all your work with it. In TFS, you can do pull requests, trigger builds automatically, and gate them so that they're reviewed thoroughly before you release them. It is a good practice that makes things a lot easier.

If you've got 100 iterations and you create a new story and try to select which iterations, it doesn't default to the current iteration. You have to scroll right down to iteration 100 in the drop-down list. It would be good if it defaulted to the current iteration rather than having to go down a long drop-down list to select it when it's right at the end.

IBM ClearCase has something called a Version Tree, where you can see all the commits and updates to the configuration as a series of nodes in a tree diagram. You can also do mergers from the different branches using that. I'd like to see some kind of visualization tool for TFS that would make life much easier.

I have been using TFS for six to seven years.

I rate TFS ten out of ten for stability.

Hundreds of users in our organization use TFS.

I rate TFS a nine or ten out of ten for scalability.

The solution's initial setup is not too difficult. The people who set it up were experts who could quickly get it up and running. So, it looked like the setup was straightforward for them.

TFS is deployed on the cloud in our organization.

Overall, I rate TFS an eight out of ten.

The solution was used for software development.

It is very user-friendly.

Since the TFS was an on-prem solution, the private network accessibility was restricted. 

I have been using TFS for a year. 

It is a stable solution. I rate the stability an eight out of ten. 

It is a scalable solution. Presently, twenty to thirty users are using the solution. 

The technical support team is good and supportive. 

Positive

The IT team deployed the solution. 

There is a yearly licensing fee that needs to be paid. 

I rate the overall solution a nine out of ten.

While I don't recall the exact version we are using, I do know that we upgraded to the latest one.

We use the solution for project planning, code repository and for releases, everything really. 

Primarily, we have used it as a code repository, something we have been doing for many years. We have not made much use of the other features. 

The project management side should be addressed and the project and release planning should be somewhat extended. The solution cannot be used as a project management tool on its own. 

Although clear, the installation is of medium difficulty. It could be better and easier. 

I have been using TFS for more than five years.

The solution is very much stable. 

We have encountered no issues with the solution's scalability. 

I am not aware of ever having contacted technical support. 

TFS is the first solution of which we made use. 

While clear, the installation is of medium difficulty. It could be better and easier.

I do not know how long it took. 

Not too many people are needed for the deployment, perhaps four or five. They consist primarily of engineers and there is one manager. 

I am not in a position to comment on the licensing terms, as we are talking about an enterprise arrangement. I am not part of that.

Subsequent to TFS, we evaluated and tried making use of Jira and Azure DevOps. 

There are around 250 people making use of the solution in our organization.

At this point, I would not recommend the solution to others. 

I rate the solution as at least an eight out of ten.

We use TFS for volume control, source checking, and source control.

The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals.

We have different teams working on different solutions using different technology sets. At the backend, it has good source control. We work with Microsoft technology stack, open source stack, as well as IBM stack. We have different teams working on the backend with TFS as our source control.

I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code.

As a version control, we have found some inconsistencies related to updates from previous versions. If you set up the Git repository, and you want to change it back to TFS, it is a bit confusing now in the latest update. We were hung up when two repositories were intermingled together. We were confused about why the Git project was not converting to TFS. I believe Microsoft is supporting the Git repositories. 

The TFS TFVC is not user-friendly because, for Git repositories that you have already created to use the TFS repositories, you need to go back into the ID to Video Studio when the TFS repository comes up by default.

Using the web interface, by default you get the Git repository. For a team that is not familiar with this and is not using the ID as a video studio or VS, code management gets difficult. Even with VS Code as an open source ID, TFS at the backend as a repository is difficult and integration is complex.

I have been using TFS on a daily basis for five years.

So far, I have found TFS to be stable.

The solution is scalable, however, we do not need to scale because we do not have many people on each team. The administration part requires three or four people, and for development teams, we have about 15 team members who actively use VS Code.

The initial setup of TFS is really just a click. It is basic and not complex.

We deployed the solution in-house.

Our organization has an enterprise license with TFS.

We explored other sources before. We also used some open-source tools.

We are considering trying another solution as we don't find TFS assistance or community help when compared to Git.

TFS is a good solution once you get comfortable using it. If you are coming from TFS 2013 or TFS 2015, you are going to find the 2019 version different. I understand that TFS is moving towards the cloud, so all the features are designed with this in mind. In the 2019 version, you will see more DevOps-related tools and automated app tools.

The solution is easy and complex at the same time. If you are familiar with pipelines, you will find it interesting. You need a technical team to provide help and assistance to get the whole value from 2000 DevOps TFVC. If you are not actually fully exploring the feature set or using them, it is just another source control like any other open-source control.

If you gain experience with the iron value sets with TFVC DevOps, the whole project management will be smooth and stable. Releases will come out but all the hiccups between the teams, such as the development teams, QA teams, and deployment teams will smooth out. 

I would rate this solution an eight out of ten overall.

We use it for code archiving, complete CI/CD functionality, code propagation, code repository, etc.

Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part.

The price could be cheaper.

We're going for a cloud solution that will give us similar functionality and integration with our other products that we are customizing, like SFD. At present, those codes aren't many. 

I've been using it for more than eight years.

It is stable.

It's scalable. We have around 45 users.

We deployed it using an in-house team. You will need two to three people who are in the DevOps teams, who do all the testing, and programmers, who use it and check the code.

You will need to obtain server and account licenses.

TFS is a good product, and I would rate it at eight on a scale from one to ten.

We use TFS for manual testing in our labs and as an automation tool., basically use TFS and we have the shared for that. 

The TFS was previously used for the build repository, but we have moved away from using it and we use other tools for builds. We are moving towards JIRA for other activities, such as cascade management, and test automation management.

The most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful. 

I have been using TFS for approximately seven years.

TFS is highly stable. We have a lot of queries and the test plans can generate for automation purposes and runs very well. I prefer TFS over Jira in this area.

TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools.

We have more than 200 users using this solution.

We use JIRA in parallel with TFS and we are facing a lot of difficulties with JIRA because we do not receive the leverage and the same features in JIRA that we do in TFS. Our preference is TFS over JIRA.

There is some maintenance required from our team. For example, licensing and overall support. 

When the applications are developed in VideoStudio and other technologies. It's preferred to use TFS for all of the management solutions.

I rate TFS a nine out of ten.

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.

I use it  for managing. To manage the project in Git and manage branches in projects. 

Merging branches is definitely one of the more challenging aspects for people new to TFS.

I have been using it for three years. 

Stability is okay. I would rate the stability an eight out of ten. 

I would rate the scalability a six out of ten. Sometimes, a lot of branches get mixed together, making it difficult to use. I remember struggling with these branch management issues some time ago and even wrote about them. It is so hard to review problems in TFS.

There are around 200 end users using this solution in our organization. 

I found Git to be a better overall experience. Merging branches in TFS, especially merging to the master branch, could be quite difficult. Git seemed to handle it more smoothly. However, after two years, the company decided to switch to Git.

For experienced users, it might be manageable, but for non-technical users like nurses, branching and merging in Git proved difficult. They often had to ask for help from team members because they found it challenging.

Overall, I would rate the solution an eight out of ten.