"The most valuable feature is the complete integration between test cases, pipelines, and issue management."
"The initial setup is quick and easy."
"It's got something that you won't find in other products."
"The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment."
"The installation is straightforward. We can create a whole new organization in less than a day."
"The initial setup is very easy."
"It is a well-integrated product in terms of the development lifecycle."
"I really like the Microsoft DevOps survey."
"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."
"The interface is easy to navigate."
"Good branching and labelling features."
"Basically, the capacity to construct various products is something I find handy."
"Some of the valuable features are version control and the ability to create different collections in terms of segregating the authorization for teams who connect to small projects."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"The most valuable feature is the backlog."
"It's is a very stable solution."
"I have not been able to use the integration with automation features, such as test management automation, with a framework that is written in Java."
"The solution can improve by adding integration with on-premise tools. The only built-in repository options are GitHub and DevOps."
"The testing environment and different pipelining concepts can be improved."
"Some of the queries, the way they're built, need to be looked at. We need better query tools."
"The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow."
"The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code."
"The price could be lowered. It would be nice if it was cheaper."
"With the query feature, we have to group items, so it becomes difficult for everyone to understand it. It's easier in JIRA, which has filters and other query options."
"It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"The execution of test cases could stand improvement."
"There are many things that I cannot do, and I have a lot of bugs."
"The dashboard and the customization of dashboards is an area they have to work on."
"The interface can be improved and made more user-friendly."
"The user interface could be improved to make it simpler and increase usability."
"The usability of TFS is not that great."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 77 reviews while TFS is ranked 6th in Application Lifecycle Management (ALM) Suites with 17 reviews. Microsoft Azure DevOps is rated 8.0, while TFS is rated 7.8. The top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". On the other hand, the top reviewer of TFS writes "Good traceability for managing workflows, but not flexible enough for agile environments". Microsoft Azure DevOps is most compared with Jira, GitLab, ServiceNow IT Business Management, Red Hat Ansible Automation Platform and Micro Focus ALM Quality Center, whereas TFS is most compared with Jira, Rally Software, Visual Studio Test Professional, Micro Focus ALM Quality Center and Zephyr Enterprise. See our Microsoft Azure DevOps vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very friendly user interface. I think TFS does have a few valuable features, though, such as its project management, which happens to not only include user stories, but task management as well. It would be good if TFS offered better integration for third-party tools like Jira. For my needs specifically, for example, I need to do a lot of manual tasks, and integration with SharePoint is not easy. Other than that, I consider the product to be pretty solid, stable, and also scalable, and haven’t experienced too many issues with it.
In contrast to TFS, Azure DevOps provides a seamless user experience that is not only consistent across Azure DevOps service, but is consistent across Azure DevOps server too. It also has great navigation and the user interface is responsive, helping employees focus better on their work. Azure also allows users to connect GitHub Enterprise with Azure Boards, with no disruption to other workflows.
While both Azure DevOps and TFS require SQL Server, Azure DevOps server can be hosted on virtual machines running on Azure. In turn, these support Azure SQL Databases give users superior backup and scaling options - and do so all without increased administrative costs that are usually tacked on to running such complex services. I also like that Azure DevOps has advanced search capabilities. For example, certain features allow information from different components of the product to be accessible from whichever parts users are working on. You can also expand the search box from the product header, which I find useful and a great addition to help improve navigation.
Conclusion:
Azure DevOps is a better match for me than TFS because it has several new features and more additional benefits than TFS can offer for my needs.
Hi @Netanya Carmi,
Both are good and in fact, TFS is now rebranded as Azure DevOps server.
Now the point is about your requirement, if your requirement is to work closely with Cloud Services Cloud Application and you are Ok to manage your code and CI/CD plans over the cloud platform then go for Azure DevOps whereas if you can't move the data to cloud use Azure DevOps Server.
But for such tools my first choice is Gitlab.
Rest you can call me at 9717996125 or drop me at kulbhushan.mayer@thinknyx.com to discuss further.
Both, it depends on what you want to do with it and what is your technical environment.