Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Azure DevOps Server
Score 8.4 out of 10
N/A
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.
N/A
draw.io
Score 7.7 out of 10
N/A
draw.io is an online diagramming tool with integrations with Jira, Google, and Confluence available free online or at cost depending on integration chosen.
$5
per month
Pricing
Azure DevOps
Azure DevOps Server
draw.io
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
No answers on this topic
Up to 10 Users
$5
per month
Up to 20 Users
$11
per month
Up to 50 Users
$27.50
per month
Up to 75 Users
$41.25
per month
Up to 100 Users
$55
per month
Up to 200 Users
$95
per month
Up to 500 Users
$152.50
per month
Up to 750 Users
$190
per month
Up to 1,000 Users
$227.50
per month
Up to 2,000 Users
$377.50
per month
Up to 5,000 Users
$827.50
per month
Up to 10,000
1,577.50
per month
Offerings
Pricing Offerings
Azure DevOps
Azure DevOps Server
draw.io
Free Trial
No
No
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Azure DevOps
Azure DevOps Server
draw.io
Considered Multiple Products
Azure DevOps
Verified User
Manager
Chose Azure DevOps
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software. On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
Compared to other tools we have used, Microsoft STS has been a much more complete tool. Communication, collaboration, tracking, management, automation, testing, speed to production—all these areas have been improved since we started using Microsoft STS. We have been looking for …
Our TFS was dated and in some ways was quite crude. VSTS is thoroughly modern and I don't have to worry about updating it since MS is always updating VSTS. Also, VSTS has better integration with other products such as JIRA than our older TFS would. I am sure you could integrate …
Being its predecessor, VSS has a very limited team-sharing view, providing little to no multiple-user, multiple-project support. Considering the fact that Microsoft has purged its support in favor of TFS and VSTS, it's only reasonable to believe they have something extra. Git …
Haven't used a lot of similar products that have the full feature set as Visual Studio. It's highly effective development platform especially when used with SVN and TFS makes large Agile project easy to manage and collaborate.
I haven't used any other products, so I can't say how VSTS/TFS would stack against any competitors, but I know that for an SDLC management tool, VSTS/TFS has everything you need to help an organization meet the requirements needed to adhere to the specific/general practices …
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
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.
draw.io can be more suitable for technical documentation for architectures, flow diagrams/charts, and conceptual images of an application infrastructure. However, this tool is not made for business intelligence work nor for dashboarding to monitor the technical components. From the administrative standpoint, this is not well suited for agile ceremony structures like retrospective boards or planning or even quarterly planning boards. The strength of draw.io lies strongly in being a lightweight diagramming tool.
Draw.io offers a lot of shapes and customizability of how the diagrams are laid out. We've been able to create a lot of different things with it, and have barely scratched the surface of the sorts of things that we could do.
Draw.io is fairly intuitive in the way that you draw shapes and connect shapes together, I was able to figure it out without a tutorial.
Draw.io is fast and performant for me compared with some of the alternatives.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
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.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
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.
The UI is intuitive. It allows a new user to start diagramming almost instantly. Manipulating elements, linking them together, etc. are all easy to do. Draw.io nevertheless a broad variety of diagram templates to help get started and also of shapes to use in diagrams. Some situations can make it a bit tricky to use, such as when having multiple shapes on top of each other (e.g. shapes placed within swimlanes) but that's a minor issue.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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
The support for draw.io is pretty decent, considering it is a free website. I had a question one time when I was trying to do something, so I sent an email to their support email and got a response fairly quickly with an answer to my question. They also have some excellent support tools on their support website for helping you get more familiar with their program, and I found that very helpful.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
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!
draw.io is open-source and free for many uses, which means minimal upfront cost and good value.It works in the browser, also has a desktop version (so you can use offline) which helps teams that may not always be online or want local backups. Useful when you want a diagram tool that “just works” without huge ecosystem lock-in.For organisations that value control, less vendor-dependency, this is a plus.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
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.