We use TFS for all of our source code. We develop a software suite with about eight different applications that work together, and then we also do firmware development. We use it for our firmware development source code repository.

It is deployed on a private server. We've gone all the way from version 2012 up to 2017, and we will be doing the 2019 upgrade very soon.

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.

It is easy to push our changes from quality to pre-prod and prod. We also use TFS for maintaining our data.

TFS is used for version control. So, other software can integrate with TFS. The tool is also used for documentation and STLC.

We use this solution mostly for our clients. It's a lifecycle management tool. We use it for the entire lifecycle of software development. Then we deliver it, and use it for production support. Basically, you can always use it for your requirements, as well as to track the health of your project.

With respect to all the Microsoft Stack development, we use TFS as a repository and source version control system.

TFS is useful for managing the code, such as code versioning, and managing where we store our soft-coding repository, which is where we can manage the versioning with the owner. The main purpose of using TFS is for managing our soft-coding, branching, and tracking of our different branches.

We use TFS for forecast management.

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

We use TFS for project management.

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

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

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.

We use this solution for test management and defect tracking. 

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.

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

The solution was used for software development.

We use TFS for bug detection and incident management. 

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 use case is as our repository for UPS Enterprise and the performance is pretty good.

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

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.

TFS is mainly used for day-to-day project management i.e. all the tasks, user stories, and test case management are done on TFS.

I use TFS as a code repository for version control.

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.

We are using TFS for testing.

My company uses the product for some of our developers who develop software on a server, after which they need to import it before collaborating with their teams. In general, the development team in our company uses the product.

We use the solution to store all the code and designs for software version control.

I use TFS to assign and manage projects.

We are using the core repository for the complete development life cycle. 

We use this solution for corporate internal SW development of small business applications manly in .NET.

I am the administrator and configurator of TFS Servers and other DevOps related tools (Jenkins, Ansible, Nexus, SonarQube). I create the projects and configure the full life-cycle, with a deployment model mainly on-premises for now.

We are using TFS for source control.

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. 

The primary use case of this solution is version control.

We use it for ticketing protecting particular items, we use the dashboard, and we use the Kanban board where you can put work items.

The deployment model that we are using is on-premises.

We have used TFS as part of our SAFe Agile Implementation.  Major uses of it were:

• Project management
• Backlog management
• Issue tracking
• Source code management.

We use the solution for creating a by-log and setting up the IPV. Also, we use it for the two-part deployment process. It helps us with application life cycle management and task management.

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 use TFS for source control. We are investigating the cloud option.

At my previous company, I was using TFS for managing projects and code.

The primary use case for TFS is for sharing data.

We use Microsoft Team Foundation Server as part of our development framework. Most of our development technology is from Microsoft and our primary language is C#, although we do have a number of Java programmers as well.

We primarily use TFS for managing our resources and scheduling. We can also use it to check to see whether tasks have been completed by the team, or not.

We use TFS for test management. Our entire project management is done through TFS.

We have our test cases uploaded, and we use it for user story tracking and progress tracking.

TFS is on our client's VMs.

I am an end-user, using this solution to assign tasks for my development team.

It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code.

We have a DevOps team and we primarily use TFS for bug tracking.

We use TFS for source control and we use code to connect to TFS as well. It's all generated and the normal process for a developer; we take the latest coding, and whenever there is a build required, we get the latest from other developers and carry out the build. We also do branching and leveling. I'm a solution architect and our company has a partnership with Microsoft. 

We use this solution for test management, bug management, and product backlog items grooming.

We use the solution mainly for store version control, backlog and product management.

Most of our development is .NET based, integrating with GitHub and the code. It has been performing well. This is why we have been using TFS.

Yes, TFS provides complete solution for ALM, We are managing the TFS Service for all the organisation like complete development, Development + Support model, Only Support model using Kan-ban board.