TFS Reviews

We are using TFS for source control.

The most valuable feature of TFS is its compatibility with Microsoft Windows systems. We have predominantly Microsoft solutions and TFS work well.

The user interface could improve and test management was not useful in TFS.

I have been using TFS for approximately three years.

The support from the vendor was good.

We switched from TFS and now we use Jira.

The initial setup of TFS was complex.

We did the implementation of the solution in-house using our own knowledge and we did some training courses in TFS.

We evaluated GitLab and Github for source control and Jira for ticketing handling. The newer versions of TFS are better but at the time we found Jira to be more user-friendly and TFS was more technical which is why we switched to Jira.

The effectiveness of TFS depends on the specific use case. It's a suitable solution if the user primarily operates with Microsoft tools, such as Azure DevOps and others.

I rate TFS seven out of ten.

The interface is good with TFS.

I am looking for some pull request features, like Git.  I do not see a pull request option for branching and merging. I would also like a true command prompt like Git.

I have been using TFS for the past fourteen or fifteen years.

TFS is definitely stable.

TFS is scalable because it is managed by Microsoft internally. 

Technical support is good. We have optional support with Microsoft.

We previously used VSTS however TFS is a far better product.

The initial setup was very easy and straightforward.

The overall price of TFS is good.

I think most people are working with Git. We feel comfortable with TFS because we are already used to it. TFS is a good product and you can continue working with it.

I am overall happy with TFS and would rate it a nine on a scale of one to ten. 

I use this solution in my organization as a product owner who manages backlogs in DevOps. I manage the backlogs items and use it to collaborate with my developers.

There are less than 100 people using this solution in my company.

The solution is deployed on-cloud.

It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration.

I only use 1% of the functionality, so I am not familiar enough to know what needs to be improved.

I have been using this solution for a couple of years.

It's stable.

It's scalable.

I would rate this solution five 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

As the solution is cloud-based, we always use the latest version. 

We use it comprehensively for client career management. We can use it to read test cases and link cases. Everything is done in TFS.

I feel that the test plan and test tools are more manageable in TFS.

In the TFS tool, we, essentially, made the test cases and test tools. The execution of test cases could stand improvement. They have provided many ways to manage the execution, but they can streamline it to one or two ways. People do not wish to try all the alternative methods.

We have been using TFS for three years.

When it comes to stability, the entire process is good.

I have no issues with the scalability. It is fine. 

I have do not recall occasion to contact TFS technical support. 

I cannot state for certain if we were previously using a different solution, as I would have to know to which year you refer. Again, we have been using TFS for three years. 

Installation is totally fine. I have no issues with it. I do not recall how long it took. 

Installation can be done with the help of the technical team. We are talking about the same team, consisting of around four people and a single manager. 

We pay for the license yearly.

They're slowly migrating the solution to DevOps at the moment.

I would recommend the solution to others. 

I suggest that those looking for enterprise wide solutions can go with TFS whereas, if they are short on team members, they can try the alternative. Smaller teams can try Jira, as well. 

I rate TFS as a seven to eight out of ten.

It is mainly for the work item handling, which is the documentation for the development projects. We also use it for requirement handling and then following a project's progress with tasks or issues.

It doesn't improve the way our organization functions, but it supports the way we work. Instead of having separate Excel or other work item lists, we can just utilize the work items provided by TFS for record-keeping and monitoring the progress.

The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements.

It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools. 

Currently, we are looking for a solution with which we can incorporate third-party development sites or third-party project teams into the system. Because it is on-premise, it is a bit problematic because we need to have a VPN or something else in the system. A cloud-based solution would be better for us, and that's what we are looking for. Our biggest problem is the external connection, which, of course, is limited by our own IT. It would be good to have some kind of publishing service for this external connection. It might be there, and it might be that our IT is making it impossible for us.

Its template editor could be easier to use. Currently, customizing the project templates according to your needs requires some work.

I have been using this solution for 15 years. I have been using its latest version for a couple of years.

It is reliable.

I haven't actually used their support very much. I'm not really the one who is maintaining the system. 

You can find a lot of information by searching the web. There is also a community around it, and a lot of answers are available. Microsoft has its own support if needed.

I haven't been so much involved in building up the TFS server, but I think it is rather simple. The installation is simple. There are so-called project templates that you might need to adjust according to your needs. These require some work. If you can use the default templates, then no work is needed. We have managed to adjust everything for what we needed. There were no problems that we couldn't overcome. Its template editor could be easier to use.

It was done in-house. It is pretty easy to come up with an installer. There is nothing difficult there.

The Team Foundation Server is now called Azure DevOps. We are using an old product. I would advise others to consider whether they need an on-premises or a cloud solution. The on-premises solution requires external developers. They can also look at the cloud option and see which product offering is better for their needs.

It is a nice system to have. You get a managed system where you can manage your development tasks easily, and you don't need to keep your own bookkeeping for tasks and backup items. They are already there in TFS. You can just use the system monthly and produce reports out of the system. For me, it was nice to see that such a tool exists.

I would rate TFS a nine out of ten. I'm pretty happy with it.

We are developers using the TFS for controlling, and for continuously developing our code.

I am not familiar with all of the features, as I only use it a bit for some of my projects. 

I am using the new kit because it is open source and has many good features.

What I like the most is that you can set permissions on just one folder.

For me, it was easy to use.

There are many things that I cannot do, and I have a lot of bugs. For example, if I want to merge two branches together, sometimes TFS will merge them automatically and I couldn't find the changes and had to check them myself.

That wasn't very good for me and I couldn't understand all of them and wasn't able to interact with them.

The merging could be simplified and improved.

I would like to see more features included for branching so that it copies your source code to the other branch, and have it in a separate folder.

We have been using this solution for five years.

We have not had any issues with stability. It's a stable product.

It's a scalable solution. We have 100 users in our organization.

I found the initial setup straightforward and easy.

We have a team of four or five to maintain this solution.

We are using the open-source version.

I would recommend this solution to others. It's definitely a good product. If you are looking to set up custom privileges then it's a good option for you. It has several features. If you want to secure your code, TFS is a good choice, as it can do it easily.

I would rate TFS a five out of ten.

We mainly use it for source control.

In the past, I've used it throughout the whole CI/CD. I've worked with Scrum and Agile methodologies. From the user story, from the product backlog to the CI/CD and deployment. I've used it for everything — the whole nine yards.

At my previous company, there were a lot of employees using this solution; it was the only system that was being used. 

Currently, there are a lot of products for managing the product backlog. The usability of TFS is not that great.

Integration from an agile perspective could be improved. Jira is far better in this regard.

I have been using TFS for over a decade.

It's is a very stable solution but when compared with Jira, Jira has taken over. The question should be: how agile is TFS? From this perspective, TFS is lacking — the ease of usability is less.

TFS is not that scalable compared to Jira. It's scalable at the story level and at the project level but in the grand scheme of things, it's hard to manage it from an entire product perspective. 

It depends on what kind of program your company has. Personally, we didn't have to deal with Microsoft tech support very often relating to TFS. 

It depends on which point you start. From my experience, problems occur when you already have a development and then you adopt the agile method and try to work it into your source code.

Our IT team handles deployment and all maintenance-related issues.

It depends on what methodology. You can use it for the entire software development process, from the user story to the code and the integration and deployment — the whole nine yards. That's something to be taken care of and set up diligently.

On a scale from one to ten, I would give TFS a rating of seven.