Azure DevOps Services vs. Polarion ALM

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.

Polarion ALM shines where it is intended to be used: Application Lifecycle Management. It fits well with agile development concepts, but the extensive customization abilities allow it to adapt to other concepts, too. It is suitable as an all-in-one solution, which is capable of giving transparency over all related areas, be it Requirement Management, Test Management, Release Management, Defect Management, etc., to the involved stakeholders.

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

Incentivized

• Requirement management in Polarion is extremely effective, with a simple but powerful authoring environment, simple approval process management, seamless traceability and advanced reuse capabilities
• Test management capabilities allow to link together the requirements with the validation process, and let the user define, plan, execute and record tests across the whole development process
• Day bay day management of development is easy to track, with out of the box support for agile methodologies, live planning reports and integration with Git, SVN and CI/CD tools.

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• Depending on complexity of application, it can be difficult to learn
• Object oriented way of organizing information might be difficult due to high abstraction level
• Massive configuration possibilities give also great responsibility and need clear focus on business benefits to prevent going too much tool centric

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

There is too much at stake to go into a new system. But with everything else being promised as far as newer more innovative products, the justification to not renew is a huge risk so that is not a concern

Incentivized

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.

Incentivized

Polarion ALM can be used individually and what I do with Polarion ALM is decided by my configuration. Lesson-learned, operational risk management, product, system or software development or customer management .... doesn't matter at all. I decide with my configuration what I will do with Polarion ALM. Of course, you can also use Polarion ALM out-of-the-box for your development because it comes with a large set of project templates.For this reason, I would also recommend not to just get started. A suitable consultant will show you the right templates and customize them according to your needs. Having Polarion ALM is like having a car. You know exactly how to operate the car. You've done it a thousand times before. The details are in the configuration: did I have a navigation system installed or not? Do I have a lane departure warning system or not? Do I have cruise control or not? Unlike when buying a vehicle, almost all functions are already available and can be used, usually at no extra cost. However, if something is missing, it can be obtained via the manufacturer's extension portal. Individual extensions are subject to a charge. Polarion ALM - easy to deploy and easy to use.

update, reindex takes to long

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

Support for customers using the full range of Polarion could be better.

Incentivized

competent trainer, good training project

Incentivized

easy to follow, efficent

Incentivized

Was not part of the process.

Incentivized

Automated install and backup procedure ist missing

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

Some tool suites look cheaper at first, but the hidden costs make it expensive in the end. This also applies to the operation of the application or, in the case of some manufacturers, I would have to speak of stitched applications. Regardless, with all tools it becomes critical at some point. We have found for ourselves that when safety and/or security come into play, things get tricky with most applications. Ultimately, it is and remains a matter of taste and the food should be based on the requirements and not on personal sensitivities. I hope everyone makes the right decision for themselves and the company.

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• The traceability features in Polarion ALM help identify and address issues early in the development cycle
• Polarion ALM provides real-time dashboards and reporting, offering stakeholders visibility into project status, progress, and quality metrics.
• The initial implementation of Polarion ALM may require time and effort. Some organizations may face challenges in adapting to the tool, and there might be a learning curve for users, especially those new to ALM solutions.