We did a self install, this has had zero issues over the years.

The deployment was personally monitored and carried out at a known organization where the CMMI 2.0 processes and Testing process improvements were carried out over a change management initiative.

After installation, I basically took over getting our test cases entered, our upcoming requirements entered, and so on. The most important thing to know here is that this is a very time consuming process. Not necessarily due to the software, but due to the unavoidable fact that hand entry can take a long time. The software does support importing from certain formats, however if they don't line up with the way you were doing your documents beforehand, it won't be useful. Give your team sufficient time to enter in items as it will save time in the future, and will be well worth the commitment.

I personally did the install and implementation. No outside help was needed.

We implemented the tool in- house. Tthe main advice is to ensure the appropriate backup & recovery process is well defined. We were able to slot SpiraTest backup in with the normal weekly backup cycle. This is extremely important for most tools and especially so for a test management tool.

We used an in-house configuration manager. You should always evaluate the compatibility with your existing environment/tools.

The implementation was done by an in-house test team.

We used an in-house implementations. I advise to plan a lot about the process itself, because the tool does not support that one very well. Also, the report functions are useless without good data consistency.

We did it in-house.

The installation was carried out by the client.

We did the implementation in-house.

This was implemented in–house.