The initial setup itself is not that challenging. But, the upgrades can be quite time-consuming. 

Since we started using this solution, we have had two major upgrades. These upgrades can take a significant amount of time and often introduce major issues. 

As a strong partner of IBM, we report these issues to them so that they can identify and fix the underlying problems. The data-sharing experience varies from customer to customer due to differences in data size. 

For smaller data sets, the process is relatively easier. However, for larger data sets like ours, the process becomes more complex and can lead to slowness, performance issues, and other unforeseen challenges. We closely report these issues to IBM, and their development team provides fixes or patches to improve the overall tool.

The initial setup is not that complex, the documentation gives you all the help you need. User adoption is a problem because it's not as intuitive as JIRA and it requires proper training, to understand where things are aligned. Especially in the RTC part of the CLM, or maybe RQM part. There are sometimes bottlenecks. 

The initial setup was not that simple. There was a steep learning curve for first time users and even steeper when configuring workflow and work item types.

Basic setup is pretty much straightforward.

Setup is straightforward. However, there are too many possible permutations and combinations, though it allows for good flexibility.

Setup will include simple application deployment, database, application server, and LDAP configuration.

The learning curve was high as the setup was not quite intuitive.

We started out directly with a standard process template, Scrum, and made adjustments on the run. Therefore, the start was easy.

However, later on we needed to change from the standard template to a custom template and this was somehow complex.

For us, the initial setup was a bit difficult. We had to learn the setup by practicing. An expert may have been able to lessen the difficulty and the time needed to set up the solution. The first time we did the setup we didn't have a good understanding of Scrum and the terminology used in the Scrum process, and the corresponding terms. Once we understood everything the process became simple.

Complex.

It was easy.

It was simple

Initial setup is a bit complex. You need to install and configure the WebSphere application server, create databases, setup some environment variables, and then finally run the product setup. To be fair, the product setup is straightforward, but until you get there, you have to do a lot of adjustments.