TFS Reviews

We use TFS for our Agile board to handle our sprints, epics, stories, and tasks, tracking how work is progressing. It is also a repository for managing code changes.

TFS integrates seamlessly with Visual Studio and Azure Cloud, facilitating continuous integration and continuous deployment, which enhances the development workflow.

We used TFS for our repository, maintaining the source code, and automating certain deployments from Dev to QA. We implemented automated scripts for testing. These are the main uses of TFS including versioning, product versioning, maintaining different branches for different clients, and having different code repositories.

Since we also use it for product management, release management is a significant aspect for product management companies. We have to ensure that the code and database are completely and fully maintained with all necessary components. Many of our team members use TFS because they use it for check-in and check-out of their codes while working, ensuring that nobody overwrites their code.

For test capabilities, it is always a mix. Where there is a licensing requirement, based on the number of licenses the team has, we utilize JMeter and Selenium. These are preferred wherever I had been, primarily because of cost reasons.

Version control is the most basic feature in TFS. It has been there since the beginning. We use it primarily for that purpose.

Basically ensuring that the code is not overwritten by other team members and maintaining the sanctity of the code. Bringing order to a disparate team which is virtual at different locations is very important, and TFS provides that control. Once you update a code, nobody can modify it until you are done working on it and check in.

It is a great product that revolutionized the way teams work together on Microsoft pieces of code. The versioning part has unique features and capabilities which are unmatched with other products out there.

I've worked with TFS for source control and Agile project management. We also used TFS for seamless team collaboration and tracking. 

I used TFS for a couple of years. Now, we use Azure DevOps. It's a wonderful tool for source control and CI/CD pipelines.

It's a really valuable tool for development projects, especially. We can leverage TFS, or even now Azure DevOps, for the entire lifecycle process.

My primary use case is within the organization's work environment, which is mainly focused on Microsoft products and TFS as part of our corporate IT infrastructure.

TFS allows me to handle automated builds and release management quite easily. It is user-friendly with a straightforward drag and drop interface, which makes it easier for me to create builds and release pipelines without needing to program YAML files. This setup is especially beneficial to me compared to GitLab.

For customers, we work in banking, finance, and healthcare domains, where there is a huge amount of data from customers and other types of applications and databases. We access this data for automation purposes. Many times, we utilize TFS for this type of thing.

Currently, we are focusing on the security features of TFS, such as the Credential Vault. We use it to store all credentials securely and provide access to specific stakeholders.

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.

The solution's iteration board is good because you can track all your work with it. In TFS, you can do pull requests, trigger builds automatically, and gate them so that they're reviewed thoroughly before you release them. It is a good practice that makes things a lot easier.

We use TFS for forecast management.

The tool is sufficient for our business.

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

It is a repository, so all the changes are saved. Also, even if there is some conflict, we have the merge tool and can use it to check the changes made by the developers. We can finalize which one to push to the server.