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)
Rider
Score 9.3 out of 10
N/A
JetBrains supports .NET development with Rider, a .NET IDE based on the IntelliJ platform and ReSharper.
$14.90
per month per user
Pricing
Azure DevOps Services
JetBrains Rider
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
For Individuals
$149
per year per user
dotUltimate for Individual
$169
per year per user
All Products Pack for Individuals
$289
per year per user
For Organizations
$419
per year per user
dotUltimate for Organizations
$469
per year per user
All Products Pack for Organizations
$779
per year per user
Offerings
Pricing Offerings
Azure DevOps Services
Rider
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
dotUltimate: All .NET tools, ReSharper C++ and JetBrains Rider, together in one pack
More Pricing Information
Community Pulse
Azure DevOps Services
JetBrains Rider
Considered Both Products
Azure DevOps Services
Verified User
Engineer
Chose Azure DevOps Services
As a cloud services user of Azure, using Azure DevOps made sense because it has the most support tailored for Azure ecosystem.
Verified User
Employee
Chose Azure DevOps Services
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.
Initially you may think it’s not worth paying and that there are better free options, which is definitely a lie we once tried to live with. It has everything you may ever need in .NET world, code analysis and debugging works super well and all the SQL/noSQL related integrations are just next level compared to the competition. It’s worth every penny.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
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.
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Rider is a great IDE with extensive C# refactoring support and .NET-specific knowledge. This is great for building .NET applications but for our purposes, the Unity specific suggestions are really helpful.
JetBrains Rider is great as an editing and debugging environment. It reliably connects to the Unity editor and allows debugging, which some IDEs are not as reliable at doing.
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.
The support forums and knowledge base are extensive and the JetBrains support staff respond quickly to new posts and help resolve issues. There is also a publicly accessible issue tracking system, which allows you to stay on top of any bug fixes or enhancement requests.
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.
Rider is hands down smoother and way less glitchy than Visual Studio Enterprise. There are way more refactoring capabilities and spell check so that your code is readable, maintainable, and easy to follow. Since Rider is cross-platform, our developers are no longer constrained to only using Windows. We can now get a familiar development environment across Mac, Windows, or Linux!
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.