IT Central Station is now PeerSpot: Here's why
Buyer's Guide
Application Lifecycle Management (ALM) Suites
June 2022
Get our free report covering Microsoft, Atlassian, Siemens, and other competitors of Atlassian ALM. Updated: June 2022.
608,713 professionals have used our research since 2012.

Read reviews of Atlassian ALM alternatives and competitors

Senior Research Engineer at a consultancy with 1,001-5,000 employees
Real User
Top 10
The amount of document control, combined with review and release probabilities and signatures is really useful
Pros and Cons
  • "We had a nice experience with technical support."
  • "The ease-of-use could be improved a little."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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.

What do I think about the stability of the solution?

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. 

How are customer service and technical support?

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.

How was the initial setup?

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. 

What about the implementation team?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AsifSharif - PeerSpot reviewer
President & CEO at Modern Requirements
Real User
Top 20
Fully integrated, good testing and can act as a single source of proof, excellent support
Pros and Cons
  • "The most valuable feature is that it's fully integrated, where we have a single place to do everything that we need."
  • "Requirements management is an area that can be improved."

What is our primary use case?

I used Azure DevOps for work item management, sprint planning, source code repository, continuous integration, continuous build, and continuous release. I build whole chains.

What is most valuable?

The most valuable feature is that it's fully integrated, where we have a single place to do everything that we need.

Testing is really good, it has come a long way.

It is the single source of proof or the single system of record that does everything you need, you don't have to put the different pieces together to form the whole chain.

We can do everything in one single platform, which is why it does a good job.

What needs improvement?

Requirements management is an area that can be improved.

Integration with Microsoft teams would be a good idea.

For how long have I used the solution?

I have been using Microsoft Azure DevOps for five years.

What do I think about the stability of the solution?

It's stable. It's been pretty good, especially in the last two years.

What do I think about the scalability of the solution?

There are no issues with scalability. We have approximately 50 people in our organization who are using it.

How are customer service and technical support?

We have contacted technical support and they are excellent. I would rate them a nine out of ten.

Which solution did I use previously and why did I switch?

I am using a mismatch of tools from HP and Atlassian, but they did not give us an integrated toolchain. Microsoft Azure does it exceptionally well.

How was the initial setup?

It is reasonably straightforward, but it is only as straightforward as the problems that you are trying to solve.

If you are trying to set up the whole chain, then the problem is complex, and the solution has to be as equally complex.

What's my experience with pricing, setup cost, and licensing?

The price is reasonable, but of course, you can find others that are cheaper such as Atlassian. But, if you look at the more serious products like Polarion, it's very competitive. 

If you have good Microsoft programs, it's nearly free.

What other advice do I have?

I would certainly recommend this product.

There are a lot of parts to the toolchain for DevOps, so take each area at a time. My advice is to take one step at a time, don't overdo it, and over time build out all of the capacity difficulties. Automation is also one of the biggest things.

Overall, it seems like a really good solution.

I would rate it a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Mathias Florian - PeerSpot reviewer
Business developer at Bat.IT
Real User
Top 5Leaderboard
Data functionality is easy to understand
Pros and Cons
  • "The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
  • "The features are not intuitive. It would be good if there were templates."

What is our primary use case?

Our organization is a software development company. We serve financial institutes that have between 8,000 and 13,000 employees.

We use Jira for process automation and as a workflow engine on the client's side. For example, a customer can fill out a form and ask a question, which is operated by Jira, and someone will be prompted to contact you with the answer. We created the forms designer and the roof engine and handle the process with the customer contact.

We are using Jira for automatic tools, so it is run on-premise.

What is most valuable?

The most valuable feature is that it has different APIs available, with good services, and it is completely by the books.

What needs improvement?

Jira could improve the documents management level. Our customers compare it to Office 365 and Sharepoint Online. They are focused on versioning of the document; Jira is missing this in their environment. It is missing functions for collaboration, like instant messaging. Currently, we try to connect the systems, we use Jira workflow which is connected to Office 365. 

Jira is trying to push for the online version, however, our customers are not ready to do that due to safety concerns.

The features are not intuitive. It would be good if there were templates.

For how long have I used the solution?

I have been using Jira for eight years.

What do I think about the stability of the solution?

Stability at the beginning had some troubles, but it is okay now. To maintain a large network, we divide it between operations and development. We have approximately six people involved.

What do I think about the scalability of the solution?

Jira is scalable.

How was the initial setup?

The initial setup depends on the project. Smaller projects where we are using minimal functionality can be quite simple. On the other hand, we have a monthly deployment process where we extend the solution, which is a complicated process because it's running a system with a lot of users.

What's my experience with pricing, setup cost, and licensing?

Pricing of licensing is too high.

What other advice do I have?

From a user perspective, Jira is simple to understand if they use its data functionality. If you want to extend it to custom feeds then you need further education.

If you are considering Jira, take a look at the online versioning and online pricing.

I would rate Jira an 8 out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Petronela Ghergulov - PeerSpot reviewer
Engineering Quality Analyst at Visteon Corporation
Real User
Top 5
Scalable and simple to use, but the stability could be improved
Pros and Cons
  • "It's easy to use."
  • "The stability of IBM Rational ALM could be improved."

What is our primary use case?

I use IBM Rational ALM in my daily work to verify the engineering tools to see the visibility aspects in different CLM facilities.

What is most valuable?

It's easy to use.

What needs improvement?

The stability of IBM Rational ALM could be improved.

For how long have I used the solution?

I have been using IBM Rational ALM for two years.

What do I think about the stability of the solution?

IBM Rational ALM is not that stable, at least in our company, it has several issues.

What do I think about the scalability of the solution?

IBM Rational ALM is a scalable solution. It is used by everyone in our organization. We have thousands of users.

How are customer service and support?

I have not contacted technical support. We have a team internally that does everything for us.

Which solution did I use previously and why did I switch?

I used Jira, a long time ago. I have not used it for two years.

We switched to IBM Rational ALM because Jira was not a complete Application solution for ALM.

What's my experience with pricing, setup cost, and licensing?

We have a contract, but I am not aware of the details.

What other advice do I have?

If it is used the way it was designed to be used, it could be a higher grade, but it depends a lot on how people are using it.

I would recommend this solution to others who are interested in using it.

I would rate IBM Rational ALM a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
Application Lifecycle Management (ALM) Suites
June 2022
Get our free report covering Microsoft, Atlassian, Siemens, and other competitors of Atlassian ALM. Updated: June 2022.
608,713 professionals have used our research since 2012.