Azure DevOps vs. HYCU

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.

Incentivized

The SQL database structure and application-consistent snapshots to local storage and recovery are very well done. The interface is nicely made and it is an intuitive design that needs very little training to use. The Restore from the Cloud function is cumbersome and slow, that could be improved by downloading and finding parts needed, instead of the entire backup media.

Incentivized

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

Incentivized

• Tiered backup policies
• On-Prem backups
• Cloud storage target backups

Incentivized

• 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.
• It could improve the search slightly better.

• I'd like to see lower annual costs.
• The setup for Azure backups required a lot of assistance from Support.

Incentivized

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.

Incentivized

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.).

Incentivized

In a Nutanix AHV environment, it’s probably the best solution out there. It checks the most important boxes for us - immutable backups, on-Prem and off site backup storage targets, Azure DR. Policy based backups make administration a breeze. Pricing is cost effective. For the most part, support is able to take care of our needs, but better guidance around creating an effective and robust DR solution is needed

Incentivized

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.

Incentivized

I have had several requests, and issues with the rollout and deployment of HYCU in our production environment. The HYCU team of support and developers have met each issue with importance and some kind of resolution or explanation of help. They have been so supportive even in the not so easy ones. That says something for their product and team behind it.

Incentivized

Was not part of the process.

Incentivized

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.

Incentivized

This fits Nutanix better than anything I have found. HYCU clearly focuses on personalized service. You can email, call or open a web ticketed, depending on your urgency.

Incentivized

• 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.

Incentivized

• We have saved a few SQL issues and recovered data that could have been corrupted.
• Applications and files have a place in the cloud in case the need is there for other depts.
• Restoring across datacenters is possible with HYCU saving us time and money to do so.

Incentivized