Polarion ALM Reviews

We do requirement management and task management using this tool.

We're generally happy with the solution. 

It is stable and reliable. It offers good performance.

The pricing is fine. 

The planning and task management aspects of the solution were not that easy.

It is a bit complex to set up.

I've been using the solution for one and a half to two years. 

The performance is pretty good. It has been stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

I'm familiar with Jir and find that it has better planning and task management features than this product. 

The product is complex to deploy. There is a lot of customization needed in order to use it effectively. It works for us now. It's not too difficult. 

We did have help from a third party that we have used for a long time. They gave us some good, sound advice. 

The solution offers a good balance between price and performance. 

We have been looking into other options. 

I'm not sure which version of the solution we're using at this time. 

If you do a good job at customization, it will help with consistency and assist with the traceability of the products. 

I wouldn't recommend the product to people who need a task management or planning tool. That's not this product as well.

As an ALM tool, I'd rate the solution eight out of ten. 

Polarion ALM's integration is very good and easy to use. 

The tool needs to improve its planning. It also needs to add more integrations. 

Polarion ALM is stable. 

Polarion ALM is easy to install, but you need good training. 

You have to pay around 50-60 euros per user. 

It is the best tool, but you would need training. I rate it a nine out of ten. 

We use Polarion ALM for development to track requirements, tasks, anomalies, project and design documentation, and other things.

This one tool incorporates almost all engineering tasks we need to do for one project. However, it's still not a polished solution for how we deploy it. So we cannot use it as a single solution for everything. Also, there are still some uses for which it's not recommended. But this is one of the primary tools our engineering team uses to keep track of their documentation for the project.

Polarion ALM has some valuable tools for managing our targets and requirements. I think that's its best feature. All the other features are helpful, but a lot of them don't work out of the box. In terms of planning and management, they need some work. 

One of Polarion's shortcomings would be planning. It can handle plans, but the planning feature is very basic. There are third-party solutions that could be easily incorporated or built into the license. They have plugins they developed only after many customers complained about Polarion's integration with third-party repositories. Some of the repositories aren't working all the time. So it works when you set it up, but it stops working after a while, and there is nothing you can do except reset the whole server and try it again. So it's not a convenient way to deal with those issues because the solution should be up 99.9% of the time.

Another issue is Polarion's integration with external tools, including repositories for source code, mechanical design, electrical designs, etc. There should be out-of-the-box integration with different tools like Jira or things of that nature. Some of this functionality exists, but it's not so easy to set up. Polarion ALM needs more integration with external repositories, especially for source code. Most of these tools don't recommend using Polarion ALM as a repository, so you have to use Search Party or a different tool for that. And integration is not straightforward or not easy to do. 

We started with Polarion ALM over a year and a half ago.

In terms of stability, Polarion ALM is okay. Some highly stable features work and integrate with other tools out of the box. Then some are not so stable, so you have to wait for the bugs to be fixed in the new releases. The stability of other features depends entirely on the IT infrastructure because they use a lot of resources. Then again, I don't know if that's necessarily Polarion's problem or how it's deployed. 

But overall, I would say Polarion is reasonably stable. We haven't had any downtime. However, there were times when we had to look for alternatives because some of the things we expect from the tool's administrative functions are not there. So you have to use specific plug-ins to be able to achieve what you need. That limits the way you can interact with the tool.

It looks like Polarion ALM is highly scalable. However, you might need to scale the team managing the tools. That's not something that most organizations are willing to do. Polarion's scalability depends on whether you have enough people to support it, so it's not necessarily the best option. It would be great if you could scale it up while easily managing and deploying it with a relatively small team. Right now, scaling up Polarion means you might need extra resources. As I said, most of the administration capabilities are not too user-friendly. It's not easy to deploy it across all projects quickly. Keep in mind that in this field, you deploy it once you have the database with everything. You cannot switch it off and then move to another server and another version with a new database next year.

And you'll have to preserve everything for, let's say, 15 years or so. So that means you have to do in-place upgrades then scale to support different templates and configurations for various projects. You'll start some projects one way and take a different approach for others. And when you change something, you'll have to support all those configurations still. You don't just apply the new configuration to everything. Sometimes, you need to apply things that are not available in the tool itself with too many projects. So you can scale, but you need lots of people to help you deploy that very fast. It's not that easy to scale once you've been working with it for a while.

I would say Polarion's support is average. 

We had some older solutions that we were using in several design centers across the globe, but the solutions were running out of support. Even the vendor was switching to something else, and what they offered didn't integrate well with other tools, so we had to find a new solution. Polarion ALM was one of the solutions that the other design centers were considering. In the end, we went with it, and the local ones were phased out as the projects started using Polarion. We never planned to migrate all the old stuff because that involves extra effort and cost and might not work 100 percent. So the old solutions are still around just for the legacy projects while all new projects are on this new system.

Polarion ALM is an administration tool that is very complex. Customizing the out-of-the-box configuration for our use case requires more work administration-wise than other tools we had in the past. For some tools, one person can administer all the projects in that tool. It's a bit more complex also because it allows you to make more mistakes. And you have to manually trickle down the configuration from one item to another — it doesn't have a way to automate this administrative work easily. So you have to know your way around and pick the right thing then duplicate the same setting somewhere else. Otherwise, it is not user-friendly from the administration's point of view.

We were switching everything over from our previous solution, so initial deployment took about a little more than six months, but now many projects are using it. But we're constantly reconfiguring Polarion ALM for new projects because some things didn't work out of the box or work as expected when we started using it. So when we implemented a tool and found a bug, we had to look for alternative solutions.

Our license for Polarion ALM is yearly. And it's not the cheapest tool that we've looked at. So if we had made our decision purely based on the licensing cost, we wouldn't have selected Polarion. Like most tools of this kind, there are maintenance costs and support contracts, etc. We're also looking to purchase a different license for other plugins that add features Polarion doesn't support or do right. If the vendor doesn't plan to improve on those features, we'll look for a third-party solution for that. So all of these costs are added on top of it.

We were looking at a few options, and we all evaluated each based on what was available out of the box. But, of course, some things don't work the same when you're using them on a project as they do when you're evaluating a product. Most evaluations don't last very long, and sometimes you realize faults with a product after the review. So we had a few products that we evaluated. In the end, Polarion turned out to be a little bit better than the other tools. I can't say whether those other tools have developed more since to overtake Polarion.

Overall, I would rate Polarion ALM eight out of 10, but it depends on your intended use. If you are limiting the scope to just a few uses, it can go all the way to 10. But if you want to use it for all the aspects of the development process, my rating would go down to six. I would also point out that some other tools are easier to administer. For example, there are tools where the administrator has to do very little. In Polarion, the admin needs to make some configuration changes and modify access rights at every level. But in other tools, these configuration changes trickle down automatically on their own without the need to double-check several places before you can finally say it's all done. So administration-wise, they can improve. And the out-of-the-box features should all work as needed without a lot of tinkering. 

To people considering Polarion, I would say that you need to do a thorough, extended evaluation. Make sure that you have an initial team of at least 10 or so people before moving ahead with a company-wide deployment. Of course, this depends on your company's scale and how many projects you want to support. If you're working on one project at a time, then one person can handle most of the stuff.

The primary use case of the solution is writing test cases, mapping those test cases to the requirements, and creating and executing test runs.

The features I find the most valuable are requirement tracking and schematics. 

The solution can be improved by making it more user-friendly, and a server-based application rather than client based. I find it difficult to update the test cases in the test run and would like a more simplistic process. As an example, If I create version one of the test case. And in a test run, I add that version one of the test cases in the test run and I go to that test case and update it to version two, I can update that fine, but in the test run, it is not automatically updated to version two.

I have been using the solution for one year.

The solution appears to be stable.

The solution is scalable.

I give the solution a seven out of ten.

There are six users in the organization using the solution and three of them use it daily.

This solution is used when we have projects based on web applications.

I suggest anyone thinking about using the solution familiarize themselves with the tool first by using a quick start guide.

There are similar solutions out there such as Jira and Confluence, but they are not as good.

The best feature of Polarion ALM to me is its traceability link.

As Polarion ALM is a development-oriented tool, easy support or easy access is provided by default, but if I want to use detailed features, I need to write the script, particularly the VM script, and this is its area for improvement. I want Polarion ALM to have a graphical user interface that doesn't need scripting.

In the next release of the tool, I'd like for it to not require scripting and programming because needing to run script language is time-consuming.

The first time I used Polarion ALM was two years ago, then I stopped using it, then two months ago, I started using the solution again.

Polarion ALM is a stable tool. I have not seen it breaking down or having issues.

I'm not sure how scalable Polarion ALM is because I only have one server and one computer for it.

The technical support for Polarion ALM is very good. I quickly get a response from the team. The support team is knowledgeable, and I would rate technical support for the tool the best score which is five out of five.

I used the classic DOORS and when you compare it to Polarion ALM, DOORS has an old interface. Polarion ALM has a newer interface and newer, more updated features than DOORS.

Whether Polarion ALM is easy or complex to set up depends on the installation scenario. If it's load balancing, setting the tool up is difficult, but if it's just a standalone installation on one server, the process is relatively easy. On a scale of one to five, with one being difficult and five being easy, I would rate the setup in the middle, so three out of five.

I don't have information on the price of Polarion ALM because it was the customer who purchased it.

I've evaluated IBM Rational ALM, Terralogic, Serena ALM, and the classic DOORS.

I'm a consultant for customers. I'm using Polarion ALM for my customer. In particular, I provide the service to my customer using Polarion ALM.

In terms of how Polarion ALM is deployed, for Japanese customers, it's on-premises because of confidentiality and sensitive information. Many Japanese do not believe in the security of cloud deployment.

My rating for Polarion ALM is eight out of ten.

Polarion is an all in one tool that we use from conception to validation testing. Our product team uses it for their requirements, our developers use it for their stories and tasks, and our quality team uses it for testing. 

It integrates with SVN and GitLab.

It's all in one place, where every department can utilize the same tool. It meets with everybody's needs without having to grab plugins. For example, Jira is nothing but a bunch of plugins.

What is most valuable is that this is an all-inclusive tool.

This is an area that has already been corrected, but the Navigation areas of the document and being able to have subdocuments was an area that needed improvement.

Technical support needs some improvement.

The pricing could be reduced. If the pricing would come down and it was more affordable then we wouldn't have to switch.

I have been using this solution for six years.

This is a stable tool as long as our environment is stable.

For us, it has been quite stable so far.

This solution is scalable and it's highly configurable. Most of it can be done through the GUI and you can get into the backend, the XML, and make changes as well.

Technical support varies, it's 50/50. You can get a knowledgeable person and you get great support. If on the other hand, you can't get someone knowledgeable then you get a runaround.

I wasn't a part of the initial setup.

It is a clustered environment where we have three nodes that our users hit to gather the data, then we have a shared database.

It's been the only ALM tool that I have used. 

As far as capabilities and learning the system, I would rate this solution an eight out of ten.

We mainly use Polarion ALM for requirements engineering as well as task planning and task execution, but we mainly use it as a documentation and traceability tool.

I work in the medical device development field. Even though Polarion is quite expensive, it's quite a good solution for medical device development in general, especially for software development.

Within our previous company, not that many people used Polarion as it was only used within our department relating to medical device development. I'd say around 20 to 30 people were using it. It's hard to say as we had around six licenses with some floating licenses.

I like that there is, more or less, a single solution for everything. In regards to Polarion, if you're not experienced, it can be quite complicated, so you may need weeks or even months to familiarize yourself with the tools and how it operates. Once you understand how it works it becomes a very useful tool; we mainly use it for requirements engineering, so for us, the traceability is a really important feature. I also like all of the possibilities for different reports and the option to have a "what you see is what you get" editor for all documents and especially, for the release of documents. 

The amount of document control, combined with review and release probabilities and signatures is really useful. For example, Confluence does not have these capabilities. You would have to install Comala, with its plug-in that is used for document control, and even then, it would not be comparable. Polarion's document control is one of the best that I have used. In terms of development itself, having the work items and requirements altogether in one place and being able to control them by Staples, is really helpful.

The ease-of-use could be improved a little, but at the same time, it's a complex tool so that has to be expected; such a complex tool cannot be completely straightforward. 

The license model is okay for large companies but would be quite expensive for smaller enterprises.

Also, the beginner's tutorials are quite outdated — working on versions from 2010 or 2012. More up-to-date tutorials with different use cases would be a nice adjustment.

It's always possible to improve such tools by adding more features and improving automatization. For example, we never tried the connection to build service. I believe it's possible to do that, to automatically link it to the software build process. We only used it more or less manually. It's possible that, that feature could be improved because I believe there was a reason why we didn't do it, but I can't explain in more detail as I was not really involved in the process.

In general, I would like to see improvements on the information and materials.

My current company has been using Polarion ALM for quite a long time, since approximately 2012. I personally started working with Polarion ALM four years ago.

I don't remember any real bugs. We always had some (more or less) minor questions relating to different issues. I don't completely remember, but we had direct contact to our vendor here in Austria, so in most cases, problems could be solved in a more or less direct way. So no really big problems. 

We had a nice experience with technical support. Contacting them was like gaining secret knowledge because so much information is not published, like macros and snippets of code and so on. If you just ask, they will give you different pieces of code for different purposes — for reports for example. You couldn't find that hidden code on your own but if you ask, Siemens will, more or less, give it to you for free. As it's clear that they don't want to publish everything on their website, just ask if they have a solution that is yet to be published, and maybe they can help you out.

I was not involved in the initial setup. Still, when you're working with Microsoft, creating your own code within the system, you have to be the admin. Also, when updating to a newer version, problems can occur leading to the loss of older, developed pieces of code. It's a small issue but you need to be aware of it in order to handle it properly. Other than that, the setup is quite straightforward. 

Maintenance was distributed between several people. We had one main administrator. We were quite a large company with 1,300 people in total, but there were only around 60 of us working in the medical device domain. We had one central IP infrastructure, but they only provided us with computers to the hardware. We managed the tool within the departments on our own. We had one administrator, who was the master administrator, who did the updates, and so on. We also had several tool administrators. In other words, we were two units within the department and for each unit, we had one administrator.

The license model is okay for large companies but would be quite expensive for smaller enterprises.

If you're a beginner to Life Cycle Requirements Engineering in general, I'd recommend that you familiarize yourself with the basics of requirement engineering in order to gain independence of the tool itself. Eventually, when you start using Polarion, start from the very beginning. Even though the tutorials are out-of-date, they are still helpful. 

We also used our vendors as our trainers and teachers. We booked them for three or four days to get a proper introduction to Polarion. Starting off with an expert is a really good idea, it will cost you, but it will save you so much time. One expert instructor can teach more than 20 workers at once, saving you hours or even weeks.

I would rate Polarion really quite high. We were happy with it, and nowadays, without this type of tool, it's not possible to develop medical devices independently of software or hardware. I would give Polarion a rating of nine out of 10.

We use the solution for development.

I am impressed with the solution’s stability.

The solution needs to improve its user experience and graphics.

I have been using the product for seven years.

We have our own team for support.

The solution is expensive.

I would rate the overall solution an eight out of ten.