Item: Azure DevOps Server
Rating: 8
Author: Luca Campanelli

Overall Satisfaction with Team Foundation Server

Use Cases and Deployment Scope

In my organization Team Foundation Server is used to better manage all projects and application packages. Having several developers in place and having to work on multiple projects Team Foundation Server allows you to have complete control of all developments and to manage independently and with order every release and every package developed without loss of data or misalignments.

Pros and Cons

Pros

No data loss
Multiple deployments
Deployment without problems of versions

Cons

You must avoid getting stuck with check-in
Developers must avoid overwriting
The developers must be at minimum coordinated among themselves during the developments

Return on Investment

No time loss
No data loss
Easy rollback deployment

Likelihood to Recommend

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.

Comments

Please log in to join the conversation

Arie Heinrich
commented 7 years ago
The three points you noted are not a problem with the tool. This is pure people a.k.a. developers mindset and how they were taught to use the tool. There is no tool that replaces inter-person communication and TFS actually tries to maximize the collaboration between developers. - Getting "stuck" in Check-in isn't something you get out of the box. This is a setting the TFS admins or Developer leads have setup the tool to enforce. - Developers must avoid overwriting - that's pure communication. TFS actually has an option to allow multiple edits at the same time or forcing just one edit at a time, which ever the dev lead or mangers decide is the best option for them, so still not a tool problem, its' human decision and human communication. - Devs must be coordinated between them - like last point, communication and responsibility for their actions

Manage with order software deployment