What is our primary use case?
We begin by drafting their requirements. However, we have only attempted to employ them for document management, even though they are meant for a requirements management system. Now, we have been attempting to use Polarion in its current manner to oversee the entire process, from requirements to calls. I began using Polarion, primarily for creating demos during the pre-sales phase. However, in my current company, I'm working on enhancing our project delivery methodology.
What needs improvement?
We encountered numerous challenges, such as issues with requirements, project management, timing, and planning. The main problem with Polarion at the outset, I believe, was our limited understanding of the planning phase. During that time, we were more focused on change management related to requirements. Recognizing the importance of planning has been a key realization for us.
Another mistake we made was not comprehending the need to document these requirements to manage all the work items effectively. Now, we understand the significance of this documentation. As a result of these insights, we have started to see a growing number of competitors from Polarion in this field. One potential improvement could be enabling Polarion to export work items not just to Microsoft Office but also to other office tools
For how long have I used the solution?
I have been using this Polarion Requirements since 2018 and we have used it in 5 products.
What do I think about the stability of the solution?
How are customer service and support?
We haven't utilized technical support because we are presently a partner with similar access, and we have never submitted an issue to the support center.
How was the initial setup?
The setup was quite straightforward for us. Our problem lay in not investing enough in training to fully comprehend the functionality, steps, and phases required for this implementation. I believe that once we understand these aspects, the implementation process will be quite straightforward. Perhaps the difficulty arises from translating our current project implementation methodology into the configuration process. Another mistake we made was attempting to perform this translation internally. I believe we should undergo training for this installation process.
What's my experience with pricing, setup cost, and licensing?
I believe the cost is subjective. It seems a bit pricey, but it depends on your perspective. To provide some context, I compared the prices with GitLab and Jira. Unfortunately, I couldn't find Jira's prices. However, GitLab costs around 40 euros, and DeepLab, which I recently discovered, also falls in a similar price range. I'm not sure about DeepLab's features or interface improvements, as they might have been implementing requirements management over the past six months. In contrast, Polarion costs around 50 to 60 euros based on the 2021 prices I have. While it may seem a bit expensive, it's worth considering whether the additional investment, perhaps around 68 euros per user, is justified. It might appear costly at first glance, but it's essential to acknowledge that it can greatly streamline your work processes.
What other advice do I have?
I would rate the product 9 out of 10.
From my perspective, I grasp the Polarion solution quite effectively. It appears to be the most suitable interface for me in terms of document management. Utilizing these documents to meet all the necessary criteria is crucial. Additionally, it's essential to consider the requirement of one license per user. Because, by addressing this aspect, you can automate a wide range of tasks, including those related to value plans and consumer rates, among others.