Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps 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.
BookStack is fantastic for having business users and not-so-technically-savvy IT users. It enables them to create a documentation they like in a visual way while still forcing them to adhere to logical structure of a document. It works fine even for more technical matters such as integration guidelines, especially when these concern some of the more obscure technologies. The exported docs are presentable but lack any interactivity. Where it lacks is generating heavily technical documentations. Heavier REST or GraphQL integrations should for example be documented through other means. As for developer documentations, there are definitely more suitable alternatives, also.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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!
Confluence, having only a slight advantage in terms of features compared to BookStack, really only makes sense to procure as a part of the Jira bundle. It requires much more maintenance from my experience and does not really deliver any extra value aside from the very strict certifications like HIPAA. DokuWiki and MediaWiki both provided way too much in terms of customizability, not really focusing on the business need. Of course, MediaWiki was conceived for a whole different purpose but is very often seen being used for both internal and public documentation delivery. DokuWiki did not provide the authors with the user-friendly environment that BookStack has and integrated most poorly with LDAP. As for OneNote, which was used for support docs prior to BookStack, it provided the authors with too much of a user-friendly environment, rendering the product of their work very inconsistent. Also, the sharing model was either peer-to-peer or within Teams, neither of which made it easy to audit and supervise.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
Spillover within Business IT staff up, nearly double substitutability. This is through the ability of a support technician servicing a different product to find a guide describing how to solve the more frequent issues the way a product lead would do it.
Time to draft and publish a documentation down some 20% compared to previous solution.
OpenSource that integrates fine with enterprise-grade software and somehow even passes security audit. 20 times cheaper to implement compared to Confluence, almost free to maintain.
