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)
Autotask PSA
Score 7.8 out of 10
N/A
Autotask PSA is designed as a complete IT Business Management Platform for MSPs, now from Datto (resulting from the Autotask merger with Datto in 2017).
N/A
Pricing
Azure DevOps
Datto Autotask PSA
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)
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.
In my opinion, Datto Autotask is exceptionally complicated to set up, manage, and use on a daily basis. I would think the target market for this product would be someone managing a team of 20 - 50 people, possibly more. In my experience, for it to run properly you will need to dedicate at least half an FTE to running this product in an organization of that size per month. I would not recommend it for companies with less than 10 people or for companies that value quick communication with their clients. I would not recommend it for companies using Datto's RMM product. The integration exists, but it is clearly a bolt-on. They were not developed together and they are slow to talk to each other. Frequently you cannot add details from RMM sessions into the PSA without manually copying the ticket number, and if the ticket is more than a week old, then you can't even find it with the ticket number.
The graphical calculations on time spent on requests, how long they were open for, who worked on a ticket last.
Grouping by priority so you can determine easier what needs to be addressed sooner rather then later. This also helps if Account Management has conversations a technician is not aware of so they can prioritize efficiently.
The email updates that are sent out to the technicians so they are aware of upcoming or stale tickets.
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.
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.).
Datto Autotask PSA is a full featured product that can do almost anything you need. There is a significant learning curve to get started which requires several hours spent in product training. Additionally, several hours / days are needed to get clients imported, contracts configured, and integrations implemented. Once the setup and user training is complete, the product is very functional, but it's imperative to not get overwhelmed when starting out.
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.
The portion of Autotask that we've used other companies for prior to using Autotask is the Endpoint Management. The Autotask Endpoint Management (AEM) portal integrates perfectly with their PSA/CRM tools. It's alerting features are much better than the above software as there aren't a bunch of superfluous and unneeded alerts. Instead, it only alerts for things that you specify that you want. Alerts aside, for the PSA/CRM, I don't have much to compare it to as Autotask was the first PSA we tried. It's hard to imagine a PSA having more features or doing a better job than Autotask.
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.
