TFS Reviews

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 this solution for test management and defect tracking. 

Most of my work is in the defect area of the solution. I like the attachments which can be directly inserted and highlighted. Users get alerted so they know when there's work required which makes the solution quite efficient. TFS also has filters that help us create a dashboard for monitoring, as well as test and script planning.

I haven't been able to get access to the test case management and execution because it requires an extra license fee. It would be helpful if that was made available to all the users who have already bought TFS.

I've been using this solution for about three years. 

The solution is stable. 

The solution is scalable. 

The features in TFS are similar to those found in Jira. 

The solution came with our Microsoft package so no deployment was required, it was just a matter of clicking on the web link. We currently have more than 500 users and that will increase in the future. 

I rate the solution nine out of 10. 

We use it for software development, but we are moving to Jira.

We work with life science companies, and they need traceability. Because we have the capability of being able to provide the traceability that they require, it helps us with laying out what they need for their validation efforts.

The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager (MTM), and you can have everything that is related to a requirement attached to it.

It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies.

It should have some of the things that Jira has, such as boards. We're focused on the scrum boards where you can actually drag and drop work from one queue to another. There should be more flexibility where you can just drag and drop as a user and have more visibility about what's active, what's not, and what's assigned to you through dashboards.

I have been using this solution for almost 14 years.

It was quite stable. We did not have a lot of issues over all those years. So, it definitely was a reliable solution for a long period of time. It just was not flexible when we started moving to a more agile model.

It was able to scale to meet our needs. It also allowed us to do our customization. I'm not sure if that ended up being a good thing, but it did allow us to do what we wanted it to do.

We have about 150 users, and they're developers, FQA, software quality engineers, business analysts, user experience team members, and architects. For its deployment and maintenance, in general, there are four or five people. They are from the DevOps team.

We don't plan to expand its usage. We're transitioning to Jira.

Their support was good. We had the support we needed for both TFS and Microsoft Test Manager.

We were not using any different solution. This company has been working with TFS for as long as I can remember. We're now transitioning to Jira.

It was fairly complex, but some of it was due to us. We did more configuration and customization, and because we customized the system, it made it more complicated.

In terms of duration, some of our previous upgrades took several days. Most of that was the actual deployment, but the preparation took several weeks.

We did use an integrator once or twice. Our experience with them was good. It was easier because we didn't have to worry about a lot of things. They took the burden of the effort, and we just had to give them information.

We haven't quantified that. In general, there has been a great time saving because with what we've done around validation artifacts, we've been able to build it right into the system. So, we can automatically generate it at the end of a release. Earlier, it would've taken us six weeks to put together a validation package. With what we've set up in TFS, it would take us a week at the max.

I was working with the engineering team, and that was not under my umbrella. From what I can remember, its license was yearly. They had the licenses on a per-user basis, and they included MTM.

I'm not really sure what they did. It was already in place when I joined the company.

I would advise Microsoft to update the tool. If a lot of users are starting to move to Jira because of the agile environment, Microsoft might want to adapt a little faster and provide similar or better functionality. It has been reliable for a very long time, and I've been really happy with it, but you've got to be able to change with the methodologies and the environments.

I would rate it a six out of 10 because it hasn't changed enough. I would've given it a much higher rating years ago, but because of the lack of evolution and not being able to adapt to the current business needs, its rating is not higher at this point.

We use TFS for bug detection and incident management. 

TFS' most valuable feature is the triage process. It is a robust solution that is easy to use. 

The tool needs improvement in stability. 

I have been using the solution for three years. 

I rate the tool's stability a seven out of ten. 

TFS' scalability is quite good. My company has 25 users. 

TFS' deployment is simple. You need about five to seven resources to handle the deployment and maintenance. 

We have seen ROI with the tool's use. 

The tool's licensing costs are yearly. 

I rate TFS an eight out of ten. 

We use TFS for project management.

Basically, the capacity to construct various products is something I find handy. For example, I could write a user story and then add some tasks to it, as well as subtasks and test cases.

Everything can be linked together, making it easy for us to track down and document hours for each and every task, whether it's a task, above, or anything else.

Everything is interconnected. As a result, tracking and viewing the bulletin board dashboard and burndown charts, among other things, is much easier.

It's a one-stop solution that is useful and makes it easier to handle.

The overall ability in the Agile process has some room to improve, even though it is interconnected. When I worked on Jira, it had the capability of better linkage.

When it comes to project management, we are having trouble with burndown charts, which we can't seem to display. As a result, we have created new tasks and realigning our process. Rather than creating larger tasks, we are creating subtasks such as development tasks, QA tasks, and deployment tasks.

An area of improvement is when there is a login for a specific user story present, it should display automatically. This is an area that where we are having difficulty and struggling in.

The scalability can be improved.

Linkage and task management are two areas that we are having difficulties with. It could be more like Jira, which has a number of different plugins. In addition, I feel that the status should include additional options. For example, they offer fewer options for a specific task user story or bugs.

I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress. I would like to see an in-progress capability where you can mark it active, but you can also write that it is in progress. When I look at the dashboard, there is nothing there to show me what has been done or why it is active or not.

My company has been using TFS since it started. It may be more than 10 years. I joined the company a year ago.

We have been using it through the cloud during COVID and working from home. We can connect to it from any network.

There have been some lags in the past, and we have also encountered some latency when setting it up on the laptop. You may have some problems at first, but as soon as you connect to the internet and update your product, everything becomes stable.

Within our organization, for example, we use Microsoft Teams for communication, chats, and for calls. We had some issues with it being unreliable and not fully airing the sound over the laptop speakers and mic. I discovered that as soon as we updated the product, the stability was restored. There was a problem with Teams, which they fixed and updated.

Initial difficulties are to be expected, but things are constantly improving.

It can be scaled to some extent. The main issue is that, unlike Jira or any other tool, the burndown chart is not displayed.

I have never used technical support because I've never been in a situation where it has gone down and I needed to contact them, but I believe that because Microsoft is a reputable organization with adequate technical support right now.

I have also worked with Jira.

I come from a QA background, and we used to do automation. Jira was far easier to integrate with our QA automation frameworks because it has a large number of exposed APIs and public APIs that we could use, which is a positive development. Also, the burndown charts, as well as the ability to manage different Agile model frameworks, where we could use scrum in one project but also had to use Kanban. As a result, the transition from one framework to another was simple. These are the things I found useful but haven't seen in the case of TFS yet.

Initially, TFS was a bit complicated. Now that it's Azure DevOps the initial setup is much easier.

It's a one-stop shop for building code repository, and a version control system within TFS or Azure DevOps, as TFS has been renamed.

I am a project manager.

I would rate TFS a seven out of ten

I use TFS as a code repository for version control.

The most valuable features of the code check-in and check-out capabilities.

The code branch capability and build features are helpful.

The interface is easy to navigate.

I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects. As it is now, I can see the details of a single project by selecting it. However, I cannot see all of the scheduled projects at once.

I have been using TFS for between seven and eight years.

TFC is a stable solution.

This is not a scalable product. We have about 35 users in our company.

We have not been in contact with technical support.

Prior to TFS, I did not work with another similar product.

The initial setup is easy and can be completed within a day.

The pricing is reasonable at this time. 

We are currently in the process of upgrading to the 2019 version, which has many more features than does the 2017 version.

My advice to anybody who is considering TFS is that once you get used to it, the interface is very easy to navigate.

I would rate this solution an eight out of ten.

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. 

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.