Azure DevOps vs. Azure DevOps Server vs. BMC Helix ITSM

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

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.

Incentivized

BMC Helix ITSM fits our environment particularly well, where standardized, auditable processes are already in place: Incident and Problem Management can be structured cleanly, with clear ownership, escalations, and fully traceable documentation—crucial in a highly regulated banking context. Through the customer platform/portal, users can log incidents and requests consistently, track their status transparently, and use a single central communication channel across service boundaries. This supports a service-oriented setup spanning multiple business services and locations. It becomes less suitable—or at least more effort-intensive—when core foundation data is not yet stable: an immature CMDB, insufficient ITAM data quality, and an unstructured knowledge base limit the value of automation and self-service. In addition, heterogeneous integrations and strict authorization models can increase implementation and ongoing maintenance efforts, especially when SLAs are not harmonized across different customer environments.

• 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

• Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
• Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
• Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.

Incentivized

• AI drive incident correlation leading to identifying problems and major incidents quickly.
• Digital Workplace gives end-users a modern and personalized UI to submit requests, monitor service health, and receive self-help.
• As an enterprise ITSM, it is critical that Request, Incident, Problem, Asset, and Change Management are integrated and flow together. BMC Helix is built on this principle.

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.

• Can add more build templates for specific technology requirements
• Can have more features in dashboards which can help dev teams stream line their tasks and priorities
• Can have raise alarm feature in case of any sort of failure in devops pipeline execution

Incentivized

• Service Level management configs can be lengthy, and when changes are needed to specific SLA, it does take a long time to configure. Templates work but only for certain things, lots of manual work is still required.
• The Online product documentation can be confusing or in same cases not correct.
• BMC products are sometimes expensive. When partners try to resell licenses or increase their own allotment, it becomes very expensive.

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

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.

Incentivized

It provides the tool we need and is able to be customised to meet new requirements. Cost to change in training and integrations would be considerable.

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

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.

Incentivized

Overall the product enhances the capability of incident management, problem management and change management. The AI based framework helps generated better visibility and reports. The effectiveness of enhanced service desk suuport improves end user experience as the incidents are handled well in time and aged incidents are highlighted at the right time.

Incentivized

for now we are satisfied. first two months 😉

Incentivized

could be faster. db is slower from introducing postgresql

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

Incentivized

Their tech support is top notch. They respond and get back to us, even on lower level incidents and issues, very quickly. It is rare that we deal with a support technician who does not know what they are doing.

the trainers dont have so much practical experiences. its mostly follow up and reading existing documentation withou own input. of course experiences people are on shore or have no free time. sad truth

Incentivized

Was not part of the process.

Incentivized

Do research beforehand and, if possible, do a trial run before implementing into production environment.

Incentivized

Satisfied because I didn't have to do it!

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

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!

Incentivized

I believe Remedy's performance and market share exceeds its competitors. But it is worth mentioning that Microsoft's SCCM has excellent integration with Microsoft enterprise solutions and has is less expensive and not efficient. The IBM solution has better analytics but lacks the wide features and capabilities of Remedy. HP & CA are the real competitors for Remedy but lacks the stability, maturity, and effectiveness in Remedy

Incentivized

unclear. lot of for less

Incentivized

Again, always room for improvement, but a very stable product none-the-less.

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

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

Incentivized

• Positive: an introduction to ITIL and viewing Asset, User Management from the perspective of ITIL, and how BMC has implemented those processes
• Negative: The development team needs to communicate better with the sales and support side, and they need offer an open API
• Negative: Currently the Asset Management side has little security and validation of Asset input: anyone can make API (mostly), at any item, which is a problem that I am apart of solving.
• The UX needs updating, badly. Its quality is poor: it functions, but it is cumbersome, click-heavy and requires several hours to understand how to function with it. Also, it needs to ditch IE11 support, altogether.

Incentivized