Azure DevOps Server (formerly TMS) Reviews

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

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.

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.

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.

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.

Azure DevOps is well suited if you have a big team that is collaborating their codes and need to have devops pipeline for all build and release work. Also since this tool provides bug management facility, you don't need to purchase any other tool for that purpose. Moreover if you have your infrastructure built over Azure cloud then this is a best match for your requirements as it integrates well with it.

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.

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.

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.

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

Team Foundation Server is well suited in product management

• Easier to build a technical backlog.
• Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
• Make a Product Manger's and engineering teams' life easier in meeting and tracking.
• Project managers can easily track the work and create reporting.

TFS is very good when working on a large project with a lot of moving pieces. When you have many BAs involved and a lot of user stories, it can be extremely useful to consolidate information. If you are not working on a large project with many users and developers, it may be excessive. However, in general, the tool is extremely helpful when implemented correctly.

TFS is well suited to developers and teams that work with Microsoft technologies and products. For other scenarios, alternatives like Git can deliver more powerful and reliable features. Also, developing software in branches is very difficult, as well as merging code. These tasks needs to be carefully planned to avoid broken code and headaches in your company.

Well, as said before. I like TFS for Source Control and automated Builds and Testing, but it could be improved in the area of Task Management.

Team Foundation Server is a very a very good tool when you are using with Visual Studio. It's very easy to check in/check out the code to the Team Foundation Server.
One can easily check the Task, Bugs and any change request items very easily from the Visual Studio. One can also check this items directly on the web browser as well.

if you are a development company or you work in a company with continuous developments it is certainly advisable to create a server dedicated to Team Foundation Server, surely you will have fewer problems in the deployment phase and you can always keep all the versioning of your software or your objects under control. Also, rollback in emergencies can be easily managed without losing too much time.

Team Foundation Server (TFS) is suited for anyone working in .NET. It's not appropriate otherwise. It's really as simple as that I think.

You could use some other source control with .NET but it integrates so well with the rest of the Microsoft family and is so reasonably priced, there'd be no need to.

TFS is a really good tool for managing small to medium-sized development teams. The ability to customize it to suit your own processes means it should be suitable for any business, though I have to confess I do not have any experience of using it within a large enterprise sized development team split across disparate locations.That said we do have developers spread across the UK and they manage to work remotely with no problems at all.

For a software development team, Team Foundation Server definitely ticks a lot of boxes. We use the Scrum methodology and Team Foundation Server enables us to manage current sprints and plan for future sprints. Even for 'pet projects' that some developers have, Team Foundation Server is a useful tool to submit their code for archiving and creating tasks to work on those projects.

I think if you work in a Microsoft exclusive environment, this is the tool for you. If you are in an arena where you might have C#, Java, or Python other tools might be better suited to your needs. TFS can be very costly but if it is instituted correctly with RM tools, it can be a wonderful thing. If you are a small shop use a free source control.

[Team Foundation Server is well suited for] Agile - Kanban boards [make it] simple and easy to see progress. Shared queries allow for all to see information, centralizing communication. [It is also well suited for] Managing projects to preventing scope creep. Provides full tractability to ensure testing covers requirements, tree queries allow export of test coverage or lack there off. The tool provides collaboration between Development and QA with the trace data and log files gathered as a test case is being executed.

TFS is well suited for a team looking for structured requirements, projects, test cases, bugs, user stories, etc. It works well for planning things out and coordinating with others to see the "bigger view". TFS is great in scenarios where paper trails and other auditable data is needed to keep people in check and accountable. The search and query functionality allows users to search for past issues that may have been resolved previously and have crept back, and can provide history and context surrounding project functionality/decisions.

TFS might not work as well for a team truly looking for a scrum experience. Although my companies have both claimed scrum, they both planned out releases at least a few weeks in advance. If you're changing things on a daily basis it might not be as great of a tool.

TFS is especially well suited for .Net shops if they already have MSDN subscriptions; in that case it's pretty much free and a great all in one ALM suite. TFS now supports development of any tech stack, so it should also be evaluated by teams doing more than just .Net development.

I think Team Foundation Server is well suited for companies looking to do web-based status reports for projects and I think it works for organizations looking to implement Agile Methodologies. It makes implementing SCRUM techniques into a project very easy as well as being user friendly. Accessing and shelving code is easy for coders to understand and use so that others can not make any changes to a piece of code unless it is checked in. It makes a whole project run smoother knowing what stage it is in and seeing where the issues are occurring by being able to access the status of each project over the web if you don't have the software downloaded to your PC.