What do you like best?
It is very easy to sort requirement, tests and progress, so that only the desired elements are displayed. E.g. upcoming features in a planed release. Way easier for people that are not familiar with Spiratest to get an overview of the progress for current release when the entire backlog contains +100 requirement and tests.
For many years i have worked with requirements and test for medical and military equipment and I had previously used Word/Excel or Confluence to manage these. Spiratest is a dream to work with compared to the way i used to work, it is so easy to manage requirements and tests. And not forget the traceability options which is always required for medical or safety equipment release.
What do you dislike?
As an Admin you cant delete existing users (also demo users). I wish i could build my own workflow, it is mostly renaming of flow elements that i miss. The crossreference between projects miss the last work, running a test across two projects will place the result in the project where the test is placed, but it should of course be placed in the project where you have requested to run the test. But i know they are working on the crossreference handling.
Recommendations to others considering the product
I would recommend Spiratest for all that wants/require requirement and test traceability. It is so easy to get/display an overview of current progress to others. Test results can easily be compared to previous releases, since all data is stored.
What business problems are you solving with the product? What benefits have you realized?
I have used Spiratest (admin/tester) at my 2 last workplaces and hope to continue to use it in the future. I use Spiratest for requirement, release and test management for product release. This includes both SW and HW requirements.
Currently we have been using spiretest to manage Compliance demands such as EMC standards. The sort functionality of spiretest is very good at displaying differences between requirements. We used the "status" to set what state the individual standard was in. E.g "obsolete", "active" or "in progress" (meaning that it is a new incoming version, which in time will replace other standards). So even if Spiratest is mostly a software tool it can be very well adapted to other tasks