codeBeamer ALM vs. SpiraTeam

In my opinion codeBeamer is well suited for any activity where detailed tracking is needed with teams involved. It can be less suited for small projects which do not last long, or are not continuous, etc

*Well Suited for Organizations having [fewer] numbers of Tech People that [means] it's easy to operate and maintain. Currently find no scenarios for its less [appropriateness]

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info

• Tracing of requirements.
• Tracking of development.
• Tracking of QA.
• Tracking of bugs.
• Tracking of releases.
• Wiki.
• Users and teams.
• Works for teams scattered across the globe.
• Testing and coverage for releases.
• Integration with SVN.

• Very easy to use.
• Entire collaboration suite for the software development lifecycle.
• Configurable to particular project needs.

• Search.
• Metric calculation.
• Would be nice that cB is a source of truth, i.e., that say SVN commit is done only from cB; know this is difficult to achieve.

• Some more sample reports or allow for a cross reference reporting engine

Sometimes info in codeBeamer can be lost, in principle, if not well organized by the user, info can never be found, or can be forgotten about, etc

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.

Excellent support professionally. Also, thanks for giving me for free access to SaaS cB for my hobbyist project.

codeBeamer is by far better.

None Other Used

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info

• Customer tracking.
• Process tracking.
• Workflow framework.
• Can be overhead.

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