Azure DevOps Server (formerly TMS)

Formerly Team Foundation Server

Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.

Integrating with Visual Studio makes it easy to see where things stand in terms of different projects' requirements, and the product is great for prioritizing and approving changes as they come up. An easy-to-use tracking and testing system ensures that all criteria are met, making this a great tool for project managers trying to keep their projects within their allotted parameters.

Scenarios where Azure DevOps Server is well suited: When the other tools you need to use are also Microsoft products bug tracking version control (although GitHub is better) Agile management backlog management scenarios where Azure DevOps Server is not well suited: When you need to integrate services other than Microsoft owned.

Great product to manage changes in project requirements and with the best prioritization and approving capabilities to multiple projects requirement needs and seamless integration with Visual Studio allowing simple and easy visibility into their status. Excellent tool to manage projects and prevent them from getting out of the scope with easy tracking and testing to ensure that it covers complete requirements.

In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.

DevOps is great for managing backlogs, requirements and resources. I don't have enough experience with this sort of software to comment on any downsides, my use is fairly limited but, it's great for my requirements.

The repro Feature “Azure Repros” was especially valuable in our use case as it was very easy to orchestrate the development of several developers via change requests. In this way, tasks/bugs execution was easy to plan and assign via boards and dashboards, and commits were documented in relation to planning objects and reviewed via the four-eye principle. Senior developers were able to oversee and review junior developers' work easily.

Azure DevOps Service I used in one of the Share point documents where we were facing issues to take back files and version history. Azure DevOps has very good document version control which makes it easy to manage the versions and changes in the document.

Our project team uses Azure DevOps to manage the epics and stories associated with one of our biggest internal enterprise-wide tools. It easily captures all stories in a simples way, creating room to include story points (for estimations), requirement notes, and design links (once ready). Additionally, it is simple to move tickets through the various stages of the process making it easy to tell the status of any given task - the ability to color-code tickets has made it exceptionally easy for me to locate the tickets specifically created for my design team to address.

In my capacity as an architect, the platform gives me the ability to define the architecture within a wiki. I can include details including flow, UML, and ER diagrams in the User Story of Features being defined by the Product Owner, and my engineering team can link the repository pull requests to the story being developed. My Product Owners can now view the business definitions, software architecture, code written, and QA tests performed all on one central platform.

More stable than Atlassian products but not quite as feature rich. I've supported both TFS (now Azure DevOps) and Atlassian products in the past. Nice to have an all-in-one stable suite but you may not have quite as many bells and whistles. I would choose less features over having to restart servers.

Azure DevOps works great if you spend most of your day in Visual Studio. If you plan on using VS Code, then skip it because Azure DevOps doesn't really work with VS Code. VS Code works with Git. For project management, Azure Dev Ops is okay, but project managers need to provide their team with links to where things are. Additionally, you might be better off using OneNote to document requirements and simply add links to your user stories where developers and testers can read the stories. The Word-like editor in Azure DevOps is extremely primitive.

Well suited:

• Large teams developing heterogeneous applications
• Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
• Company undergoes regular external audits of their SDLC practices
• Comprehensive reporting is required
• Pipeline templating is required
• Many git repositories are needed having to link to a unified backlog
• Access to backlog work items and reporting is required for business stakeholders

If you are a large organization that needs structure, Azure DevOps Server (formerly Team Foundation Server) is a great place to go. It does really benefit from others that have experience with the tool--that is a major plus. Azure DevOps Server (formerly Team Foundation Server) is particularly well suited for organizations that are looking to become more agile in the way they do business, especially in the way they code.

We still call it TFS. It is very useful for our marketing team and working with our developers. Every time we have a page, a bug, a user story, or an epic project, we can put the details into [Azure DevOps Server] and work back and forth with our dev team in there to complete the work.

Team Foundation Server (TFS) is best for large scale enterprise deployments. Not needed for a small company. With the infrastructure investment, TFS can aid large scale software development immensely. TFS is highly customizable, but if you go the route of heavy customization, don't upgrade to the latest version aggressively. Plan to invest in at least one full time TFS administrator. Make sure the users are properly trained.

The best use for Azure DevOps Server is for issue tracking and reconciliation for defects during the QA process.

It is well suited for any IT team, provides a great way to manage and track projects. Great for code reviews and bug management.

Azure DevOps Server is a great tool for keeping large projects organized. It is well suited for building large, business applications that require a lot of organization and history of the project that is accessible.
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.

Git is very popular right now and can be used instead of TFS for source control, but TFS can integrate with Git. Git has more of a learning curve than TFS, IMO.

Team Foundation Server (TFS), provided by Microsoft, provides you a wide array of collaborative software development tools that integrate with your IDE providing secure version control, extensible integrations, agile tooling among many others. You can set up an on-premise version of TFS or you can sign up for Visual Studio Team Services which is backed by Microsoft Azure if you don’t want the hassle of managing the infrastructure.

For companies, especially big companies, when they adopt the way of CI/CD, they need a build pipeline to realize all these. Either they develop websites with languages like Python, Ruby, or C#, or they set up infrastructure with Terraform, Ansible, or Puppet. Azure DevOps integrates everything together and provides a solution that works with all the technologies you use.

Great for source control, project management, and code reviews. It is really critical to put in place code review policies with required reviewers before a pull request can ever be merged into a target branch. As a senior developer sometimes I feel this can be cumbersome but there have been a few instances where I have caught a major error in a pull request and was able to prevent the code from being merged.

If you are using Azure as a cloud provider and want to build solid code management and overall software life cycle management, then azure DevOpsSserver is a great fit and should generally work. Also, the reporting features out of the box are really helpful and the higher management can get great visibility on how the code and product are being managed.

Our dev team is able to use Azure DevOps to do cross development or paired programming. The ease of deployment is wonderful. The integration with the current IDE and ways to track or monitor changes is also great. I would love to see it expand outside of only IT within our company.