codeBeamer ALM Pricing, Features, Reviews & Comparison of Alternatives

Pros
Very flexible and powerful platform that can be adapted in a variety of ways to align to your process and practices for managing your application lifecycle. Expect to invest time and effort to configure the platform to meet your needs and expect significant return on your investment. Over a 6 month window we rolled out codeBeamer capabilities for: 1) Requirements Management 2) Risk Management 3) Architecture and Design Management 4) Test Management 5) Defect Management 6) Scrum Team Rituals (Sprints, Stories, Tasks, ...) codeBeamer is now our single digital system of record for the full Application Lifecycle.

Cons
It can be challenging to debug why a user is unable to execute a task given the intersection of 1) license constraints 2) project permissions 3) tracker permissions 4) field permissions

Rating breakdown

Pros
Simply: it works! Seriously. I worked with other ALM tools. Either the tools didn't cover (understand) the ALM universe, or the tools were glued together resulting in diminished functionality or even failure. Supected links. Traceability browser. Test coverage. Those tools work perfectly in codeBeamer.

Cons
Sometimes it's difficult to handle WYSIWYG. Implementation is done with a third party tool (Froala) and codeBeamer is bound to its limitations and drawbacks. Usually I get my ideas realized within the HTML editor, but sometimes you have to struggle a little.

Rating breakdown

Likelihood to recommend: 10/10

Pros
Good agile development features including Kanban board and Scrum process artefacts Easy management of integrated SCM repositories (Git, SVN) Good handling of project templates to specify and provide organisation specific development process templates REST API for a flexible integration of CodeBeamer with other tools Improved dashboard functionalities for project and user dashboards

Cons
It would be great to get more out-of-the-box integrations with other popular parts of a development toolchain like: Slack, IntelliJ

Rating breakdown

Likelihood to recommend: 9/10

Pros
Tracking the requirements Tracability between requirements Create and use the libraries Baslining of the specifications Ajust the workflows of each Tracker/department Release management SW-test reuse Change management for the requirements/test

Cons
There are tree ways to create the authorization/user-management and this is sometimes difficult because of the roles for each project. If in our template project is create a new role we have to make the input in each prject manually.

Rating breakdown

Likelihood to recommend: 9/10

Pros
* adaptability * large scale of functionality (from requirements to implementation, to testing, releasemanagement and Support) * very good documentation about codebeamer * webinars from intlant * full-text search

Cons
* too many posibilities for filtering or reporting of issues with too different features (the one you use allways needs a feature of another search functionality) * too less posibilities for dashboards (maybe changes with 8.1) * project management (ok its not the focus of this tool, but it would be nice)

Rating breakdown

Likelihood to recommend: 9/10