Azure DevOps Server

Formerly Team Foundation Server

Because of the microsoft ecosystem and the product is also build on ms services cloud which uses azure internal services so it is easy to integrate.
more reliant support available for the microsoft services because of the well established user community of the product and services. It is also easy to learn because of good documentation

Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.

Managing projects is a breeze using Azure DevOps Server, and the tool also automates testing and checks to see if the project is within its scope. Intuitive, with a low learning curve for novice users; it's also simple to collaborate on projects and keep tabs on their progress because of its tight interaction with other Microsoft tools.

Honestly speaking, GitHub is better in terms of version control and Jira has better functionality when it comes to Agile boards, other than that, the UI could have been a bit better for Azure DevOps Server. In all other areas, I feel overall Azure DevOps Server is better.

In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!

I was new to the agile methodology when it was first introduced to the Enterprise. Different project teams opted to leverage different project management tools, two of the most common being Jira and DevOps. For someone overcoming a huge learning curve already, I felt that DevOps was easier to intuitively navigate and had a much smaller learning curve than Jira.

My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other companies - but it was a large issue from my position.

Overall Atlassian products seem to be less stable. Azure DevOps [Server (formerly Team Foundation Server)] also has Test Center and Build functionality built in. This prevents needing a handful of separate products loosely coupled together to get a comprehensive solution to take software from start to release. This creates a more seamless experience for developers.

At the time we brought Azure DevOps in-house it really was the only game in town. Our company migrated from Visual SourceSafe to TFS to Azure DevOps without any issues or downtime. Git isn't overly intuitive so I never recommend it and shy away from it. I loved it when Microsoft gave MSDN subscribers a free local version for in-home use but that seems to have gone by the wayside. Still, your choice is Azure DevOps or Git.

Azure DevOps has a

• backlog module which is a substitute for Jira / Trello
• pipeline module which is a substitute for Jenkins / TeamCity
• artifact management module which is a substitute for Artifactory
• test case management module unmatched by the above
• dashboards and reporting module unmatched by the above

(an end to end SDLC solution similar to how GitLab is)

I was not involved in the purchase decision for this product. Since I have started working at my company, we have always used [Azure DevOps Server]. So I can't comment on how it performs vs its competitors. I have used many project management tools that are not as robust, but I didn't list them here since they are not direct comps.

The other ALM tools I've used and administered are Rational ClearCase and ClearQuest, HP Quality Center and Microsoft Source Safe. While Rational ClearCase and ClearQuest are excellent tools in their own right. I find that TFS does the best with integrating all aspects of the ALM in one place.

I've used and currently use Jira, which is a similar software to Azure DevOps Server. Azure DevOps Server is more detailed and comprehensive than Jira. They both offer many of the same features and capabilities but Azure has a better overall interface and is more in-depth. It is also very user-friendly.

Azure DevOps Server is a fantastic tool and my favorite for organization and management of large application building projects. It was selected for its ease of use with a user-friendly design that allows any team members, particularly outside of developers, to quickly get up to speed and see visually where the project is headed. It also is a Microsoft tool so there is trust with the name.

TFS is more of a GUI; has more features integrated into the product.

TFS tool by default comes with a git version control repository which offers centralized TFVC and distributed git version control.

Microsoft Azure DevOps is the one that integrates everything you can possibly use and provides a solution that eases your developing process. It has a strong support community and well-written documentation. No matter what you do, you will always find the right pipeline. It is also very stable and performs well.

I was not involved in selecting the tool.

Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose and hence always need to be integrated with some other tool for achieving the target. While Azure DevOps integrates within itself all features and utilities required to deliver the code from developer machine to the production environment.

TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a decision making process.

The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly and to became more reliable. If you are using programming languages and tools that are not from Microsoft, perhaps Team Foundation Server will not stack up against other technologies.

TFS can be used for both version control and also for tracking items.

Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because the integration into Visual Studio is not as good.