What advice do you have for others considering TFS?

TFS is effective for code management and tracking but could benefit from improved automation and simplified user management. Overall, I rate it a seven out of ten.

Overall, I would rate it a nine out of ten. I recommend to use it.

I rate the overall tool a six out of ten.

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

TFS is deployed on the cloud in our organization. Overall, I rate TFS an eight out of ten.

I rate the overall solution a nine out of ten.

I rate the solution an eight out of ten.

I rate TFS an eight out of ten.

TFS is a scalable and useful solution. I rate it a seven out of ten.

I rate the solution as a seven. I advise others to prefer Azure DevOps as it has better features than TFS.

Before choosing TFS, they need to check the development program used earlier by their company. If they have used something linear to Microsoft, then TFS is an apt tool for them. I rate it eight out of ten.

Since in our company, we are already trained to use the solution, and so we never face any issues or problems while using the solution. The pre-existing features in the solution are more than enough to meet our needs. The solution has a user-friendly interface. The solution already allows for more integrations with other solutions. Also, there is a separate team that works on the solution. The solution protects the systems in my organization. When it comes to the products offered to customers by TFS, they are constantly evolving since it has been in the market for twenty years. Also, we keep getting updates for the solution every second or third day. I have a laptop, and if I start the solution on that laptop after two weeks or three weeks, I won't be able to connect. I need to take it to my technical support team. They will install some updates, and then I will be able to use my laptop. So, from this, one can figure out how much the solution has invested in their system. So, it is very rare that the solution faces any issues, and if any issues crop up in the solution, they have a very robust system of dealing with such problems. They have a good IT team that quickly resolves any issues. So, people are working to improve the system day by day. Every day, there is an evolution in their products. Some teams are working on production issues because of the new features implemented in the tool. Also, they are monitoring it continuously. I rate the overall solution a ten out of ten.

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.

I recommend TFS to others. I rate TFS a nine out of ten.

I rate this solution a nine out of ten.

I would rate TFS eight out of ten.

I would rate this solution five out of ten.

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

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.

The only advice I would give is to design the security model and the developer model assuming that you have a larger team of developers than what you have when you start. You should set it up originally for multiple users to be working on the projects rather than having to change your methodology partway through. We made some decisions on how we structured our source code and how we structured our team projects, and I would not have done that if I had known that the developers would be working on it in the fashion that we do now. Your configuration for ten developers would work with one developer too, but the configuration for one developer doesn't always work for ten developers. So, set it up for ten assuming that you're going to be doing that. I would rate it a seven out of ten because of the issues with the upgrade path, restructuring folders, and things like that. If you don't configure it right to start with, it's a little bit difficult to change. That's the only reason that I'm not giving it a nine. If I have to make the same decision again, I absolutely would buy it again. It does what it was advertised to do, and it's not causing us any harm. It's doing its job, and it does it well. There are just a few things around the upgrade and around the restructuring of source code that could be improved. That's all.

I rate the solution nine out of 10.

I rate TFS a nine out of ten.

I would rate this solution 8 out of 10. I'd give it that rating because there are security glitches, but otherwise, from a usability standpoint and from the operational perspective, I think the products are really good.

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.

I am a project manager. I would rate TFS a seven out of ten

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.

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.

If someone is looking for version control software and product management software today, then I would recommend them to go for Azure DevOps. If they do not have any restrictions in terms of keeping their data on-cloud, then they should go with Azure DevOps Cloud Service, because then you will not have to worry about installing anything on the server. If you want to have an on-premise solution, then you can use the Azure DevOps Server version. I rate TFS an eight out of ten.

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.

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.

My advice to anybody who is considering TFS is that the suitability depends on what technology you are trying to use. For example, if you're using Microsoft technology then it is better to use TFS. If on the other hand, you are developing something outside of Microsoft, perhaps using an open-source tool, then I wouldn't be able to recommend TFS. Instead, I would choose one of the other many third-party tools that are available. I would rate this solution a nine out of ten.

In my opinion, I would say that TFS is more supportive of a large enterprise. There is a lot of information available online. The suitability of TFS depends on the requirements of the customer. If it is for Test Management, I would say that TFS is a product that they should consider if it's a large organization that has multiple or multi-thread implementations. Overall, I would say it's fine and I would recommend it. I would rate TFS and eight out of ten.

In summary, this is a good product and I strongly recommend it. If the reporting were enhanced then it would be even better. I would rate this solution an eight out of ten.

Overall the solution is good. It's scalable and stable and has been working well for us. Of course, the phased release could be smoother, and it's something they need to improve upon. I'd recommend this solution, even though we do plan to move to Microsoft Azure DevOps. I'd rate the solution eight out of ten.

It's a good product and it's fulfilled all that I want it to do. I recommend this product. If you are looking for something simple, TFS is what you should use. If you are looking for a more complex solution then I would suggest going with Jira. I would rate this solution an eight out of ten.

This is a good tool for core depository, but there are a lot of thing in TFS you can do: You can automate the entire update process. You can run your sprint and everything, it's a good option enterprise wise. Nowadays everything has DevOps so it's a good thing to use. I would rate this solution an eight out of 10.

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.

My advice to anybody who is implementing this solution is to use as much as possible, out of the box. Customizing it is difficult. It may not necessarily fit everything perfectly and it can be tricky to scale, but not impossible. There are definitely challenges scaling it. That said, the tool from Microsoft does allow you to do things very differently but try to do it in a standard way first. I would rate this solution an eight out of ten.

There is a gap between project management, agile methodology, and TFS resource management. If they can fill this gap then it would be a great improvement for us and many other companies. My advice for anybody who is implementing this solution is to keep in mind that using the tool, alone, will not change the way they develop their software. First, they should become familiar with agile methodology, and then they will be able to properly use TFS. I would rate this solution an eight out of ten.

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.

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.

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.