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)
Craft
Score 8.9 out of 10
N/A
Craft, from the company of the same name in Tel Aviv, is presented by the vendor as a better way for Product Managers to manage and plan their products in agile environment.
N/A
Pricing
Azure DevOps Services
Craft
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)
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Craft is really well suited for any size design team - I have used it within a team of 3, and within a team of 30. It helps with collaboration within the team, and between external teams through 'sync' with Invision. It increases efficiency of using Sketch with things like 'data', 'duplicate', and 'stock'. These tools not only make designing faster, but also more realistic, allowing us to 'test' our designs sooner.
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 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.
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.
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.
Craft was originally developed in response to ExpressionEngine's shortcomings. While ExpressionEngine has caught up in some regards, it still looks and feels a bit unpolished by comparison. Additionally, ExpressionEngine's vendor has never gotten UI right - not on their website, nor in their CMS. Craft remains easier to use, more polished and provides a wider feature set in its base install (without needing plugins). As for WordPress - while I recognize its massive popularity, I find its reliance on themes, third-party plugins, along with security shortcomings, make it a poor fit for the larger custom projects we build. On the other hand, if you want to throw up a passable website in a day, you can't beat WordPress.
