SpiraPlan vs. SpiraTeam

We selected SpiraPlan because the workflow allows us to start simple without adopting an entire methodology. It suits small teams and single users really well.

It is easy to define structures and documentation "modules". This allows for a workgroup-oriented approach and supports SCRUM. However, in the medical device market SCRUM does not work well for documentation. Therefore the modularized approach on the requirements and testing side supports sprint development, while the depth of documentation needed for compliance may not be "ready" and can be completed later.

• Flexible requirements organisation structure. I'm able to group and sub-group requirements as I see fit.
• Competitive product pricing. Paying by active use instead of registered user was the winning point.
• UI is straightforward and easy to use.

• Good Defect Tracking
• Easy to maintain Test Cycle
• Configurable Reports
• Easy to maintain Roles and access

Incentivized

• Access from South East Asia is rather sluggish. Could be due to server location.
• Complimentary phone app to do simple tasks (e.g. create tasks, create requirements, add comments) offline would be beneficial because access to the internet can be an issue at the customer's environment.

• Reporting could be made a bit easier.
• Some functions are not always absolutely intuitive.
• Document baselining can be tricky.
• Some configuration can only be done in the database and is not explained as by the books.

The usability is excellent in most cases but lacks some intuitive functions, such as a copy to the clipboard for selected items. In fact, in an older version, a COPY button copied all selected records rather than putting it on the clipboard. The button has been renamed recently to CLONE, otherwise, my rating would be lower.

Main differentiating factors: 1. Lightweight process 2. Plans based on active users instead of registered users.

None Other Used

Incentivized

• Allows us to manage simple IT requirements without major upfront costs. Allows us to expand our process complexity at our own pace.
• Slow UI response from a South East Asia country can make data entry a drag.

• Better historical information about what happend in past releases, deeper integration with the whole software development life cycle.