Try our new research platform with insights from 80,000+ expert users
Product Owner at PerkinElmer, Inc.
Real User
Reliable, good performance, good reporting tools, and useful for managing all of your development tasks
Pros and Cons
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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. 

What needs improvement?

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.

Buyer's Guide
TFS
October 2024
Learn what your peers think about TFS. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.

For how long have I used the solution?

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

What do I think about the stability of the solution?

It is reliable.

How are customer service and support?

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.

How was the initial setup?

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.

What about the implementation team?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Kumar Rajan - PeerSpot reviewer
Manager at Havells
Real User
Good user interface, with longevity in the market, optimal performance compared to other choices
Pros and Cons
  • "The interface is good with TFS."
  • "I would also like a true command prompt like Git."

What is most valuable?

The interface is good with TFS.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

TFS is definitely stable.

What do I think about the scalability of the solution?

TFS is scalable because it is managed by Microsoft internally. 

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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

How was the initial setup?

The initial setup was very easy and straightforward.

What's my experience with pricing, setup cost, and licensing?

The overall price of TFS is good.

Which other solutions did I evaluate?

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.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
TFS
October 2024
Learn what your peers think about TFS. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Kumar Rajan - PeerSpot reviewer
Manager at Havells
Real User
Good code check-in and check-out features, with an interface that is easy to navigate
Pros and Cons
  • "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."

What is our primary use case?

I use TFS as a code repository for version control.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

TFC is a stable solution.

What do I think about the scalability of the solution?

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

How are customer service and technical support?

We have not been in contact with technical support.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

The pricing is reasonable at this time. 

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user718215 - PeerSpot reviewer
AVP, DevOps Manager at a financial services firm with 10,001+ employees
Real User
Can Provide A Centralized Place To Store All Source Code And Build Information For Entire Organization
Pros and Cons
  • "Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology."
  • "Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI."

What is most valuable?

Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology.

TFVC is a file and folder based version control system, which includes the ability to check-out, check-in, label, lock, branch, and merge. The security model is extremely granular allowing permissions to be set at the individual file, folder, or branch level (with inheritance as needed). The Git implementation is comparable to other on-premise Git offerings, such as Bitbucket and GitLab. The Git feature set has improved greatly between the 2013 and 2017 (latest) versions.

Build: The TFS build engine allows us great flexibility in how we perform our builds. While continuous integration (build on check-in) is used throughout the majority of the organization, we also leverage scheduled and manually initiated builds. The build workflow is entirely customizable and extensible to suit any need. Out-of-the-box build workflows in TFS 2013 are very NET-centric, however this has been completely overhauled in the 2015 and 2017 releases of the product. The newer versions of TFS can be used to create builds for virtually any technology stack, such as iOS builds on a Mac, Android builds, Java builds on windows\linux, etc.

.NET API: The ability to hook into TFS with custom a .NET code via API calls is critical. It allows us to automate any and all version control and build operations that we need to. Custom tooling which interfaces with TFS is a major component of our DevOps strategy/code delivery pipeline.

How has it helped my organization?

TFS sits at the core of our entire software delivery strategy. Implemented and used properly, it provides a centralized place to store all source code and build information for the entire organization. We always know which version of the code is deployed to which environment and are always in a position to support the production code line. Custom automation surrounding TFS (via the API) has increased the number of code deployments we are able to perform 1000-fold in the past 5 years.

What needs improvement?

Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI.

New files/folders added to a branch are not automatically picked up as merge candidates requiring merges to be performed at a higher folder level (annoyance).

A broader view of the system-wide TFVC permissions would be beneficial. Since the security model is so granular, it makes it difficult to pull effective permissions for everything in TFVC into a single report.

For how long have I used the solution?

I have been a user for ten years. I have been a System Administrator of TFS for eight years.

What do I think about the stability of the solution?

No. I have experienced no system outages in the TFS systems, which I built and configured myself.

Obviously, a poorly configured server/database instance will have stability problems. However, there is extensive public guidance provided by Microsoft on setup, upgrades, and migrations.

What do I think about the scalability of the solution?

No. However, my user base has always been relatively small:100–200 users.

How are customer service and technical support?

Excellent. Every ticket which I have submitted to Microsoft Premier support has been responded to very quickly. I have been put in touch with very knowledgeable engineers, and reached a resolution quickly. Post-incident follow-ups and surveys are also performed to ensure that customers have a quality experience.

Which solution did I use previously and why did I switch?

No.

How was the initial setup?

It really depends on your use case. For a sandbox, you can have TFS up and running with a SQL Express instance in about 1 hour. That’s not a production-ready system, though.

Performing initial (first-time) setups is fairly straightforward – getting properly spec’ed servers/database instances, following the install guide. Performing upgrade/migrations can be complex depending on how much customization that you have to the product and what has changed between versions. If you have a lot of customization, then the upgrades are going to be complicated.

What's my experience with pricing, setup cost, and licensing?

Use the Microsoft recommended “seat-based” licensing model. This allows a single developer with multiple machines to consume only one client license.

Which other solutions did I evaluate?

We recently looked at moving to GitLab. We chose not to do this because we already have millions of lines of code hosted in TFVC and migrating all of that to Git would be a daunting task with very little value. Since both TFVC and Git are now available and since the feature set is comparable to GitLab, we opted to stay with TFS. Development teams can “choose their own version control technology” between TFVC and Git.

What other advice do I have?

Hire a TFS expert or bring on a consultant. Nothing will ruin your development shop quicker than a poorly implemented version control/build system.

Microsoft premier consulting services is very expensive, but they can typically get you setup from soup-to-nuts in three to four weeks. That will include extensive guidance in how to use the tool. Your internal resources should work very closely with any consultant as a learning experience.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Ashu Singh - PeerSpot reviewer
Senior quality analyst at Lalli
Real User
Top 5Leaderboard
The solution provides ROI with use but pricing is expensive and improvement needs to be made on stability
Pros and Cons
  • "The tool's installation is straightforward."
  • "TFS needs to be stable."

What needs improvement?

TFS needs to be stable.

For how long have I used the solution?

I have been using the solution for six months. 

What do I think about the stability of the solution?

I rate the tool's stability an eight out of ten. 

What do I think about the scalability of the solution?

My company has more than 50 users. 

How was the initial setup?

The tool's installation is straightforward. 

What was our ROI?

I have seen ROI with the tool's use. 

What's my experience with pricing, setup cost, and licensing?

TFS is expensive, and the licensing costs are yearly. I rate the tool's pricing an eight out of ten. 

What other advice do I have?

I rate the solution an eight out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Asst. Vice president, Applications Architecture at a tech services company with 10,001+ employees
Real User
Good project management features improve discipline and productivity in our application development lifecycle
Pros and Cons
  • "The most valuable feature from my point of view is project management, which includes user stories as well as task management."
  • "The user interface could be improved to make it simpler and increase usability."

What is our primary use case?

The primary use for TFS is for event planning, including things like writing the user story and then assigning tasks to the developers. Another task is writing test cases, then recording test results, and sending bugs to the team members. The third thing is that we use TFS as part of our CICD pipeline.

As part of our pipeline, we use it for checking in code and it acts as a repository. This leads to the fourth thing we use it for, which is to move the code from dev to QA to production. Essentially, we establish a complete lifecycle using TFS.

We also use it in conjunction with Azure DevOps.

How has it helped my organization?

This product brings a lot of discipline and consistency in the way that our developers use their tools. 

What is most valuable?

The most valuable feature from my point of view is project management, which includes user stories as well as task management. I would say that these features are critical.

What needs improvement?

I would like to see better integration between TFS and third-party tools such as Jira. For example, integration with SharePoint is not very straightforward and we need to do a lot of manual work.

The user interface could be improved to make it simpler and increase usability. Making it more user-friendly would be a good thing. While it is okay in some regards, it does not compare to tools like Jira. There is some complexity because there are a lot of features, but usability can still be much better and it would be more comfortable to use.

For how long have I used the solution?

We have been using Team Foundation Server for almost five years.

What do I think about the stability of the solution?

This product is stable and we have not experienced any issues with it.

The developers are completely dependent on TFS and are using it on a daily basis.

What do I think about the scalability of the solution?

TFS is quite scalable and there are different deployment options that are available. I don't see any problems with scalability. We have between 40 and 45 people in my department who are using TFS.

How are customer service and technical support?

The support that we received during the initial setup was the only time that we needed to contact them. Beyond that, we didn't have to ask for technical support. I wouldn't refer to our initial support as very technical because it was more about knowing how to perform certain tasks within the tool.

Which solution did I use previously and why did I switch?

Prior to using TFS, we used CVS as our code repository solution. All of our requirements and bug tracking were done using manual effort. We were using Word documents and things like that. However, all of that has now been put into TFS.

What led us to switch was the ability to track all of the developers' activities. Before this, getting visibility and deliverables was a real pain point. For example, we didn't know how many stories the developers had completed, how much effort has been spent, or where we were with respect to the tasks that were completed by the teams.

How was the initial setup?

I would say that the initial setup is of medium difficulty. You definitely need help from an expert, as it is not like I can just pick it up and start running it. TFS requires a little bit of expert support in setting up, and we received solid support from Microsoft.

Our deployment took place over the course of a week. It was not a week's worth of effort but we had to schedule calls for support. I would say that TFS can be set up and tested in a single day, although it may take up to a week to finalize things.

What about the implementation team?

During our implementation, we requested help directly from Microsoft.

Our in-house DevOps team is responsible for maintenance.

What's my experience with pricing, setup cost, and licensing?

I wouldn't say that this tool is cheap or expensive but in the middle. TFS is definitely not as expensive as some other tools like Rational Team Concert. Basically, I would say that it is affordable.

Professional Services is a separate cost from the standard licensing fees.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
System developer at Tieto Sweden AB
Real User
Top 20
Proves effective for code management, but the automation features could be better
Pros and Cons
  • "The initial setup was straightforward: creating a new project, importing code, and setting up branches."
  • "The product access management features and connectivity need improvement. Rights management is also complex and could be simplified."

What is our primary use case?

My primary use case for TFS is to track source code changes, including branching, merging, and comparing changes. I also use it to check in and out code, track changes, and maintain a history of modifications. 

How has it helped my organization?

The solution has been valuable in managing source control and tracking code changes, improving code management and development efficiency. However, it has not significantly impacted project delivery timelines or cost efficiency.

What is most valuable?

The product's most valuable feature is the ability to view and track the history of changes. It allows me to see previous modifications and helps develop similar features by referencing past work.

What needs improvement?

The product access management features and connectivity need improvement. Rights management is also complex and could be simplified. 

Additional automation features would be beneficial. 

For how long have I used the solution?

I have been using TFS since the early 2000s.

What do I think about the stability of the solution?

The solution is generally stable, though connectivity issues have occurred, often related to VPN usage.

Which solution did I use previously and why did I switch?

I have used a similar solution sparingly.

How was the initial setup?

The initial setup was straightforward: creating a new project, importing code, and setting up branches.

What about the implementation team?

The setup was done in-house.

What other advice do I have?

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. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
AmrEL Tahan - PeerSpot reviewer
Software QA Lead at Ajman Municipality
Real User
Top 5
High performance, useful bug reporting, and simple implementation process
Pros and Cons
  • "The most valuable features of TFS are bug reporting and its high performance."
  • "The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one."

What is our primary use case?

We are using TFS for STLC

How has it helped my organization?

It improved SDLC & STLC 

What is most valuable?

The most valuable features of TFS are bug reporting and its high performance.

What needs improvement?

The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one.

In a future release of TFS, they should be more integration and DevOps features added.

For how long have I used the solution?

I have been using TFS for approximately 15 years.

What do I think about the stability of the solution?

I rate the stability of TFS a six out of ten.

What do I think about the scalability of the solution?

The scalability of TFS is good.

We have approximately 50 people from our IT teams that are using the solution in my company.

I rate the scalability of TFS a six out of ten.

How are customer service and support?

I have not used the support from TFS.

Which solution did I use previously and why did I switch?

I previously used Jira. I did not switch solutions, the new company I work for selected TFS.

How was the initial setup?

The initial setup of TFS took a couple of days to implement. The full process was simple.

What's my experience with pricing, setup cost, and licensing?

There are different prices depending on the configurations. There is a free version available. There is no extra cost for the solution. However, the hardware could be something that needs to be considered.

What other advice do I have?

The maintenance of the solution can be done by one or two people.

I would recommend this solution to others.

I rate TFS an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free TFS Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2024
Buyer's Guide
Download our free TFS Report and get advice and tips from experienced pros sharing their opinions.