In different roles that I've had with different companies, I've used CVS, which is a different source code system. It's on the Linux system. It's not on Microsoft Windows. I've also used TortoiseSVN. I find TFS much easier because it's fully integrated into our solution.

In the previous world, I wasn't the decision-maker about which one to use. I came into projects that already had those in place, and they were not developing on the Microsoft platform. I understand why they didn't use the Microsoft platform in that case. In our world, we're developing software that runs mostly on the Microsoft platform, so it made sense to do that. Originally, when I used other packages, I was working as a consultant. I was working at different places, and I was using whatever the decision-makers used at those places as their source code control systems. When we started this company and I was the decision-maker, I used the Microsoft TFS platform.

We used SSMS and Visual Studio before, but then we switched to TFS because it is a native product of Microsoft.

We were not using any different solution. This company has been working with TFS for as long as I can remember. We're now transitioning to Jira.

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.

We use JIRA in parallel with TFS and we are facing a lot of difficulties with JIRA because we do not receive the leverage and the same features in JIRA that we do in TFS. Our preference is TFS over JIRA.

The features in TFS are similar to those found in Jira. 

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

Yes, I used to use VersionOne, HP AGM, and JIRA to track and monitor Agile practice in my previous companies. At Lennox they had only one option, TFS.

Previously, we were using HPE ALM, QA Manager, Atlassian Stack, and small, customized ALM products. The change was made at the corporate level.

TFS is the first solution of which we made use. 

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

The previous solution was PBCS which was obsolete for our team and that is why the company decided to invest in TFS.

When selecting a vendor what's most important, speaking from a money point of view, is that it be cost effective. It should have good support like Microsoft doing provides with TFS, and be easy to use as well.

I found Git to be a better overall experience. Merging branches in TFS, especially merging to the master branch, could be quite difficult. Git seemed to handle it more smoothly. However, after two years, the company decided to switch to Git.

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

No.

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.

Not applicable.

Yes, I previously used VSS, but since it was just a source control solution, I moved to TFS, which offered much more features in one package.

We are still using TFS, however, we're considering switching to Microsoft Azure DevOps.

Previously we used manily another solution (Serena Dimensions CM). But specially Java developers hated it, so we start to migrate to GIT and Jenkins for them, while .NET developers prefer to use TFS.

We switched from TFS and now we use Jira.

We have not used any other solutions previously. This has been the first one with version control.

Back in 2007 we used Source Safe Control. When we realized that we needed a generic platform which would combine task and defects tracking with version controlling, we moved to TFS.

I have used a solution called In-House Coding, developed by our organization. 

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. 

I was using TFS at my previous company and my current organization uses JIRA. I would say that TFS is the more scalable of the two. With JIRA, you really need connectors and things like that. You have to have external addons to make it more scalable.

In terms of usability, JIRA might provide a better user experience but from an organizational and stability point of view, TFS wins hands-down.

Price-wise, TFS is better than JIRA.

We were using Microsoft SourceSafe, but is unreliable and slow. These issues are enough for anyone decide to change to another software management tool. As we are a Microsoft partner, we naturally switched to TFS and are happy with this solution so far.

No, we didn't use a different solution. TFS has been the solution from the beginning.

I have worked with Jira and TestRail as part of a different project. They are simpler than TFS. It is really easy to follow these other tools, but TFS has more features and its own unique way of functioning. JIRA has no facility to create test cases, but TFS has it. TestRail is good for writing test cases mostly; project management techniques are more in TFS and MTM. In short, MTM and TFS have more functions. Project management and test management can be done together in one tool.

No previous solution was used.

We used VSS and most of our projects are in Microsoft stack. I opted to choose TFS for incorporating DevOps with easy integration VS IDE as there are many advantages.

We used VSS and most of our projects are in Microsoft Stack. Opted to choose TFS for incorporating DevOps and easy integration of VS IDE. There are many advantages.

I did not use a different solution prior to using TFS.

We did not use a similar solution prior to implementing TFS. However, we did use Microsoft Project for scheduling. It was not specifically for the purpose of software development, but we used it for putting together the steps of a project. For example, first, the UI would be developed, and then the backend. These steps were listed in the project management software.

Yes we are using HPE ALM for Test Management, TFS was purchased to help support the development team

Previously, I was working with Jira and QC. 

The change to TFS was because our client moved onto to TFS.

TFS is more stable and more scalable. We handling multiple projects using TFS. Usability is good and it's very easy for me to have traceability with a view on everything. 

Yes. The company chose a different solution basically because of the higher cost.

We used TFS 2010. We don’t evaluate any other product because we only use Microsoft products.

The decision was not mine, but it was based on having a complete ALM solution instead of just a bunch of systems thrown together.

No previous solution was used.

Previously, we used VSS, which was nothing but a repository, so TFS was the logical step up. Since we develop almost exclusively on MS stack, TFS as a comprehensive ALM solution fitted perfectly.

I used before IBM Clear Quest, which had a very bad interface, was very expensive as they price per user, was very hard to modify screens, no flexibility to extend, and by the way it can only be integrated with IBM Clear Case source control.

TFS also is one license for multiple products "source control, work item, build management, reports" also it integrates easily with other products, by its powerful API.

Also it is not easy to find an IBM CQ , or an IBM CC consultant, while it is easier to find a TFS consultant.

Yes, we used JIRA. Since we have to pay for Visual Studio, licenses for coding purposes (and these licenses included TFS) it did not make sense to continue paying for JIRA, even though I really liked the JIRA solution.

We used HP QC, then we moved to TFS because of the client's affinity towards TFS.

I had to use TFS because it was there in the companies where I worked, but I also used CVS and Git. I think that TFS is easier because it is already integrated with Visual Studio, if you are using Visual Studio.

For source control, I've used SVN Tortoise before. TFS is more useful, organized and user-friendly.

Previously we primarily used a waterfall software development methodology, so our move to TFS coincided with a reorganization we went through into an agile shop.

We previously used SourceSafe.

I worked with Jira two years ago. As a product, Jira is better but it's much more complex. It is hard to design but after that, it's easy to use.

We used VSS earlier, then switched to the TFS product.

I have worked with similar solutions, albeit a long time back. Visual SourceSafe was one of them and it is now discontinued. We switched to TFS as part of an upgrade.

As a Test Architect, I have used varying solutions. So, it depends on the direction that the company is taking from a tooling perspective.

The company chose to switch from HP to Microsoft because of the expense of the licenses.

Yes in 2007 we used a different source controlling tool and we faced a lot of issues and with no GUI we had to deal with it using commands which made our life even harder.

I previously used MS Source Safe and TFS was just the logical progression.

We used GIT, and we switched because TFS was easier to use and maintain.

I have used Jira In the past and if you compare Jira with Microsoft, Jira integrates from portfolio to project, to product, to version control management. Everything is linked in Jira. If you have a company portfolio of several programs that someone can see. If your responsibility is at a program level, you can see all the projects under it. You can even go to product backlogs for each program and got the code version control to see the programs being developed.

In terms of Microsoft, they have an organization structure. You can create multiple organizations, but Azure DevOps is only for product management. If you have your project risks and plan, that is outside Azure DevOps. You have to go to a separate tool in Microsoft, which is Microsoft Project. If you want to go to content management, if you stay in Jira you have another tool, which is also integrated into the overall platform, and that is called Confluence Content Management. If you use Microsoft, then either you need to do it on SharePoint or you will be using Teams.

I have been with the company only for the last one and half years, and the TFS was already in place. In my previous job, I used a different solution.

No, I have used this solution for 12 years now.

We used JIRA, but the technology is different. If the developers don't use TFS, then the MTM is really hard to integrate to the process.

I used SVN, and wished to have a proprietary tool so choose TFS.

VSS, which has less features when compared to TFS.

We used Visual SourceSafe and it lacked the ability to branch code.